Quirks and issues found by jwt:
[17:47] <jwt> phoku, does mapEvents override a previous mapEvents call? Or merge with it?
[17:47] <phoku> mergeing it
[17:47] <phoku> hm, that is definitely missing: unmapEvent
[17:47] <phoku> oh
[17:47] <phoku> wait
[17:47] <phoku> i think it does override
[17:48] <jwt> ok, doesn't really matter either way. But it should probably be added to the docs
[17:48] <phoku> yep =)
[17:48] <jwt> also, I think merge leads to nicer end-user code, if that wouldn't be too difficult to change
[17:49] <phoku> hm it merges different events
[17:49] <phoku> but overrides events/names which are same
[17:49] <jwt> oh, ok. So it does do what I want :)
[17:49] <phoku> though i am unsure whether the old event get's actually unmapped
[17:50] <phoku> i do think the old handler still gets called!
[17:50] <phoku> this behaviour will change.
[17:58] <jwt> any ideas http://rafb.net/p/SFbYON74.html ?
[18:00] <phoku> hm
[18:00] <phoku> try:
[18:00] <phoku> button = Button(...)
[18:00] <phoku> button.name = key
[18:01] <jwt> ha, there we go!
[18:01] <phoku> hmmm.... the self.gui is already shown?
[18:02] <phoku> try leaving out the button,show()
[18:02] <phoku> but call gui.adaptLayout -
[18:02] <jwt> ok, will do
[18:03] <jwt> hey, it works! Now if I just had a way to pick which side of the Spacer to put the button on ;)
[18:04] <phoku> that won't work until refinements
Edit: I think both are fixed now.