Hi,
I think there are two more problems in the last interim release:
- When you redefine the OnLinkClicked event for a wxHtmlWindow,
and you want to access the link argument (where you can see
the contents of the link you clicked on), you only get a
reference to that object, and not the contents of it.
- Apparently, when you redefine the icon for your application in
Windows, wxPython scales down the 32x32 pixel one to 16x16
pixels instead of taking the 16x16 pixel version that is in the
.ico file. This makes your icons look really muddy.
Kind regards,
Pieter
Pieter Claerhout -
[hidden email]
Response Center - Applications Support
Creo Europe - Excelsiorlaan 21 - 1930 Zaventem - Belgium
Tel: +32 (2) 711 14 00 - Fax: +32 (2) 720 96 71
-----Original Message-----
From: Robin Dunn [mailto:
[hidden email]]
Sent: Thursday, January 06, 2000 8:14 AM
To:
[hidden email];
[hidden email]
Subject: Re: [wxPython] Oops List for wxPython-2_1_11-20000102
>
> Here are a few problems that I noticed in the latest interim release when I
> went through the demo:
>
> 1) wxButton: icon is missing from the button
It also does it on win98, but not NT...
> 2) wxTreeCtrl: problem with icon spacing
Can you be more specific, or send me a screen shot?
> 3) wxRadioBox: Background colour is now white
I'm glad somebody else has seen this. The wxwindows guys think I am nuts.
> 4) Sizers: text on tree and scrolled list goes gray when "try it" button is
> activated
This is because the frame with the sizers is made modal, and that is how a
disabled tree control looks.
> 5) wxFloatBar: when floating buttons can not be seen and it does not dock
> back into the window
I fixed this today. Something weird was going on with wxWindow::SetSize
(renamed to SetPosition for wxPython.) So I fixed that and most of the
floatbar's problems went away. I tweaked a couple other things too. Now if
I can just figure out how to make it work better for wxGTK...
> 6) GenericButtons: some of the buttons overlap a bit
>
Do you have larger than normal fonts? The demo uses brute force positioning
so font sizes could screw it up.
--
Robin Dunn
Software Craftsman
[hidden email]
http://AllDunn.com/robin/http://AllDunn.com/wxPython/ Check it out!
_______________________________________________
wxPython-users maillist -
[hidden email]
http://starship.python.net/mailman/listinfo/wxpython-users_______________________________________________
wxPython-users maillist -
[hidden email]
http://starship.python.net/mailman/listinfo/wxpython-users