On Mon, May 24 2010, Daniel Graña wrote: > That's cool, but I can't find a place for where I can access phys_screen and > widget creation.
Indeed. Widget creation is not related to a screen, that's gonna be a problem. So basically, that let's us with your initial approach if we don't want to break the API. >> In your approach, the X systray is not registered if the systray widget >> is never attached to a wibox or displayed. > > > I merged the patch: http://gist.github.com/412326 > > It is much simple to read now, and it is clear (as you said) that it is > registering/unregistering > based on systray existence inside wibox for each phys_screen. Ack. > Sorry, but I am a newbie here, can I ask why not? > It doesn't makes sense to me to register for systray notifications if > systray widgets can't show > updates because they are not attached to a wibox. Creating a systray and registering it should be done in a row IMHO. Attaching to a wibox, making it visible, etc, should not interferes with it being registered. But as you pointed out, we lack of widget<->screen assignation upon widget creation, so your approach is the only we can implement for now, so I say we'll go with it after all. I'd like a couple of "OK it works" from some people who tested it. Guys? -- Julien Danjou // ᐰ <[email protected]> http://julien.danjou.info
pgpJQNSRUgjyB.pgp
Description: PGP signature
