RE: [wxperl-users] wxPerl "weirdness"

[Mattia B. <mb...@ds...>]

<replying to the list>
> Hi Mattia,
> 	Here's the example that I promised.  It's as simple as I can get
> it.  It's basically a skeleton of my app, but shows some odd behavior.
> I was able to get around some of the crashing.  I think that I needed 
to
> pay more attention to what ID's I was using.  But I don't really know
> much about what the ID's actually do, so I'm giving most of my stuff
> unique ID's.
They are just IDs ( identifiers ); in wxPerl you rarely need 
explicit identifires ( i.e. passing an id != -1 ), but in wxWindows
( C++ ) you can't do without them ( OK, you _could_ do, but it would
be impratical )

> 	Anyhow, the problems I'm getting with this code exist in the
> TextCTRL and the Listbox.  If you go to "file" "new" and create a 
bunch
> of tabs and compare the Listboxes on each tab, they have different
> properties, ranging from text boldness to the order in which things 
were
> inserted into the Listbox.  Also, you'll note that in some Listbox's 
the
> "wxLB_EXTENDED" feature works and on some it doesn't.  All the 
Listbox's
> on each tab *should* be the same from what I can see, since they're 
all
> created with the same "constructor".  The problem with the TextCTRL at
> the bottem only *seems* to exist on windows xp as it doesn't show up
> that I can remember on my win2k machine.  On XP, the default text 
shows
> up as *'s and not the actual text.
I had it on 2k, too, the problem is that you need to
combine flags using '|', not passing a list of them; i.e.
you do [wxLB_NEEDED_SB, wxLB_EXTENDED], but you must
do wxLB_NEEDED_SB|wxLB_EXTENDED

Regards
Mattia