Thanks for that, although it seems that once the I set the container's widget to systray, setting it to nil again does not remove the systray from my wibox. Any ideas? Do I have to have the wibox redraw itself or something?
On Mon, Dec 31, 2012 at 6:41 AM, Uli Schlachter <[email protected]> wrote: > Hi, > > On 30.12.2012 22:43, Sean Goodwin wrote: > > I upgraded to 3.5 today, and in the process of updating my widgets I > > noticed something that seems to be missing, or at least I can't find it. > In > > 3.4 I could call visible on a systray (I.E. mst = widget({ type = > "systray" > > }), mst.visible = false and the systray would not show up) but now that > > systrays are handled through wibox I can't seem to be able to set this > > value. I've looked through the documentation to see if there was any > > mention of a new visibility function, but I can't find anything. If > anyone > > could help me I would appreciate it. > > That's right, there is no ".visible" right now. Something like this could > be > added, if needed, to all widgets by implementing lots of magic in > wibox.widget.base. However, I'm not sure if I really like this magic. > > In the mean time, here is some hack to fake .visible for any widget: > > local systray = wibox.widget.systray() > local container = wibox.layout.margin(systray) > (Use "container" instead of the actual systray in your wibox) > > To hide the systray: > > container:set_widget(nil) > > To make the systray visible: > > container:set_widget(systray) > > Uli > > -- > - Captain, I think I should tell you I've never > actually landed a starship before. > - That's all right, Lieutenant, neither have I. > > -- > To unsubscribe, send mail to [email protected]. >
