Control-O and Alt-FO key stroke problems

[Randall]

I have been burning up some hours trying to get MJT macros to work with Internet Explorer.

If I bring up IE manually, I can hit CTRL-O keys and it will automatically bring up the open box.

However if I bring up IE and then run MJT to send the following

>Press CTRL
>SendText>O
>Release

IE acts like it never saw the sequence.

However if I send ALT - FO, to open up the menu, under the File selection then send O to open up the Open selection, sometimes that fails too, unless I put at least a 0.3 second delay between the F and the O characters. IE acts as if it is not ready for two characters right next to each other, but must prepare itself for the "O" character.

I really want to be able to select the Open box using CTRL-O, but I have been unable so far to accomplish this simple task.

Thanks if you have insight to this or can point out something which I have missed

[olllllliii]

Paste This..
i think it will work

Code: Select all

Press LCTRL
Send>o
Release LCTRL

or ALT-FO

Code: Select all

Let>delay=0.25

Press ALT
Send>f
Wait>delay
Send>o
Release ALT
Wait>delay
Press>Enter

Kind Regard O.Hilger

[CyberCitizen]

Also Try A Set Focus.

You Need To Send A Small o (LowerCase) Not A O (Uppercase).

This Worked For Me.

Code: Select all

SetFocus>Internet Explorer*
Press LCTRL
Send>o
WaitWindowOpen>Open
Release LCTRL

If Your Wanting To Open A URL, You Could Try The Below.
iexplore http://www.google.com.au

If Ever In Doubt, Try Recording The Actions Using The Macro Recorder, Then Analyze The Script.

[armsys]

Hi olllllliii,
You may abbreviate your script:

Paste This..

Code: Select all

Let>SK_Delay=2
Press ALT
Send>f
Release ALT
Send>o
Press>Enter

[armsys]

Hi CyberCitizen,
I prefer:

Code: Select all

Let>WW_TIMEOUT=10
SetFocus>Internet Explorer*
Press CTRL
Send>o
Release CTRL
WaitWindowOpen>Open
If>WW_Result=FALSE
  MDL>IE FAILURE-Report to CyberCitizen
Endif

[CyberCitizen]

LOL Very Funny Armstrong,

Yes I Maybe Should Have Included A Timeout On The Wait Window.

The Main Point Was To Ensure That The Character Being Send Was A Lowercase o.

[Randall]

[quote="armsys"]Hi olllllliii,
You may abbreviate your script:
[quote="olllllliii"]Paste This..
[code]
Let>SK_Delay=2
Press ALT
Send>f
Release ALT
Send>o
Press>Enter[/code][/quote][/quote]

okay, the script with LCTRL and small letter "o" works. I found previously that I need SK_DELAY = 30 for the IE to have enough time to set up from the file menu box.

Also RCTRL works as I expected to find, once I knew that LCTRL works. It is still odd that CTRL does NOT work, and that a capital letter O does not work, although that's what IExplorer wants to see from the keyboard.

I like the control-o approach better than the alt-f-o approach since I am assured that I will get the correct open window if IE recognized the key sequence.

Thanks for the assist, this is appreciated

[armsys]

Hi Randall,

It is still odd that CTRL does NOT work, and that a capital letter O does not work, although that's what IExplorer wants to see from the keyboard.

Thanks for informing us your script works.
Press CTRL should work as expected.
Give it one more shot:

Code: Select all

CapsOff
Let>WW_TIMEOUT=10
Let>WF_TYPE=2
Let>SK_Delay=5
SetFocus>Internet Explorer*
WaitReady>1
Press CTRL
// Remember: CyberCitizen reminds us a small "o" here 
Send>o
Release CTRL
WaitWindowOpen>Internet Explorer*
If>WW_Result=FALSE
  MDL>IE FAILURE-Report to Randall immediately!
Endif

[CyberCitizen]

@armsys: Wait Ready>1 Didn't Work For Me, I Had To Use 0 Or Comment It Out.

[armsys]

Hi Cy,

@armsys: Wait Ready>1 Didn't Work For Me, I Had To Use 0 Or Comment It Out.

What do you mean by "Didn't Work For Me"?
Please narrate the symptom.
For graphics intensive webpages, I always use WaitReady>1 to ensure the webpage is ready receive keyboard/mouse actions.
BTW, why is there a space in your weird command "Wait Ready>"

[CyberCitizen]

The space was only cause I was typing it. Not linking code.

It didn't display the open dialog as it got stuck waiting for a paint event.

[armsys]

It didn't display the open dialog as it got stuck waiting for a paint event.

Thanks for your reply.
Yes, your test webpage likely contains mainly plain text, isn't it?
Yes, in this case, it takes excruciatingly long time.
Yes, in this case, you're better off using WaitReady>0.
Thanks pointing out a potential issue.

[CyberCitizen]

Correct it was a blank IE window, we had already set focus, we then needed to open the open address dialog (Ctrl+o). This is where the paint event was failing. All good, looks like Randall is all sorted now anyway.

[Marcus Tettmar]

Capital O = Shift o.

So CTRL-O may be seen as CTRL-SHIFT-o which is not what you want.

Therefore always use lower case for shortcut key sends.

This is explained here:
http://www.mjtnet.com/blog/2006/01/17/h ... on-script/

[armsys]

Correct it was a blank IE window, we had already set focus, we then needed to open the open address dialog (Ctrl+o). This is where the paint event was failing. All good, looks like Randall is all sorted now anyway.

Hi CyberCitizen,
Thanks for your testing result.
Why does WaitReady>1 take excruciatingly long time for a text-only screen? Why couldn't MS automatically detect the existence of graphics? I hope Marcus will help us resolve the puzzling myth.