Hi Przemek, Sounds great as is. We should probably use a structure instead of trying to make everything fit into 32 bits. If this isn't causing a big speed penalty of course, but it doesn't seem so.
Brgds, Viktor On Fri, Mar 13, 2009 at 1:59 PM, Przemyslaw Czerpak <dru...@acn.waw.pl>wrote: > On Fri, 13 Mar 2009, Szak�ts Viktor wrote: > > Hi, > > > No. IMO, if we need to redefine Clipper compatible keycodes and do a > local > > build just to access these keys, the solution is > > wrong. > > I imagine a proper solution would look like adding a new > > INKEY_ filter/modifier, new HB_K_CTRL_x keys with > > alternate values, and this way the feature could be easily > > selected at runtime. In it's current form, it's pretty much > > unsuited for general consumption and users have to choose > > between Clipper compatibility and this feature at build time. > > This feature is quite important, so I hope to hear other > > opinions on how to implement this properly in Harbour. > > It has to be runtime switch but IMO we should change cursor key > values not K_CTLR_<letter> ones. > It's a common standard that CTRL+<letter> should return > ASC( <letter> ) - 64 on ASCII based machine. Lot of code depends > on it. > The other way is adding key modifiers to return values as bit field > for CTRL, SHIFT, ALT, ALTGR flags though here I see one potential > problem with defining portable list of basic key codes and interactions > with national characters. So we probably should add also bits to mark > type of keycode, f.e. ASCII character, UNICODE character, MOUSE event, > SCANCODE. > The mouse event should contain also the status of mouse buttons and > mouse row/col position. > It may be hard to keep all this information in single 32bit word > though it's possible if we reduce maximal size of GT window for > mouse position to 256 x 256. > The low level GT driver should send to core GT such row untranslated > event values. INKEY() will make translation online unless user will > not set some INKEY_RAW or INKEY_EXT flag. > That's all. > > best regards, > Przemek > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
