Given the recent rash of odd dialog UI behavior, I did some digging and it appears that we might be abusing wxUpdateUIEvent[1]. This event handler was specifically designed for updating controls that respond to command events such as menus, toolbars, buttons, etc. Using them for anything else is risky. I would avoid using UI control object calls inside a wxUpdaetUIEvent handler other than those provided by the wxUpdateUIEvent object itself. I'm pretty sure making changes to a control inside a wxUpdateUIEvent handler can spawn an event loop where the changes made to the control generate a new wxUpdateUIEvent. A better solution might be to use wxIdleEvent to do any dialog control post processing as a one shot.
Cheers, Wayne [1]: https://docs.wxwidgets.org/3.0/classwx_update_u_i_event.html#aa25df58e7047f819f5dd0520eb2cc8ea _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
