{lshift up} not working for anyone else?

[IKilledBambi]

Send("{lshift down}")
Sleep(500)
Send("{lshift up}")

Doesn't send shiftup for me, is this a bug for everyone else?

Edit* woot noticed post count

Edit 2* Just noticing that rshift does it to.

Edited January 17, 2009 by IKilledBambi

[FireFox]

up mean that its not pressed so you cant send it as a key ...

Cheers, FireFox.

Edited January 17, 2009 by FireFox

[IKilledBambi]

its pressed

Send("{lshift down}")

[FireFox]

yep but Send("{lshift up}") not possible as i said if you want to press its just for release the press down

Cheers, FireFox.

[Yorn]

LSHIFT UP does not work for me either. Exactly as you describe, once you use LSHIFT DOWN, the key stays down until you manually hit the left shift key.

Edited July 28, 2009 by Yorn

[Yorn]

Is there any way to force all keys up? Preferably through some sort of hardware hack so we don't have to wait for this to get patched? Again, if {LSHIFT DOWN} is used for 15 seconds then {LSHIFT UP} will ***NEVER UNDER ANY CIRCUMSTANCES*** undo it.

Simple script to test:

Send("{LSHIFT DOWN}")

Sleep(500)

Send("{LSHIFT UP}")

Run that, then watch as your computer continually runs with Left Shift Down. Just try clicking on anything, it won't work or will highlight text or do whatever would normally happen with shift down.

Edited July 28, 2009 by Yorn

[LarryDalooza]

I had a similar problem and had to use {SHIFTUP} ... I try to avoid the generic UP and DOWN operators on "modifier keys" like SHIFT and ALT.

Lar.

[motionman95]

What! This is unacceptable. The same thing is happening to me, and it is really messing up my script. My code:

Send("{LSHIFT down}") ;Left Shift down
Sleep(1000)
MouseClick("right") ;Right Mouse press
Sleep(1000)
Send("{LSHIFT up}") ;Left Shift up

Edited July 30, 2009 by motionman95

[motionman95]

There's no fix for this, is there?

[Jos]

What! This is unacceptable.

What is unacceptable?

There's no fix for this, is there?

http://www.autoitscript.com/trac/autoit/ticket/1094 ?

[motionman95]

It seems like this bug is only fixed in the BETA...am I right?

[GEOSoft]

It seems like this bug is only fixed in the BETA...am I right?

According to the ticket it is fixed for the next Beta release. If all goes well then the fix will remain in the Beta releases until the next Full release, and somehow I seem to recall that being the primary reason for Beta releases, to test new and changed code before it is finalized. Don't bother asking for release dates. They are released when they are released.

[motionman95]

Hmm...If I were to get the BETA release, would I be risking anything?

[CodyBarrett]

i'm using it.... nothing bad has happened XD

[Jos]

Hmm...If I were to get the BETA release, would I be risking anything?

Beta runs next to the production release so you easily test it, but you haven't answered my first question and I am really curious which part you consider unacceptable? Edited August 1, 2009 by Jos

[motionman95]

I was frustrated...and I think that what I posted earlier was a poor choice of words. I had been trying to troubleshoot my application for an hour and a half when I gave up and checked the forums. And discovered that it wasn't working just because I was horrible at coding, but because it was a bug. And to me it seemed like the guy got very little help.

Edited August 1, 2009 by motionman95

[Jos]

I was frustrated...and I think that what I posted earlier was a poor choice of words. I had been trying to troubleshoot my application for an hour and a half when I gave up and checked the forums. And discovered that it wasn't working just because I was horrible at coding, but because it was a bug. And to me it seemed like the guy got very little help.

Yea, well that can happen that people don't read threads. To be honest: I only pick the posts that appear well formulated and will avoid most of the bot stuff as I am not interested in that. Picking a good Topic title and subtitle is very important as that is the first selection most people do.

Its understandable that it can be frustrating when you hit a bug but that doesn't mean you should post like you did because that will only have an adverse effect as many will just "walk away" from your posted question.

Edited August 1, 2009 by Jos

[motionman95]

Really? Great advise...I'll keep it in mind for the next time I post! >_

[Yorn]

FOR FUTURE REFERENCE AND ANYONE SEARCHING FOR A FIX FOR THIS PROBLEM CODE:

Send("{LSHIFT DOWN}")
Sleep(500)
Send("{LSHIFT UP}")

THE FIX:

Send("{LSHIFT DOWN}")
Sleep(500)
Send("{SHIFTDOWN}")
Send("{SHIFTUP}")

Something about {SHIFTDOWN} "resets" the {LSHIFT DOWN}. Please use this workaround till the official patch comes out. Thanks to everyone who contributed.

Edited August 3, 2009 by Yorn

[motionman95]

FOR FUTURE REFERENCE AND ANYONE SEARCHING FOR A FIX FOR THIS PROBLEM CODE:

Send("{LSHIFT DOWN}")
Sleep(500)
Send("{LSHIFT UP}")

THE FIX:

Send("{LSHIFT DOWN}")
Sleep(500)
Send("{SHIFTDOWN}")
Send("{SHIFTUP}")

Something about {SHIFTDOWN} "resets" the {LSHIFT DOWN}. Please use this workaround till the official patch comes out. Thanks to everyone who contributed.

Your solution makes sense. Thanks for the awesome fix! Hopefully this will help everyone experiencing problems with this.

Edited August 4, 2009 by motionman95