Caps Lock affects Send>

Technical support and scripting issues

Moderators: JRL, Dorian (MJT support)

Post Reply
Me_again
Automation Wizard
Posts: 1101
Joined: Fri Jan 07, 2005 5:55 pm
Location: Somewhere else on the planet

Caps Lock affects Send>

Post by Me_again » Wed Apr 26, 2006 5:20 pm

Strange but true :( I wrote a macro for my own use to login to a VPN server. I RunProgram> the Cisco client, it defaults in the username, I Send> the password. If Caps Lock is set on the keyboard the password is rejected.

Not a big deal, and I could workaround it if I had to, just thought it worth to mention in case anyone else runs into a similar inexplicably failing macro situation.

User avatar
JRL
Automation Wizard
Posts: 3529
Joined: Mon Jan 10, 2005 6:22 pm
Location: Iowa

Post by JRL » Wed Apr 26, 2006 6:39 pm

This has been the case for as long as I've been using Macro Scheduler. (Version 6) The capslock key reverses the case of any text applied using the Send> function. If Capslock is on, sending a lower case alpha character will apply an upper case alpha character. Sending an upper case alpha character will apply a lower case alpha character.

You obviously don't work with people whose capslock is continuously on or you'd have run into this long ago. :)

Later,
Dick

Me_again
Automation Wizard
Posts: 1101
Joined: Fri Jan 07, 2005 5:55 pm
Location: Somewhere else on the planet

Post by Me_again » Wed Apr 26, 2006 6:49 pm

"hELLO wORLD" :lol:

Gosh darn you're right. I thought it was a Cisco thing. I very rarely have a need to use Send> and I would never have imagined it worked like that :? Does it affect key combinations too? Maybe this feature could be added to the Help text?

User avatar
jpuziano
Automation Wizard
Posts: 1085
Joined: Sat Oct 30, 2004 12:00 am

Post by jpuziano » Thu Apr 27, 2006 2:48 am

Hi Me_again,

The post Detecting CapsLock State has some background on this issue and shows how one can deal with it...

...but I agree with you that a note or warning should be added to the Help file for Send> to say that the Caps Lock key will affect the output. I also think the few lines of code it takes to detect CapsLock/Numlock/ScrollLock etc. should be there in the help file too.

Before using a command for the first time, I think many of us read about it in the help file. If details like this aren't in there, often we'll learn about it the hard way. Hitting snags is no fun and takes time... however, if its there, no problem and no time wasted.

The vetern macro coders pick up these things through experience (making mistakes) but for new users... how much easier and faster it would be if all things like this were in the help files... just my two cents.

Also... hats off to the folks working on translating the help file. Not only will this bring the documentation to another language, but a lot of corrections and improvements are being applied to the English version as a result, good job all!
jpuziano

Note: If anyone else on the planet would find the following useful...
[Open] PlayWav command that plays from embedded script data
...then please add your thoughts/support at the above post - :-)

Me_again
Automation Wizard
Posts: 1101
Joined: Fri Jan 07, 2005 5:55 pm
Location: Somewhere else on the planet

Post by Me_again » Thu Apr 27, 2006 3:02 am

Thanks, that's an interesting thread.

I guess the follow on question is why is it designed to function this way?

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts