[Wesnoth-bugs] [bug #25337] allow custom widget definitions in umc

Update of bug #25337 (project wesnoth): Open/Closed:Open => Closed ___ Reply to this item at: ___ Message

[Wesnoth-bugs] [bug #25337] allow custom widget definitions in umc

Follow-up Comment #6, bug #25337 (project wesnoth): https://github.com/wesnoth/wesnoth/pull/895 implents this, the wesnoth.unregister_widget_defnition function might be added later when we have a usecase for it. ___ Reply to this item at:

[Wesnoth-bugs] [bug #25337] allow custom widget definitions in umc

Update of bug #25337 (project wesnoth): Status:None => Fixed ___ Reply to this item at: ___ Nachricht

[Wesnoth-bugs] [bug #25337] allow custom widget definitions in umc

Follow-up Comment #3, bug #25337 (project wesnoth): You shouldn't be adding definitions before the dialog shows. You should do that early, in a load event or similar. Plus, if you try to add the same definition twice, obviously it won't actually be added twice. So even if you DID add your

[Wesnoth-bugs] [bug #25337] allow custom widget definitions in umc

Follow-up Comment #2, bug #25337 (project wesnoth): > I think it would make more sense to automatically unregister any custom definitions when the Lua kernel is destroyed. .. Hmm yes i had the same idea, but i wonder whether that's enough ? If you have code that adds a new definition everytme

[Wesnoth-bugs] [bug #25337] allow custom widget definitions in umc

Follow-up Comment #1, bug #25337 (project wesnoth): I too prefer the second method, but rather than an unregister function, I think it would make more sense to automatically unregister any custom definitions when the Lua kernel is destroyed. (Which means that any definitions registered in the

[Wesnoth-bugs] [bug #25337] allow custom widget definitions in umc

URL: Summary: allow custom widget definitions in umc Project: Battle for Wesnoth Submitted by: gfgtdf Submitted on: Mi 23 Nov 2016 15:15:51 UTC Category: Feature Request