Dear list,
Is it intended behaviour that the wxEvent GetX() and GetY() return
invalid values in the EVT_CHAR handler? In wxPython 2.4.2.4, these
return valid and correct values (probably cached), but in wxPython
2.6, I get things like:
-1073753836, 1088743278
After some furious mousing and clicking, I get:
143065860, 1088743278
Any information would be greatly appreciated.
Thanks,
Charl
···
--
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/
URP, sorry about that. This is with:
wxPython 2.6.0.1 (built from source) on Debian 3.0 and libgtk 2.2.4
···
On 5/31/05, Robin Dunn <robin@alldunn.com> wrote:
Charl P. Botha wrote:
> Is it intended behaviour that the wxEvent GetX() and GetY() return
> invalid values in the EVT_CHAR handler? In wxPython 2.4.2.4, these
> return valid and correct values (probably cached), but in wxPython
> 2.6, I get things like:
> -1073753836, 1088743278
>
> After some furious mousing and clicking, I get:
> 143065860, 1088743278
Which platform?
--
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/