I've been working on bug 819
(http://bugs.plkr.org/bug_view_page.php?bug_id=819). On the Acer S60, pen
events aren't getting translated correctly to native coordinates. The cvs
code does the translation by:
EvtGetPenNative( WinGetActiveWindow(), &( event->screenX ),
&( event->screenY ), &( event->penDown ) );
which is the right way to do it. However, this doesn't seem to work on the
S60, though it works everywhere else. What does work is to change the code
just to double event->screenX and event->screenY. Unfortunately, doing that
will break all future hi-res devices that don't use 144dpi. So this isn't
an option. It is looking to me like the S60 fails to implement
EvtGetPenNative() correctly.
If so, then we need a hardware-specific workaround. The workaround is
easy--just double the coordinates. However, I don't know how to detect the
S60 (and S50, too). Any ideas? The Acer website has pulled its developer
info. I recall coming across some information on detecting the Acer
yesterday on the web while doing some google search, but I can't find that
information any more. Maybe other googlers will have more luck?
Alex
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online papers and home page: www.georgetown.edu/faculty/ap85
--------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
