shortcut will not work

[Aaron]

Im having trouble with getting the shortcut on firefox to go to the address bar
shortcut is ctrl + L

Code: Select all

wait>1
SetFocus>Mozilla Firefox
Press>Ctrl
Send>L
Release>Ctrl

any thoughts would be helpful

thanks

[Bob Hansen]

Try lowercase

Send>l

[jpuziano]

Hi Aaron,

Bob's probably right about that Capital L... you want to use a lowercase l.

Also... "Press>Ctrl" and "Release>Ctrl" is not proper syntax, you want just "Press CTRL" and "Release CTRL", try the code below:

Code: Select all

Wait>1
SetFocus>Mozilla Firefox
Press CTRL
Send>l
Release CTRL

This should work fine... as long as no one presses your "Caps Lock" key. As soon as that happens, the script will likely fail as the Send> command is now going to be sending a Capital L... and we're back to the same old problem.

Thankfully, we now have a slick solution to this problem that was implimented in Version 9.0 11/10/2006 - see this post for the background. Here it is, copied straight from the Help file on the Send> command:

• Note that this command sends keystrokes and therefore any keys sent will be subject to the current state of modifier keys and the caps lock key. To ignore the caps lock state and send the text as entered set SK_IGNORECAPS to 1. (Let>SK_IGNORECAPS=1).

So... here's your code again, only this version will keep working no matter what state your Caps Lock key is in:

Code: Select all

Let>SK_IGNORECAPS=1
Wait>1
SetFocus>Mozilla Firefox
Press CTRL
Send>l
Release CTRL

Hope this was helpful. Let us know if this works for you... and take care.

[Aaron]

Let>SK_IGNORECAPS=1 Dose not work but the lower case will.

Not sure if its a version problem or something else.

Thanks

[Bob Hansen]

For the record, I have used both of these formats for years with success:

Press CTRL
Press>CTRL

I think I started by using the ">" and had no issues. Then some years later I discovered that I had been doing it "wrong" and started to leave out the ">", but old habits are hard to break, and I still find myself using "Press>"

[jpuziano]

For the record, I have used both of these formats for years with success:

Press CTRL
Press>CTRL

I think I started by using the ">" and had no issues. Then some years later I discovered that I had been doing it "wrong" and started to leave out the ">", but old habits are hard to break, and I still find myself using "Press>"

Thanks for bringing that to light Bob. If you enter the following two lines into the Advanced Editor...

• Press CTRL
  Press>CTRL

...you'll see that the first line gets colored blue (a recognized command) while the second line stays black (unrecognized... which I took to mean... not a valid command).

Also, in the "Press" topic in the Help file, there is not a > character anywhere so... I assumed including the > was not proper syntax.

Since Press commands of the form: Press>SOME_KEY currently work, I know they'll have to keep working. We're not going to get around that one... to change that would break old scripts and that would be very bad.

As it stands though, this functionality is undocumented and the way the syntax highlighting works for this is actually misleading. To maintain the highest standards of documentation and consistency we've come to expect from Macro Scheduler, I'd recommend the following two fixes:

1. The Advanced Editor color syntax highlighting should recognize both forms of the Press commands; both with and without the > should show up in bright blue because... they are both valid.
2. A note should be added to the "Press" topic in the Help file (and the on-line help) that the "Press>SOME_KEY" form of the command is also valid (though perhaps not preferred).

Do you agree Marcus?

Thanks again Bob for clarifying that...

[jpuziano]

Let>SK_IGNORECAPS=1 Dose not work but the lower case will.

Not sure if its a version problem or something else.

Thanks

What version are you using?

[Aaron]

Version 9.054 pro

[Me_again]

Yes, thanks Bob. I always found that very confusing.