Although it seems like a legitimate question–why should it freeze with too many textctrls? (and I don’t have the answer)–I have to always ask why people want to put hundreds of any object (but particularly textCtrls) on one screen. It just doesn’t seem like good UX at all. Maybe I’m missing something.
Although it seems like a legitimate question--why should it freeze with
too many textctrls?
Perhaps a better question is why shouldn't it freeze, or at least be very very slow? With 5 widgets per row in the sample code the system has to deal with 2500 widget handles, plus the overhead of 2500 instances of the C++ and Python classes, plus paint events and DCs and drawing of backgrounds, border lines and text for 100 or so widgets at a time as the window is scrolled or resized or damaged by other windows, plus data allocations for the values and fetching the values from memory, plus each of those 2500 widgets will be sending events like EVT_SIZE, EVT_TEXT, and several others, etc.
(and I don't have the answer)--I have to always ask
why people want to put hundreds of any object (but particularly
textCtrls) on one screen. It just doesn't seem like good UX at all.
Maybe I'm missing something.
If you listen very carefully you can hear the sample application crying and whimpering things like, "This is so hard, why didn't you use a wx.grid.Grid?" "Please, please, can I have a Grid? I won't ask for anything else ever." "If you really liked me you would upgrade your wxPython and use a DataViewCtrl."
