> From the headers one would assume that event.screenX and
>event.screenY are DISPLAY-RELATIVE; however, someone has found a bug
>in one of our apps that leads me to think that they are actually
>WINDOW-RELATIVE. Looking at the sources seems to corroborate this...
And looking at the documentation might clarify it even more. :-) May I
quote, from the description of penDownEvent:
screenX Window-relative position of the pen in pixels...
>Also, does PenGetPoint/EvtGetPen return
>SCREEN-RELATIVE or WINDOW-RELATIVE coordinates?
Again, the docs are remarkably clear on this point. "pScreenX... x
location relative to display"
Don't feel too badly, though; last week I made the very same mistake when
working on a new feature in the rom! Took me a while to figure out why it
wasn't working when a non-full-screen dialog was up...
>...should these parameters be renamed to windowX/windowY to
>avoid future confusion?
Now that's a good question. It is easy for us to update those sorts of
things, but how much work are you willing to tolerate, when a new version
of the SDK changes things like this and thus forces you to change your code
in order to recompile?
-David Fedor
Palm Developer Support
