> The
> pointer to config for the plugin instance is given as a parameter on the
> instance creation so it may be remembered in the private data to use for
> that purpose.
Ah yes! Thank you!

>     Please, inspect LXPanelPluginInit description in the plugin.h header
> file - the config callback should never run configuration dialog but just
> compose it, you know you can handle different responces anyway, just
> connect to the "response" signal and use g_signal_stop_emission_by_name()
> API if you want to keep dialog still open after responce.
Thanks for that.
I see how it's done in dclock and it looks like I'll have to further
modularize the logic and separate creation from execution of the dialog.

Very cool!

Cheers!
Piotr


------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list

Reply via email to