Advice from Andre Garzia:
I have no problem with that and I use it here as well. Just do a visual
feedback like this:
on rawKeydown, check for the altKey and change all the labels of the
buttons for the
actions they will perform if that key is down, this way, as soon as
someone presses ALT,
If you are using alt as a modifier:
on rawKeyDown
if altKey() = down then
-- do some stuff
end if
end rawKeyDown
If you just want to detect the alt key, one option could be to use the
idle message which essentially acts as a loop:
[ card or stack script ]
on idle
if altKey() = down
If I have this sort of script in my stack:
on rawKeydown
if altKey() = down then
put ALT down into fld AKD
end if
end rawKeydown
on Macintosh that ONLY WORKS if I am pressing an alphanumeric key while
holding the altKey down,
it DOES NOT work if all I do is press the altKey.
Now,
Late to this discussion but.. Polling (or maybe an external?) is the only
real solution for this problem right?
On Sun, Dec 2, 2012 at 7:59 AM, Richmond richmondmathew...@gmail.comwrote:
If I have this sort of script in my stack:
on rawKeydown
if altKey() = down then
put ALT down
On 12/02/2012 05:30 PM, Mike Bonner wrote:
Late to this discussion but.. Polling (or maybe an external?) is the only
real solution for this problem right?
Polling the key downs is possible, but will slow down
a program considerably.
___
Use idle as scott said? Or, if you don't need it to be super responsive. IE
you're using visual cues as andre suggested, then polling every 100 or 150
milliseconds might suffice. Idle is probably easiest. Was wondering about
the external, seems that since this is related to os/arch even an
On 12/02/2012 05:58 PM, Mike Bonner wrote:
Use idle as scott said? Or, if you don't need it to be super responsive.
My Devawriter does have to be 'super responsive' as it is, ultimately, a
glorified typewriter,
and as such should, in an ideal situation, work not much more slowly
than the
Yeah, too true. And if others are like me, having to wait for things to
catch up is really annoying!
Well, this is only osx (objective c) and I'm clueless about it, but the
example on this page might give someone who isn't a clueless c nub like me
a chance to build an external to catch key
On 12/02/2012 07:02 PM, Mike Bonner wrote:
Yeah, too true. And if others are like me, having to wait for things to
catch up is really annoying!
Well, this is only osx (objective c) and I'm clueless about it, but the
example on this page might give someone who isn't a clueless c nub like me
a
On Macintosh, according to Apple's documentation the key code for
the left option key is 98 and 58 for the right option key.
There is a school of thought flying around that the key code for both is 35.
However . . . keysDown doesn't work for modifier keys on Mac . . .
interestingly enough
I remembered something about updateScreen on the Game Academy, they used
dispatch to poll the stack for a screen refresh and it didn't seem to have too
much detrimental effect on the game, I had a quick look, took out the bones and
tried this…
on preOpenStack
if the platform is MacOS then
On 11/30/2012 09:04 AM, Richmond wrote:
On 30/11/12 08:56, Richmond wrote:
On 30/11/12 08:33, Richmond wrote:
Has anybody any bright ideas why this doesn't work:
on mouseUp
if altkey() is down then
put ALT key is down into fld fOUTPUT
end if
end mouseUp
or this:
on mouseUp
if
Is it just me, or . . . ?
So, here I am, during my luch break, at home, AND . . .
having had No joy with this on my G3 iMac running Mac OS 10.4 at the
school:
on mouseUp
if the altKey is down then
put down into fld fOUTPUT
end if
end mouseUp
it works on MacINTEL 10.6.7 !
but
On 11/30/12 5:20 AM, Richmond wrote:
Is it just me, or . . . ?
So, here I am, during my luch break, at home, AND . . .
having had No joy with this on my G3 iMac running Mac OS 10.4 at the
school:
on mouseUp
if the altKey is down then
put down into fld fOUTPUT
end if
end mouseUp
On 30/11/12 19:47, J. Landman Gay wrote:
On 11/30/12 5:20 AM, Richmond wrote:
Is it just me, or . . . ?
So, here I am, during my luch break, at home, AND . . .
having had No joy with this on my G3 iMac running Mac OS 10.4 at the
school:
on mouseUp
if the altKey is down then
put
On 11/30/12 11:52 AM, Richmond wrote:
Nothwithstanding the above, I do wonder why Livecode-on-Mac cannot grab
onto rawKeyDownsfor modifier keys.
As I understand it, the OS doesn't send any key messages until the combo
is typed. I believe it's always been that way on Macs; at least, I
recall
On 11/30/2012 10:38 PM, J. Landman Gay wrote:
On 11/30/12 11:52 AM, Richmond wrote:
Nothwithstanding the above, I do wonder why Livecode-on-Mac cannot grab
onto rawKeyDownsfor modifier keys.
As I understand it, the OS doesn't send any key messages until the
combo is typed. I believe it's
Has anybody any bright ideas why this doesn't work:
on mouseUp
if altkey() is down then
put ALT key is down into fld fOUTPUT
end if
end mouseUp
or this:
on mouseUp
if the altkey is down then
put ALT key is down into fld fOUTPUT
end if
end mouseUp
on Linux?
'Tisn't
On 30/11/12 08:33, Richmond wrote:
Has anybody any bright ideas why this doesn't work:
on mouseUp
if altkey() is down then
put ALT key is down into fld fOUTPUT
end if
end mouseUp
or this:
on mouseUp
if the altkey is down then
put ALT key is down into fld fOUTPUT
end if
On 30/11/12 08:56, Richmond wrote:
On 30/11/12 08:33, Richmond wrote:
Has anybody any bright ideas why this doesn't work:
on mouseUp
if altkey() is down then
put ALT key is down into fld fOUTPUT
end if
end mouseUp
or this:
on mouseUp
if the altkey is down then
put ALT
20 matches
Mail list logo
