On Sunday, October 14, 2018 at 9:20:42 PM UTC-4, Alex Harsanyi wrote: > > > However, I don't think it is a good idea to create many widgets > dynamically in event callbacks, than just leave them around to be garbage > collected, which your example code does. In a real application, you should > consider: > > * create all widgets you need before the top-level frame or dialog is > shown, the widgets that don't need to be visible can be created with a > 'deleted style. You can than use change-children to add or remove widgets > as needed, to change the visual contents of the window as needed. > * for displaying tabular data, consider using a list-box% control, as it > supports multiple columns which can be shown/hidden. > > I was a little fuzzy on the 'deleted' status of controls and wasn't sure if that sort of thing would work. (I guess the docs are reasonably clear that this is an explicit status of children, but it's obfuscated by the fact that you can't read or set this status explicitly. Similarly, the naming of the "hidden" status compared to its manipulator, "show", is unfortunate.)
Although I'm an experienced programmer, I rarely work on user interfaces, so your suggestions are very welcome. Thanks! -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
