Bug in wxTreeCtrl under XP?

Hi,
Before I go to the trouble of producing an app demonstrating a possible bug, has anyone experienced this bug with tree control:

    AppendItem causes the new item to become the FIRST child.

        and

    The new first child may be assigned the same number of children as the following item, but they will take the names of its SIBLINGS.
    (And other bizarre, but similar, behavior - but you can get the idea from this description.)
    
This behavior seems to have surfaced after I started developing on XP.

At the moment, for a work around I will rebuild the tree when something is added.

Environment:
  Windows XP
  Python version (2, 2, 1, 'final', 0)
  wxPython version 2.3.3.1
-Rick King
Southfield MI

Rick King wrote:

Hi, Before I go to the trouble of producing an app demonstrating a
possible bug, has anyone experienced this bug with tree control:

AppendItem causes the new item to become the FIRST child.

and

The new first child may be assigned the same number of children as
the following item, but they will take the names of its SIBLINGS. (And other bizarre, but similar, behavior - but you can get the idea
from this description.)

This behavior seems to have surfaced after I started developing on
XP.

I havn't seen it. Does it do it in the demo for you?

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!