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. Brgds, Viktor On Fri, Mar 13, 2009 at 12:53 PM, Abeb <abe.b...@att.net> wrote: > > did you rebuild Harbour with the modified inkey.ch? > > > Viktor Szakáts wrote: > > > > Can't make it work here in a default Harbour build. > > Tried plain Inkey() and Inkey( 0, INKEY_ALL + INKEY_EXTENDED ). > > <Ctrl+A> always returnes 1. > > > > Brgds, > > Viktor > > > > On Thu, Mar 12, 2009 at 4:28 PM, AbeB <abe.b...@att.net> wrote: > > > >> > >> the K_CTRL_* are already implemented. I had cut the following from > >> xharbour's > >> setkey.ch into harbour's > >> and rebuild harbour, and it just works (in GTWVT). > >> > >> i don't know about K_SH_* key's > >> > >> in xharbour it's selected by #defining HB_EXT_INKEY when building > >> xharbour. > >> > >> > >> > >> Viktor Szakáts wrote: > >> > > >> > This would be good, especially since on certain GTs the number of > >> usable > >> > keys are scarce (no Alt+ combinations f.e.), so enabling these > >> > CTRL keys could certainly help on shortcut congestion. But users > should > >> > enable it explicitly by using INKEY_ flag to keep Clipper > >> compatibility. > >> > > >> > I don't know what it takes to implement it though. > >> > > >> > Brgds, > >> > Viktor > >> > > >> > On Sun, Mar 8, 2009 at 6:26 PM, AbeB <abe.b...@att.net> wrote: > >> > > >> >> > >> >> can the following be an option in inkey.ch ( it's from xHarbour) > >> >> > >> >> /* New control keys that do not overlap with other codes */ > >> >> > >> >> #define K_CTRL_A 513 /* Ctrl-A > >> >> */ > >> >> #define K_CTRL_B 514 /* Ctrl-B > >> >> */ > >> >> #define K_CTRL_C 515 /* Ctrl-C > >> >> */ > >> >> #define K_CTRL_D 516 /* Ctrl-D > >> >> */ > >> >> #define K_CTRL_E 517 /* Ctrl-E > >> >> */ > >> >> #define K_CTRL_F 518 /* Ctrl-F > >> >> */ > >> >> #define K_CTRL_G 519 /* Ctrl-G > >> >> */ > >> >> #define K_CTRL_H 520 /* Ctrl-H > >> >> */ > >> >> #define K_CTRL_I 521 /* Ctrl-I > >> >> */ > >> >> #define K_CTRL_J 522 /* Ctrl-J > >> >> */ > >> >> #define K_CTRL_K 523 /* Ctrl-K > >> >> */ > >> >> #define K_CTRL_L 524 /* Ctrl-L > >> >> */ > >> >> #define K_CTRL_M 525 /* Ctrl-M > >> >> */ > >> >> #define K_CTRL_N 526 /* Ctrl-N > >> >> */ > >> >> #define K_CTRL_O 527 /* Ctrl-O > >> >> */ > >> >> #define K_CTRL_P 528 /* Ctrl-P > >> >> */ > >> >> #define K_CTRL_Q 529 /* Ctrl-Q > >> >> */ > >> >> #define K_CTRL_R 530 /* Ctrl-R > >> >> */ > >> >> #define K_CTRL_S 531 /* Ctrl-S > >> >> */ > >> >> #define K_CTRL_T 532 /* Ctrl-T > >> >> */ > >> >> #define K_CTRL_U 533 /* Ctrl-U > >> >> */ > >> >> #define K_CTRL_V 534 /* Ctrl-V > >> >> */ > >> >> #define K_CTRL_W 535 /* Ctrl-W > >> >> */ > >> >> #define K_CTRL_X 536 /* Ctrl-X > >> >> */ > >> >> #define K_CTRL_Y 537 /* Ctrl-Y > >> >> */ > >> >> #define K_CTRL_Z 538 /* Ctrl-Z > >> >> */ > >> >> > >> >> /* extended shift key codes, none in Clipper */ > >> >> > >> >> #define K_SH_LEFT 424 /* * Shift-Left > >> >> */ > >> >> #define K_SH_UP 425 /* * Shift-Up > >> >> */ > >> >> #define K_SH_RIGHT 426 /* * Shift-Right > >> >> */ > >> >> #define K_SH_DOWN 427 /* * Shift-Down > >> >> */ > >> >> > >> >> #define K_SH_INS 428 /* * Shift-Ins > >> >> */ > >> >> #define K_SH_DEL 429 /* * Shift-Del > >> >> */ > >> >> #define K_SH_HOME 430 /* * Shift-Home > >> >> */ > >> >> #define K_SH_END 431 /* * Shift-End > >> >> */ > >> >> #define K_SH_PGUP 432 /* * Shift-PgUp > >> >> */ > >> >> #define K_SH_PGDN 433 /* * Shift-PgDn > >> >> */ > >> >> > >> >> #define K_SH_RETURN 434 /* * Shift-Enter > >> >> */ > >> >> #define K_SH_ENTER 434 /* * Shift-Enter > >> >> */ > >> >> > >> >> > >> >> -- > >> >> View this message in context: > >> >> > >> > http://n2.nabble.com/feature-request.-K_CTRL_*-should-not-overlap-with-other-codes-tp2445208p2445208.html > >> >> Sent from the harbour-devel mailing list archive at Nabble.com. > >> >> > >> >> _______________________________________________ > >> >> 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 > >> > > >> > > >> > >> -- > >> View this message in context: > >> > http://n2.nabble.com/feature-request.-K_CTRL_*-should-not-overlap-with-other-codes-tp2445208p2468019.html > >> Sent from the harbour-devel mailing list archive at Nabble.com. > >> > >> _______________________________________________ > >> 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 > > > > > > -- > View this message in context: > http://www.nabble.com/feature-request.-K_CTRL_*-should-not-overlap-with-other-codes-tp22400427p22494982.html > Sent from the Harbour - Dev mailing list archive at Nabble.com. > > _______________________________________________ > 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
