Re: Keypress Help - Solution
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 But not necessarily for the mouse ;-) On Apr 20, 2005, at 12:56 AM, sims wrote: Doing the above will also be therapeutic for you. Frank D. Engel, Jr. <[EMAIL PROTECTED]> $ ln -s /usr/share/kjvbible /usr/manual $ true | cat /usr/manual | grep "John 3:16" John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. $ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCZkdz7aqtWrR9cZoRAoqkAJ9Mmr5moj5vvahE03qpmKLFdsxTCACdHVjt v43Cp+ukbfmfxGgLagBAHKE= =WQ3w -END PGP SIGNATURE- ___ $0 Web Hosting with up to 200MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help - Solution
Recently, J. Landman Gay wrote: On a whim, I replaced the keyboard (which apparently works fine) on the XP machine, and the keysDown function now works. [sigh] It's the old "Machines Rise Up and Rebel Against Humanity" conspiracy. Be afraid. Funny that you said this. A little while after I replaced the keyboard, a wireless mouse connected to a completely different system on the far side of the desk decided to stop working. Reset didn't work, unplug/replug didn't work, it just decided to stop working. I am afraid. Keyboard Exorcism is your only course of action...then smash with a big hammer...then apply large blow torch if possible...if torch is not an alternative place keyboard in a bathtub until it drowns. Doing the above will also be therapeutic for you. ciao, sims ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help - Solution
Recently, J. Landman Gay wrote: >> On a whim, I replaced the keyboard (which apparently works fine) on the XP >> machine, and the keysDown function now works. [sigh] > > It's the old "Machines Rise Up and Rebel Against Humanity" conspiracy. > Be afraid. Funny that you said this. A little while after I replaced the keyboard, a wireless mouse connected to a completely different system on the far side of the desk decided to stop working. Reset didn't work, unplug/replug didn't work, it just decided to stop working. I am afraid. Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help - Solution
On 4/19/05 5:25 PM, Scott Rossi wrote: On a whim, I replaced the keyboard (which apparently works fine) on the XP machine, and the keysDown function now works. [sigh] It's the old "Machines Rise Up and Rebel Against Humanity" conspiracy. Be afraid. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help - Solution
On Apr 19, 2005, at 4:25 PM, Scott Rossi wrote: The solution: get a new keyboard. LOL! -- Dar ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Keypress Help - Solution
>> How can one reliably tell on Windows when a key is pressed versus when >> it is released? > No two Windows OS machines behave alike, no matter > how hard you try... many computer labs are > the true proof. The solution: get a new keyboard. On a whim, I replaced the keyboard (which apparently works fine) on the XP machine, and the keysDown function now works. [sigh] Many thanks to folks who offered alternate script solutions and who verified behavior of the test stack on Windows -- this helped me track down the problem. Best Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 There are areas in which no two installation of the SAME Windows version seem to behave alike. Can't think of a specific one atm, but I do remember having seen differences in behavior from two (virtually identical) computers (the same model, with essentially the same hardware -- same video card, network card, and so on), having had Windows installed from the same installation media using the same settings (when working in a college computer lab having a network/site license of some sort, of course). On Apr 19, 2005, at 2:17 PM, Dar Scott wrote: On Apr 19, 2005, at 8:04 AM, Alejandro Tejada wrote: No two Windows OS machines behave alike, no matter how hard you try... many computer labs are the true proof. Rats. And I thought Scott could use my counter solution. Well, Scott, if you have to do it by cases, the D DU DU DU DU U behavior I saw was on XP sp1? and Rev 2.5. Dar -- ** DSC (Dar Scott Consulting & Dar's Lab) http://www.swcp.com/dsc/ A Sponsor of RevCon West ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution - --- Frank D. Engel, Jr. <[EMAIL PROTECTED]> $ ln -s /usr/share/kjvbible /usr/manual $ true | cat /usr/manual | grep "John 3:16" John 3:16 For God so loved the world, that he gave his only begotten Son, that whosoever believeth in him should not perish, but have everlasting life. $ -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (Darwin) iD8DBQFCZVFR7aqtWrR9cZoRArgdAJ42OTq874fEKPiacm7LxZ44IPwAYgCfbrq/ IJuo4n/rhS9v52+UJ5to7HU= =XK6X -END PGP SIGNATURE- ___ $0 Web Hosting with up to 200MB web space, 1000 MB Transfer 10 Personalized POP and Web E-mail Accounts, and much more. Signup at www.doteasy.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
On Apr 19, 2005, at 8:04 AM, Alejandro Tejada wrote: No two Windows OS machines behave alike, no matter how hard you try... many computer labs are the true proof. Rats. And I thought Scott could use my counter solution. Well, Scott, if you have to do it by cases, the D DU DU DU DU U behavior I saw was on XP sp1? and Rev 2.5. Dar -- ** DSC (Dar Scott Consulting & Dar's Lab) http://www.swcp.com/dsc/ A Sponsor of RevCon West ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
Recently, Alejandro Tejada wrote: > All keys detected, even 3 or 4 keys pressed at > the same time. if i press 4 keys and lift 2 of > these keys, the field changes to reflects this. Thanks for the response. Several folks have reported key detection is working fine so now I need to try to discern why my machine is not producing the same results. Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
Recently, Mark Wieder wrote: > Works fine for me on Win2k, rev 2.5.1. Does your target machine have > some weird setting in the BIOS, like no delay before starting an > automatic key repeat? Thanks for the confirmation. I've tried messing around with key repeat settings but still haven't seen any change. I'll keep playing with it. Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
Scott- Monday, April 18, 2005, 5:06:10 PM, you wrote: SR> Does this work for you on Windows (or anyone else for that matter)? Works fine for me on Win2k, rev 2.5.1. Does your target machine have some weird setting in the BIOS, like no delay before starting an automatic key repeat? -- -Mark Wieder [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
on Windows 98 SE, All keys detected, even 3 or 4 keys pressed at the same time. if i press 4 keys and lift 2 of these keys, the field changes to reflects this. This confirm something i suspect time ago. No two Windows OS machines behave alike, no matter how hard you try... many computer labs are the true proof. al Visit my site: http://www.geocities.com/capellan2000/ __ Do you Yahoo!? Plan great trips with Yahoo! Travel: Now over 17,000 guides! http://travel.yahoo.com/p-travelguide ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
On 4/18/05 7:06 PM, Scott Rossi wrote: Recently, J. Landman Gay wrote: How can one reliably tell on Windows when a key is pressed versus when it is released? Are you sure you don't have your operating systems backwards? ;) In my experience, it has always been Mac OS that doesn't generate accurate keyUp messages. Windows has always worked for me. That is an OS limitation, as Macs send keyup immediately after keydown, regardless of the physical state of the key itself. Or at least, that's how it has always been in the past. Thanks for the response Jacque. But I wonder if you might be thinking about OS9. OSX works great for me. Seems to work for me too, so it must have been OS 9. It's been a few years since I had to use this. When I run the following simple test stack on MacOS, it works as expected: go url "http://www.tactilemedia.com/download/keytracker.rev"; Enable the test button and press one/some keys. The pressed keys are shown and [empty] is displayed when nothing is pressed. When this is run on WindowsXP, I get a mostly empty result, that flickers between the pressed keys and [empty]. The keysDown function is apparently not working because it doesn't seem to reliably return the keys that are pressed (my understanding is the keysDown function was originally designed to get around this whole key detection problem). Does this work for you on Windows (or anyone else for that matter)? Wish I could test it on Windows for you, but my Windows machine is unavailable for a few weeks. But someone else said it worked in WinXP -- which is weird, if it isn't working on your machine. Could your machine have caught a virus/keylogger (or would that even interfere?) Or do you have some macro thing installed, or anything? Thanks & Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
And of course those keys which remove the hilite from the btn Space and Return. - Original Message - From: "Pat Trendler" <[EMAIL PROTECTED]> To: "How to use Revolution" Sent: Tuesday, April 19, 2005 10:23 AM Subject: Re: Keypress Help Win XP Pro SP2 etc All keys detected except those you wouldn't expect to detect: Power, Sleep and WakeUp. Pat - Original Message - From: "Scott Rossi" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 19, 2005 10:06 AM Subject: Re: Keypress Help Recently, J. Landman Gay wrote: How can one reliably tell on Windows when a key is pressed versus when it is released? Are you sure you don't have your operating systems backwards? ;) In my experience, it has always been Mac OS that doesn't generate accurate keyUp messages. Windows has always worked for me. That is an OS limitation, as Macs send keyup immediately after keydown, regardless of the physical state of the key itself. Or at least, that's how it has always been in the past. Thanks for the response Jacque. But I wonder if you might be thinking about OS9. OSX works great for me. When I run the following simple test stack on MacOS, it works as expected: go url "http://www.tactilemedia.com/download/keytracker.rev"; Enable the test button and press one/some keys. The pressed keys are shown and [empty] is displayed when nothing is pressed. When this is run on WindowsXP, I get a mostly empty result, that flickers between the pressed keys and [empty]. The keysDown function is apparently not working because it doesn't seem to reliably return the keys that are pressed (my understanding is the keysDown function was originally designed to get around this whole key detection problem). Does this work for you on Windows (or anyone else for that matter)? Thanks & Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
Win XP Pro SP2 etc All keys detected except those you wouldn't expect to detect: Power, Sleep and WakeUp. Pat - Original Message - From: "Scott Rossi" <[EMAIL PROTECTED]> To: Sent: Tuesday, April 19, 2005 10:06 AM Subject: Re: Keypress Help Recently, J. Landman Gay wrote: How can one reliably tell on Windows when a key is pressed versus when it is released? Are you sure you don't have your operating systems backwards? ;) In my experience, it has always been Mac OS that doesn't generate accurate keyUp messages. Windows has always worked for me. That is an OS limitation, as Macs send keyup immediately after keydown, regardless of the physical state of the key itself. Or at least, that's how it has always been in the past. Thanks for the response Jacque. But I wonder if you might be thinking about OS9. OSX works great for me. When I run the following simple test stack on MacOS, it works as expected: go url "http://www.tactilemedia.com/download/keytracker.rev"; Enable the test button and press one/some keys. The pressed keys are shown and [empty] is displayed when nothing is pressed. When this is run on WindowsXP, I get a mostly empty result, that flickers between the pressed keys and [empty]. The keysDown function is apparently not working because it doesn't seem to reliably return the keys that are pressed (my understanding is the keysDown function was originally designed to get around this whole key detection problem). Does this work for you on Windows (or anyone else for that matter)? Thanks & Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
Recently, Dar Scott wrote: > So maybe you can use a counter that is incremented with down and > incremented with up and call the key down if it is not zero. If > neither up or down has come in in some period of time clear the > counter, making the key up. Thanks for the suggestion Dar. Barring a 'real' detection scheme, I might have to resort to something like this. Thanks & Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
Recently, J. Landman Gay wrote: >> How can one reliably tell on Windows when a key is pressed versus when it is >> released? > > Are you sure you don't have your operating systems backwards? ;) In my > experience, it has always been Mac OS that doesn't generate accurate > keyUp messages. Windows has always worked for me. That is an OS > limitation, as Macs send keyup immediately after keydown, regardless of > the physical state of the key itself. Or at least, that's how it has > always been in the past. Thanks for the response Jacque. But I wonder if you might be thinking about OS9. OSX works great for me. When I run the following simple test stack on MacOS, it works as expected: go url "http://www.tactilemedia.com/download/keytracker.rev"; Enable the test button and press one/some keys. The pressed keys are shown and [empty] is displayed when nothing is pressed. When this is run on WindowsXP, I get a mostly empty result, that flickers between the pressed keys and [empty]. The keysDown function is apparently not working because it doesn't seem to reliably return the keys that are pressed (my understanding is the keysDown function was originally designed to get around this whole key detection problem). Does this work for you on Windows (or anyone else for that matter)? Thanks & Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
On Apr 18, 2005, at 5:44 PM, Ken Ray wrote: Notice the two downs at the start and two ups at the end. A long time ago I spoke with Scott Raney about this, and he said that different OSes may send different sequences of downs and ups (he's just reporting them as they come in from the event manager in the OS)... the only thing he could guarantee was that there was always going to be an equal number of downs to ups (i.e. none would get lost). Well, if all the OSes Scott Rossi needs are like this, he's set. dar ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
On 4/18/05 6:05 PM, "Dar Scott" <[EMAIL PROTECTED]> wrote: > > On Apr 18, 2005, at 2:21 PM, Dar Scott wrote: > >> Here is what I see with rawKeyDown and rawKeyUp: >> >> When the key is pressed, a rawKeyDown is sent. As the key is held >> down then a sequence of rawKeyDown/rawKeyUp pairs are sent. Then a >> rawKeyUp is sent. > > A picture might help: > > D DU DU DU DU DU DU DU U > > Notice the two downs at the start and two ups at the end. A long time ago I spoke with Scott Raney about this, and he said that different OSes may send different sequences of downs and ups (he's just reporting them as they come in from the event manager in the OS)... the only thing he could guarantee was that there was always going to be an equal number of downs to ups (i.e. none would get lost). I know this doesn't help, but it does explain why different OSes behave differently in this case. Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
On Apr 18, 2005, at 2:21 PM, Dar Scott wrote: Here is what I see with rawKeyDown and rawKeyUp: When the key is pressed, a rawKeyDown is sent. As the key is held down then a sequence of rawKeyDown/rawKeyUp pairs are sent. Then a rawKeyUp is sent. A picture might help: D DU DU DU DU DU DU DU U Notice the two downs at the start and two ups at the end. Dar -- ** DSC (Dar Scott Consulting & Dar's Lab) http://www.swcp.com/dsc/ A Sponsor of RevCon West ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
On Apr 18, 2005, at 12:48 PM, Scott Rossi wrote: How can one reliably tell on Windows when a key is pressed versus when it is released? (An external?) Here is an idea that might work. Here is what I see with rawKeyDown and rawKeyUp: When the key is pressed, a rawKeyDown is sent. As the key is held down then a sequence of rawKeyDown/rawKeyUp pairs are sent. Then a rawKeyUp is sent. So maybe you can use a counter that is incremented with down and incremented with up and call the key down if it is not zero. If neither up or down has come in in some period of time clear the counter, making the key up. (There might be some other scheme based on the down/up pairs being close together if that doesn't work.) Dar -- ** DSC (Dar Scott Consulting & Dar's Lab) http://www.swcp.com/dsc/ A Sponsor of RevCon West ** ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Re: Keypress Help
On 4/18/05 1:48 PM, Scott Rossi wrote: Howdy List: Still looking for options to reliably detect keypress events on Windows with Rev. Recap: keyUp messages are immediately sent regardless of whether a pressed key is released. Same happens with keyDown and rawKeyDown. Even the keysDown() function doesn't seem to help here since it apparently alternates between returning the pressed key/s and empty. I now have to go explain to a client why I was unable to get their demo working correctly on a test system. This is majorly irritating since key events work as expected on MacOS. How can one reliably tell on Windows when a key is pressed versus when it is released? Are you sure you don't have your operating systems backwards? ;) In my experience, it has always been Mac OS that doesn't generate accurate keyUp messages. Windows has always worked for me. That is an OS limitation, as Macs send keyup immediately after keydown, regardless of the physical state of the key itself. Or at least, that's how it has always been in the past. At any rate, I wrote a work-around for it, which should work just as well on Windows as it does on Macs. You'll have to alter the script to suit your own needs, but basically I had to implement a checking loop after a key was depressed. I used a rawKeyDown to start the actions I needed to do, and added "checkKey whichKey,theBtn" to the rawKeyDown handler. That started the loop. Then this handler managed the rest of it: on checkKey whichKey,theBtn -- see if "f" or "r" key has been released; Macs don't generate -- accurate keyUp msgs so we need to use a loop check put charToNum(whichKey) into theKey if theKey is not in keysDown() then -- key is released repeat for each line i in the pendingmessages if i contains "checkKey" then cancel (item 1 of i) end repeat send "mouseUp" to btn theBtn else send "checkKey whichKey,theBtn" to me in 200 milliseconds end if end checkKey In my case, I only needed to check for the keys "r" or "f", but you could alter this to check for whatever keys you need, or all of them. I didn't have any trouble with the keysdown() function returning incorrectly. That may be because I allowed some time between checks, but I don't know for sure. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
Keypress Help
Howdy List: Still looking for options to reliably detect keypress events on Windows with Rev. Recap: keyUp messages are immediately sent regardless of whether a pressed key is released. Same happens with keyDown and rawKeyDown. Even the keysDown() function doesn't seem to help here since it apparently alternates between returning the pressed key/s and empty. I now have to go explain to a client why I was unable to get their demo working correctly on a test system. This is majorly irritating since key events work as expected on MacOS. How can one reliably tell on Windows when a key is pressed versus when it is released? Thanks & Regards, Scott Rossi Creative Director Tactile Media, Multimedia & Design - E: [EMAIL PROTECTED] W: http://www.tactilemedia.com ___ use-revolution mailing list use-revolution@lists.runrev.com http://lists.runrev.com/mailman/listinfo/use-revolution
