That can't work, since prefs runs in a separate process to
gnome-shell. You will need to use dbus to communicate.
On 11/04/13 15:41, Vadim wrote:
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:
Hi Vadim,
Could you just use gsettings (i.e. the same thing that
you use with `prefs.js` to store extension settings) for
this?
In the `prefs.js` your widget does a:
let settings = Convenience.getSettings();
settings.set_int('my-setting-name', 1);
and in the extension you connect to the change:
// in your init() say
let settings = Convenience.getSettings();
// in your enable() say
settings.connect('changed::my-setting-name',
callback)
So `callback` is called whenever a user changes
the setting in the prefs widget.
_______________________________________________
gnome-shell-list mailing list
gnome-shell-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-shell-list
|
_______________________________________________
gnome-shell-list mailing list
gnome-shell-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gnome-shell-list
