Yes, I know about GSettings and use them a lot to store static
options. Thanks a lot in any case. Here I wanted to store a reference to a gtkWidget that is created in the preferences dialog. The way I wanted to do is: gtkWidget is created in pref.js, a global variable is used to reference the widget, and the extension knows that the widget is created and directs some output there. One way I was thinking about before was to direct output to a GSettings key and react on this change in prefs.js, but that is not efficient. Another way was to direct output to a file, and read the file in prefs.js. I do not like either solution. For me the best deal would be to share some variable space between both extension and prefs.js, but as far as I know they are in different processes. Any other ideas? Thanks again, Vadim. On 04/10/2013 06:55 PM, Amy wrote:
|