At 1250335283 time_t, Uli Schlachter wrote: > If we remove/add a widget we are not in this code at all. Instead we would be > in > luaA_wibox_newindex()' A_TK_WIDGETS case.
No. This A_TK_WIDGETS case i only used when you do mywibox.widgets = bla > But yeah, stuff like 'mytextbox.text = "new text"' goes through this code and > could change the widget's size (or even some other widget's size which makes > all > other widgets move around alittle). Damn. :( Yup. > Ideas how to fix this? We could check in wibox_draw() if the widget under the > mouse changed. Would this help and fix this? Want me to write and submit this? Yeah, actually wibox_need_update() should do a little more than doing ->mouse_over = NULL I guess. It should send something like mouse_leave maybe. I've no idea right now. Propose. :) -- Julien Danjou // ᐰ <jul...@danjou.info> http://julien.danjou.info // 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD // This is the end of my signature.
signature.asc
Description: Digital signature
