Re: [Harbour] inkey(0) and set key to

2010-03-26 Thread Qatan
ncesco perillo" To: "Harbour Project Main Developer List." Sent: Friday, 26 de March de 2010 16:07 Subject: Re: [Harbour] inkey(0) and set key to You can use setkey with one parameter ( the inkey(0) return value) to check if a codeblock is associated and then invoke it with correct

Re: [Harbour] inkey(0) and set key to

2010-03-26 Thread francesco perillo
You can use setkey with one parameter ( the inkey(0) return value) to check if a codeblock is associated and then invoke it with correct parameters... something like this nCode := inkey( 0 ) (check nCode) cBlock := setkey ( nCode ) if cBlock Eval( cBlock, procfile(1), procname(1), procline(1)

[Harbour] inkey(0) and set key to

2010-03-26 Thread harbour-list
hi, inkey(0) does not honour "set key to" settings. i guess that is by design, at least it was the same in clipper S87. we had found some assembler way around that, but that won't do for harbour. is there any way to enable the key mappings with an inkey(0) like function? any other function to

Re: [Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Viktor Szakáts
Hi Przemek, > > K_MDBCLK is randomly generated while keeping the middle button > > pressed and moving the mouse, with GTXWC. This may count as a bug. > > I've just tested it using tests/gtkeys and it works correctly just > like LEFT and RIGHT buttons. I tested it with GTXWC and GTTRM and > PTerm

Re: [Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Przemyslaw Czerpak
On Tue, 17 Feb 2009, Szak�ts Viktor wrote: Hi Viktor, > K_MDBCLK is randomly generated while keeping the middle button > pressed and moving the mouse, with GTXWC. This may count as a bug. I've just tested it using tests/gtkeys and it works correctly just like LEFT and RIGHT buttons. I tested it

Re: [Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Viktor Szakáts
Hi Pritpal, > The behavior of K_MBUTTONDOWN, K_MBUTTONUP, K_MDBLCLK is exactly > > as it should be and it's the same as K_[LR]BUTTONDOWN, K_[LR]BUTTONUP > > and K_[LR]DBLCLK in GTXWC and CL53. If you used some GT dirver which > > does not work like CL53 then it should be fixed. > > > > I had intro

Re: [Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Viktor Szakáts
Hi Przemek and all, About K_NCMOUSEMOVE: Added here to xhb: 2004-07-21 16:45 UTC+0530 Pritpal Bedi It will generate these events while hovering with the mouse over non-client area of the GTWVT window, most notable the title bar. This can explain some strange behaviour I've seen while developing

Re: [Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Pritpal Bedi
Hi Przemyslaw Czerpak-2 wrote: > > I do not know what is K_MMLEFTDOWN, K_MMRIGHTDOWN, K_MMMIDDLEDOWN > and K_NCMOUSEMOVE. It's Harbour extension and I've never seen any > description for this inkey mouse value. I thought that the first > 3 ones describes some extended mouse buttons but I do not

Re: [Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Viktor Szakáts
Hi Przemek, > I do not know what is K_MMLEFTDOWN, K_MMRIGHTDOWN, K_MMMIDDLEDOWN > and K_NCMOUSEMOVE. It's Harbour extension and I've never seen any > description for this inkey mouse value. I thought that the first 3 ones describes some extended mouse buttons but I do not have it. > Clipper does

Re: [Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Przemyslaw Czerpak
On Tue, 17 Feb 2009, Szak�ts Viktor wrote: Hi Viktor, > There seem to be some problems with mouse handling in GTXWC: > - When left clicking and dragging, instead of K_MMLEFTDOWN, > K_MOUSEMOVE gets generated. > - When middle clicking and dragging, instead of K_MMMIDDLEDOWN, > a mixture of K_MBUTT

[Harbour] Inkey() problem with GTXWC + mouse

2009-02-17 Thread Viktor Szakáts
Hi all, There seem to be some problems with mouse handling in GTXWC: - When left clicking and dragging, instead of K_MMLEFTDOWN, K_MOUSEMOVE gets generated. - When middle clicking and dragging, instead of K_MMMIDDLEDOWN, a mixture of K_MBUTTONDOWN, K_MBUTTONUP, K_MDBLCLK events are generated. Br

Re: [Harbour] inkey() & HB_K_RESIZE % SET(_SET_EVENTMASK, INKEY_KEYBOARD )

2009-02-12 Thread Viktor Szakáts
The easiest solution is to turn off resize while you're waiting for input, so you won't receive any events. hb_GTInfo( HB_GTI_RESIZEMODE, HB_GTI_RESIZEMODE_FONT ) This is the default for GTWVT. Brgds, Viktor On Thu, Feb 12, 2009 at 5:33 PM, Abeb wrote: > > GTWVT. > Please make is so it should

Re: [Harbour] inkey() & HB_K_RESIZE % SET(_SET_EVENTMASK, INKEY_KEYBOARD )

2009-02-12 Thread Abeb
GTWVT. Please make is so it should honor EVENTMASKs. programs waiting at inkey(0) just continue if the screen was resized before. Thanks Abe Pritpal Bedi wrote: > > Abeb > > > Abeb wrote: >> >> is it possible that even if SET(_SET_EVENTMASK, INKEY_KEYBOARD ) is used >> inkey() will retur

Re: [Harbour] inkey() & HB_K_RESIZE % SET(_SET_EVENTMASK, INKEY_KEYBOARD )

2009-02-11 Thread Pritpal Bedi
Abeb Abeb wrote: > > is it possible that even if SET(_SET_EVENTMASK, INKEY_KEYBOARD ) is used > inkey() will return HB_K_RESIZE (1101)? > Which GT? GTWVT ? HB_K_RESIZE is not honoring EVENTMASKs. Any practical reason you want to disable it? Regards Pritpal Bedi -- View this message in

[Harbour] inkey() & HB_K_RESIZE % SET(_SET_EVENTMASK, INKEY_KEYBOARD )

2009-02-11 Thread AbeB
is it possible that even if SET(_SET_EVENTMASK, INKEY_KEYBOARD ) is used inkey() will return HB_K_RESIZE (1101)? -- View this message in context: http://n2.nabble.com/inkey%28%29---HB_K_RESIZE-SET%28_SET_EVENTMASK%2C-INKEY_KEYBOARD-%29-tp2312362p2312362.html Sent from the harbour-devel mai

Re: [Harbour] inkey

2008-06-22 Thread Enrico Maria Giordano
-Messaggio Originale- Da: "George Frehner" <[EMAIL PROTECTED]> A: "Harbour Project Main Developer List." Data invio: sabato 21 giugno 2008 19.54 Oggetto: [Harbour] inkey Hi developers, I made this little test because I was getting 100% CPU usage in so

[Harbour] inkey

2008-06-21 Thread George Frehner
Hi developers, I made this little test because I was getting 100% CPU usage in some old code when using RC1 (rev 8779) and BCC55 on Windows XP. In xharbour I did not get 100% CPU. The help file says the granularity of inkey() is 1/10 of a second. Should be 1/100? The loop below does not run if