mrhattyhat
01-21-2008, 02:35 AM
I know much has been said and written (and lamented) about comboboxes and datacomboboxes, and I've gone through all that (well, most of it). So here's my issue:
A basic application, two datacomboboxes: one for states (all states and territories in the US, total of 59), the other for cities which gets populated by a dataset that is called when the state is chosen. The result is a list of cities in the chosen state. Needless to say, in some cases this is a pretty large list.
For states like Delaware it works ok, but for large states like California, the cities list actually does load moderately fast, but here's where it sticks. Once the list is loaded and I make a choice, the entire app freezes. I can't click any buttons after that, I can't change tabs (the lists are inside a tabpane), I just have to wait for the dreaded "run slowly" warning to pop up.
Questions:
1- Why does the app choke AFTER the list is already loaded?
2- Is there a better component I should be using for this kind of thing, or alternatively, is there some way to tune the datacombobox for better performance (i.e. some way to force the app to release resources that it used building the list or something)?
A basic application, two datacomboboxes: one for states (all states and territories in the US, total of 59), the other for cities which gets populated by a dataset that is called when the state is chosen. The result is a list of cities in the chosen state. Needless to say, in some cases this is a pretty large list.
For states like Delaware it works ok, but for large states like California, the cities list actually does load moderately fast, but here's where it sticks. Once the list is loaded and I make a choice, the entire app freezes. I can't click any buttons after that, I can't change tabs (the lists are inside a tabpane), I just have to wait for the dreaded "run slowly" warning to pop up.
Questions:
1- Why does the app choke AFTER the list is already loaded?
2- Is there a better component I should be using for this kind of thing, or alternatively, is there some way to tune the datacombobox for better performance (i.e. some way to force the app to release resources that it used building the list or something)?