On 30.05.2011 19:42:22, Peter Bloomfield wrote:
Got it! It was a bizarre consequence of creating Balsa's UniqueApp
with a NULL startup_id. Using a startup_id of "balsa" fixes it
(both the status request and the mailto handler), but with
who-knows-what other unintended consequences. Can anyone explain
the role of the startup_id?
Freedesktop.org has some discussion of the startup process
<URL:http://standards.freedesktop.org/startup-notification-spec/startup-notification-latest.txt>,
which states that the startup_id should be globally unique, and which
contains a suggested format. I'm testing that now--seems to work.
Hey, Peter! great news!
I hope you'll port the fix to GTK+2 branch because
I (and ALTLinux) are ready to switch to GTK+3 balsa as soon as it'll
have all the features the main branch has.
Thanks a lot!
--
Ildar Mulyukov, free SW designer/programmer
================================================
email: [email protected]
home: http://johan-notes.blogspot.com/
ALT Linux Sisyphus
================================================
_______________________________________________
balsa-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/balsa-list
