Hi, > As far as I understand that would be very desirable because any > workaround on application level counteract the cc65 maxim of target > independence. Based on your hints I played around somewhat more and found that moving the mouse while pressing the primary mouse button can generate the phantom keycode 62 which maps to the char '>'. In contrast to the keycode 160 this is a "useful" keycode necessary to be entered. Therefore I don't see any workaround possible on application level :-(( Maybe I'm exaggerating but from my current perspective the C64 mouse support in cc65 is sort of broken. Best, Oliver ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Sun Jan 31 11:14:35 2010
This archive was generated by hypermail 2.1.8 : 2010-01-31 11:14:38 CET