General Macro Scheduler discussion
Moderators: JRL, Dorian (MJT support)
-
Spidersnet
Post
by Spidersnet » Fri Oct 15, 2004 6:08 am
I have been using MS for lots of applications The set Focus to Filenote works fine but no matter how much wait time or Sk_delay I create the key sends to this Filenote do not generate action.
let>SK_DELAY=10
Set>FileNote*
Wait>1
Press CTRL
sen>s
Wait>1
waitwindowopen>Claim Search*
set>Claim Search*
sen>%EnterNumber.msEdit1%
press enter
-
Lumumba
Post
by Lumumba » Fri Oct 15, 2004 6:26 am
Might sound like a stupid question. Anyway ...
Have you declared the variable EnterNumber.msEdit1 somewhere above in your code ?
Let>EnterNumber.msEdit1=MyVarContentIsThisLousyStringWhichHasNoMeaningAtAll
Or do you want your string be seen as a cumulation of literals ?
-
spidersnet
- Newbie
- Posts: 4
- Joined: Fri Oct 15, 2004 6:34 am
Post
by spidersnet » Fri Oct 15, 2004 6:40 am
yes The above code is a snippet from 1600 line script. My main concern is that after the Set Focus shows the Filenote application as Active my Sen> Ctrl s does not activate the secondary child window - but normal keyboard action at this stage does
-
Bob Hansen
- Automation Wizard
- Posts: 2475
- Joined: Tue Sep 24, 2002 3:47 am
- Location: Salem, New Hampshire, US
-
Contact:
Post
by Bob Hansen » Fri Oct 15, 2004 7:00 am
Are you missing Release>CTRL?
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!
-
spidersnet
- Newbie
- Posts: 4
- Joined: Fri Oct 15, 2004 6:34 am
Post
by spidersnet » Fri Oct 15, 2004 7:20 am
still no action, have updated, have been using MVR and Lclick as current get around while trying for a more reliable fix, the code did include Release CTRL originally
I tried using the Macro recorder as well and on running it's code same errors occuring where no action to key send.........
WaitWindowOpen>FileNote Organiser - \\Remote
MoveWindow>FileNote Organiser - \\Remote,0,-6
ResizeWindow>FileNote Organiser - \\Remote,683,609
Wait>0.01
MouseMove>386,267
Wait>1.13
Press CTRL
Wait>0.38
Send>s
WaitWindowOpen>Claim Search - \\Remote
MoveWindow>Claim Search - \\Remote,218,142
ResizeWindow>Claim Search - \\Remote,363,145
Wait>0.13
Release CTRL
Wait>1.2
Even tried moving release CTRL to above WaitWindowOpen
Still no change.....
-
support
- Automation Wizard
- Posts: 1450
- Joined: Sat Oct 19, 2002 4:38 pm
- Location: London
-
Contact:
Post
by support » Fri Mar 04, 2005 5:14 am
Hi,
We have found a solution for handling ctrl/shift/alt under Citrix.
It appears that a change we made some time back to fix an issue sending these keystrokes in Windows 2000 stopped them working under Citrix. Typical! Therefore, rather than unfix it again, we have added a variable called SK_LEGACY which can be set to 1 to force MSched to use the old method for sending these keys.
Jon has tested this successfully and the solution will be available in the next update.