The number of tree items returned by GetSelections() is not correct in all
situations. When selecting multiple items (holding shift key down)
then GetSelections() is not returning all selected items. If you select n items,
the returned list from GetSelections() is n-1 items long. The missing item is not
the first or last item in the tree. It is item n-1 which is missing !!
Example: If I select “item1, item2, item3, item4” then GetSelections() will
return "item1, item2, item4"
When deselecting tree items, everything is OK.
Sorry if the above is a bit unclear…
The reproduce the problem you can modify the TreeCtrl-DEMO by:
The number of tree items returned by GetSelections() is not correct in all
situations. When selecting multiple items (holding shift key down)
then GetSelections() is not returning all selected items. If you select n items,
the returned list from GetSelections() is n-1 items long. The missing item is not
the first or last item in the tree. It is item n-1 which is missing !!
Example: If I select “item1, item2, item3, item4” then GetSelections() will
return "item1, item2, item4"
When deselecting tree items, everything is OK.
Sorry if the above is a bit unclear…
The reproduce the problem you can modify the TreeCtrl-DEMO by:
On 6/1/07, Edgar Poth <epmlist@googlemail.com> wrote:
Hi,
The number of tree items returned by GetSelections() is not correct in all
situations. When selecting multiple items (holding shift key down)
then GetSelections() is not returning all selected items. If you select n items,
the returned list from GetSelections() is n-1 items long. The missing item is not
the first or last item in the tree. It is item n-1 which is missing !!
Example: If I select "item1, item2, item3, item4" then GetSelections() will
return "item1, item2, item4"
When deselecting tree items, everything is OK.
Sorry if the above is a bit unclear..
The reproduce the problem you can modify the TreeCtrl-DEMO by:
The number of tree items returned by GetSelections() is not correct in all
situations. When selecting multiple items (holding shift key down)
then GetSelections() is not returning all selected items. If you select n items,
the returned list from GetSelections() is n-1 items long. The missing item is not
the first or last item in the tree. It is item n-1 which is missing !!
Example: If I select “item1, item2, item3, item4” then GetSelections() will
return "item1, item2, item4"
When deselecting tree items, everything is OK.
Sorry if the above is a bit unclear…
The reproduce the problem you can modify the TreeCtrl-DEMO by:
OK have upgrade to wxPython 2.8.4.0 <http://2.8.4.0> but have still the same problem !
I also can't duplicate the problem using my current workspace version (2.8.4.1pre). The items don't always come in the order that I expect, but they are all there.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
OK have upgrade to wxPython 2.8.4.0 <http://2.8.4.0> but have still the
same problem !
I also can’t duplicate the problem using my current workspace version
(2.8.4.1pre). The items don’t always come in the order that I expect,
but they are all there.
–
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
I also can’t duplicate the problem using my current workspace version
(2.8.4.1pre). The items don’t always come in the order that I expect,
but they are all there.
–
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Aha, now I'm seeing it. I get proper behavior by using the mouse, but exactly what you describe when using the up/down keys.
Yep, me too.
Edgar, please enter a bug report about this with a category od "wxMSW Specific" and be sure to mention that this only happens with keyboard selection.
I will try tomorrow the same test on Linux.
It doesn't have this problem, but it does have the "feature" that child items within collapsed selected items are part of the selection list. I'm not sure if that should be considered a bug for wxMSW or for wxGTK...
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Frank Tobia wrote:
> Aha, now I'm seeing it. I get proper behavior by using the mouse, but
> exactly what you describe when using the up/down keys.
>
Yep, me too.
Edgar, please enter a bug report about this with a category od "wxMSW
Specific" and be sure to mention that this only happens with keyboard
selection.
>> I will try tomorrow the same test on Linux.
It doesn't have this problem, but it does have the "feature" that child
items within collapsed selected items are part of the selection list.
I'm not sure if that should be considered a bug for wxMSW or for wxGTK...
I remember someone pointed out in the past this last "bug" (feature?)
about CustomTreeCtrl, which has been fixed a while ago. I don't know
for sure about keyboard selection though... I have to try and see if
CustomTreeCtrl behaves strangely