I have to load about 5,000-10,000 values (maybe more) to a choice box at run time. It's a list that could keep growing....
The response time seems a little slower than I expected, considering how fast the other widgets seem to respond (maybe just my perception!?)
I've attached the code I am playing with - is there something I am doing wrong or is this just how fast I can expect this to be?
Thanks for your help!
Choice controls are really only meant to be used for holding up to a few dozen items. Putting that many in is way too much, and frankly quite unusable for the person that will be using the app to find the item in it. Should try to rethink how you are designing the ui. This issue is brought up on the list fairly often (to my memory anyhow), searching the archives might bring some more ideas.
I am rewriting an MS Access app in wxPython, and the client would like the screens to be very similar. The users asked for something like this, they think it’s usable…(see attached image)
I will search the archives, thanks. I would appreciate any suggestions!
I have to load about 5,000-10,000 values (maybe more) to a choice box at run time. It’s a list that could keep growing…
The response time seems a little slower than I expected, considering how fast the other widgets seem to respond (maybe just my perception!?)
I’ve attached the code I am playing with - is there something I am doing wrong or is this just how fast I can expect this to be?
Thanks for your help!
Choice controls are really only meant to be used for holding up to a few dozen items. Putting that many in is way too much, and frankly quite unusable for the person that will be using the app to find the item in it. Should try to rethink how you are designing the ui. This issue is brought up on the list fairly often (to my memory anyhow), searching the archives might bring some more ideas.
You could try making your own ChoiceList with wx.PopupWindow and
wx.ListCtrl(style = wxLC_VIRTUAL | wxLC_REPORT) Virtual list loads data as
scrollbar is used… this could be faster.
Mind that wx.PopupWindow will not work on Mac (should be
available in wxPython 2.9.* thought) (gtk and msw only).
I have to load about 5,000-10,000 values (maybe more) to a choice box at run
time. It’s a list that could keep growing…
The response time seems a little slower than I expected, considering how fast
the other widgets seem to respond (maybe just my perception!?)
I’ve attached the code I am playing with - is there something I am doing wrong
or is this just how fast I can expect this to be?
Thanks for your help!
Choice controls are really only meant to be used for holding
up to a few dozen items. Putting that many in is way too much, and frankly quite
unusable for the person that will be using the app to find the item in it.
Should try to rethink how you are designing the ui. This issue is brought up on
the list fairly often (to my memory anyhow), searching the archives might bring
some more ideas.
Cody
I am rewriting an MS Access app
in wxPython, and the client would like the screens to be very similar. The
users asked for something like this, they think it’s usable…(see attached
image)
I will search the archives, thanks. I would appreciate any suggestions!
You could try making your own ChoiceList with wx.PopupWindow and wx.ListCtrl(style = wxLC_VIRTUAL | wxLC_REPORT) Virtual list loads data as scrollbar is used… this could be faster.
Mind that wx.PopupWindow will not work on Mac (should be available in wxPython 2.9.* thought) (gtk and msw only).
Or make a custom popup for wx.combo.ComboCtrl.
But thousands of items in a control like that is still a bad idea from the UI and user experience perspective, so it would still be better to split it up somehow. For example, if the list could be divided into groups then there could be one choice or combo to select a group, which will then cause the next choice or combo to have that group's items loaded into it for selection, and so on for however many nested groups you can segment the items into.
If the items aren't groupable like that then there are other things that could be done.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
You could try making your own ChoiceList with wx.PopupWindow and wx.ListCtrl(style = wxLC_VIRTUAL | wxLC_REPORT) Virtual list loads data as scrollbar is used… this could be faster.
Mind that wx.PopupWindow will not work on Mac (should be available in wxPython 2.9.* thought) (gtk and msw only).
Or make a custom popup for wx.combo.ComboCtrl.
But thousands of items in a control like that is still a bad idea from the UI and user experience perspective, so it would still be better to split it up somehow. For example, if the list could be divided into groups then there could be one choice or combo to select a group, which will then cause the next choice or combo to have that group’s items loaded into it for selection, and so on for however many nested groups you can segment the items into.
If the items aren’t groupable like that then there are other things that could be done.
