At 18:36 2003-04-07 +0200, Aldo Calpini wrote:
so, if you found any bug, please submit them *now*!
This all goes for 0.0.558, some things may be fixed.
When using Win32::GUI::DoEvents instead of Win32::GUI::Dialog, pressing a
key will result in two characters in an input field (and possibly other
controls). This is unfortunately a showstopper for some applications that
need it's own main loop.
(this is a very bad bug report) TabStrips aren't always displayed properly
when there are other controls on top of them and after the TabStrip
tab-order-wise.
(this too) When scrolling a RichEdit, the display sometimes has left-over
pixels.
When dragging a Resizer, the height/position is wrong if it doesn't cover
the entire height of the window.
Generally, I miss a lot of events, but I have no specifics :)
Pressing Tab from within a RichEdit doesn't move focus to the next control.
Pressing Ctrl-Tab doesn't change the selected tab to the next tab in a
TabStrip, and I don't think shortcut keys work either.
/J
-------- ------ ---- --- -- -- -- - - - - -
Johan Lindström Sourcerer @ Boss Casinos [EMAIL PROTECTED]
Latest bookmark: "Agility Test"
http://www.c2.com/cgi/wiki?AgilityTest
dmoz (1 of 9): /Computers/Hardware/Peripherals/Displays/ 34
