>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...
Yes... that's the exact problem we've got; one of our hacks is
misbehaving in such cases. And I rememeber checking the docs to make
sure that I was doing any necessary translation of coordinates, too!
>
> >...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?
Personally, I don't mind at all! First of all, it's easy to fix with
a global find/replace (assuming y'all have a text file quickly
explaining all parameter name changes). Secondly, I'm guessing that
lots of people have made this mistake, and if they recompile and it
doesn't work, well, what a perfect opportunity to fix a bug!
What do you think?
Ok, and for a fix for my hack, then if I want to check to see if the
pen is in the topLeft corner of the screen, then I should do this:
[ this is from memory, some exact API calls may be mangled or have
out-of-order params, but you get the point]
x=event->screenX;
y=event->screenY;
WinWindowToDisplayPt(&x, &y); // need to add this to make it work
always, right?
RctPtInRectangle(&r, x, y);
Thanks,
Alan Pinstein
Synergy Solutions, Inc.
http://www.synsolutions.com
1-800-210-5293
