I am using Macro Scheduler with TextPad on a new routine. I have used both programs for years with no issues until tonight.
Macro Scheduler is being called by another program to start TextPad, open a file, execute a TextPad macro, parse some text, save the results, close TextPad, and continue with its other tasks.. This is a typical usage for me.
BUT.....Trying to open a file in TextPad, I sent the CTL-O combination to open a file and instead of the Open File(s) dialog, I get a small "Quick Open" window, which I have never seen before. After no luck finding the source, I changed the method to send ALT-FO keys, and this is working fine. If I open TextPad manually, and sent CTL-O is works fine, only fails under macro speed. This is being used on XP Pro system. Tried on another XP PRO system with same results. Have no other machines available right now to test on other Operating Systems. Has anyone else seen anything like this? What is triggering the Quick Open window? I don't believe it is from TextPad or Macro Scheduler. I think the OS is the culprit. Could not find anything with Google either.
I can easily change the macro to use ALT-FO, but I am curious about where this comes from and when I can expect to see it.
Thanks for listening.......
Quick Open message
Moderators: JRL, Dorian (MJT support)
- Bob Hansen
- Automation Wizard
- Posts: 2475
- Joined: Tue Sep 24, 2002 3:47 am
- Location: Salem, New Hampshire, US
- Contact:
Quick Open message
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!
Bob
A humble man and PROUD of it!
You are specifying capital O. CTRL-O. This is the same as CTRL-SHIFT-o. In TextPad this opens the dialog you describe, though strangely there doesn't appear to be a menu item for it. It does however let you open a file in textpad, so this is nothing to do with the operating system.
If you change your macro to use lower case O it will work: CTRL-o
Press CTRL
Send>o
Release CTRL
I always use lowercase letters when sending ctrl/alt keystrokes as upper case letters are equivalent to having shift pressed. o is key o, O is shift-o. This may not always be a problem, but will be when there is a
corresponding shift-key shortcut as there appears to be in this case. So just in case I always issue lower case characters.
If you change your macro to use lower case O it will work: CTRL-o
Press CTRL
Send>o
Release CTRL
I always use lowercase letters when sending ctrl/alt keystrokes as upper case letters are equivalent to having shift pressed. o is key o, O is shift-o. This may not always be a problem, but will be when there is a
corresponding shift-key shortcut as there appears to be in this case. So just in case I always issue lower case characters.
MJT Net Support
[email protected]
[email protected]
- Bob Hansen
- Automation Wizard
- Posts: 2475
- Joined: Tue Sep 24, 2002 3:47 am
- Location: Salem, New Hampshire, US
- Contact:
Thanks for the reply. I just left the TextPad forum where I left the same message. CTL-SH-O opens up a TextPad QuickOpen dialog window, so that is the source, not XP.
I usually make it a point to closely look at the case size on the menus because I have run into problems in the past. In TextPad, the option is clearly an uppercase O, vs. a lowercase o.
Manually, pressing CTL-O gets normal Open File dialog if Caps Lock is on/off, makes no difference. The QuickOpen only comes up when I physically hold down the SH key when doing CTL-O.
I will be changing to lowercase o later tonight Will also have to look closely at my macro script and check for an earlier PRESS SHIFT that I did not RELEASE.
Thanks for the feedback.......
I usually make it a point to closely look at the case size on the menus because I have run into problems in the past. In TextPad, the option is clearly an uppercase O, vs. a lowercase o.
Manually, pressing CTL-O gets normal Open File dialog if Caps Lock is on/off, makes no difference. The QuickOpen only comes up when I physically hold down the SH key when doing CTL-O.
I will be changing to lowercase o later tonight Will also have to look closely at my macro script and check for an earlier PRESS SHIFT that I did not RELEASE.
Thanks for the feedback.......
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!
Bob
A humble man and PROUD of it!
- Bob Hansen
- Automation Wizard
- Posts: 2475
- Joined: Tue Sep 24, 2002 3:47 am
- Location: Salem, New Hampshire, US
- Contact:
I did change to lower case "o". Problem fixed.
Note here for TextPad users:
I have left a request with TextPad to correct the Keyboard designations. All settings are shown as UpperCase, and although hot keys can be defined, the lowercase selections still show up in Uppercase. But that is a TextPad issue now, not Macro Scheduler. Bottom line is that they are both working together for me again.
Note here for TextPad users:
I have left a request with TextPad to correct the Keyboard designations. All settings are shown as UpperCase, and although hot keys can be defined, the lowercase selections still show up in Uppercase. But that is a TextPad issue now, not Macro Scheduler. Bottom line is that they are both working together for me again.
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!
Bob
A humble man and PROUD of it!