Ah. I see...
gtk_accel_map_save() : Saves current accelerator specifications (path, key and modifiers) to filename. The file is written in a format suitable to be read back in by gtk_accel_map_load().
So, the paths are good for persisting your customised hotkey settings between runs of your app.
But I we'll not be needing that for MaxGUI.
Maybe we can do :
<appname>-<windowtitle>/<gadget>/<some-generated-id>
I wonder if we shouldn't follow child heirarchy in the path? Perhaps that's a wee bit of overkill though :-)
<appname>-<windowtitle>/<panel1>/<panel2>/<gadget>/<some-generated-id>
gtk_accel_map_save() : Saves current accelerator specifications (path, key and modifiers) to filename. The file is written in a format suitable to be read back in by gtk_accel_map_load().
So, the paths are good for persisting your customised hotkey settings between runs of your app.
But I we'll not be needing that for MaxGUI.
Maybe we can do :
<appname>-<windowtitle>/<gadget>/<some-generated-id>
I wonder if we shouldn't follow child heirarchy in the path? Perhaps that's a wee bit of overkill though :-)
<appname>-<windowtitle>/<panel1>/<panel2>/<gadget>/<some-generated-id>