yslaw Czerpak
> Sent: Friday, March 13, 2009 3:00 PM
> To: Harbour Project Main Developer List.
> Subject: Re: [Harbour] feature request. K_CTRL_* should not overlap with
> other codes
>
> On Fri, 13 Mar 2009, Szak�ts Viktor wrote:
>
> Hi,
>
> > No. IMO, if we need to
[mailto:harbour-boun...@harbour-project.org] On Behalf Of Przemyslaw Czerpak
Sent: Friday, March 13, 2009 3:00 PM
To: Harbour Project Main Developer List.
Subject: Re: [Harbour] feature request. K_CTRL_* should not overlap with other
codes
On Fri, 13 Mar 2009, Szak�ts Viktor wrote:
Hi,
> No. IMO, if
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 wrote:
> On Fri, 13 Mar 2009,
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
>
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
s
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 ).
> always returnes 1.
>
> Brgds,
> Viktor
>
> On Thu, Mar 12, 2009 at 4:28 PM, AbeB wrote:
>
>>
Can't make it work here in a default Harbour build.
Tried plain Inkey() and Inkey( 0, INKEY_ALL + INKEY_EXTENDED ).
always returnes 1.
Brgds,
Viktor
On Thu, Mar 12, 2009 at 4:28 PM, AbeB wrote:
>
> the K_CTRL_* are already implemented. I had cut the following from
> xharbour's
> setkey.ch into
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:
>
> Thi
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
