Re: Hiding OE's window
Re: Hiding OE's window
- Subject: Re: Hiding OE's window
- From: Andy Wylie <email@hidden>
- Date: Sun, 03 Mar 2002 22:44:03 +1300
the mailman seemed to mislay your post for awhile Paul
iWrote:
>
> with due respect your wheel is an outdated , as account info can be
>
> configured in schedules there seems little point in replicating this in a
>
> script and contrary to your belief keystrokes can be sent from a compiled
>
> script running in OE (5.0.3 at least) either attached to a schedule or from
>
> the script menu.
to which Paul replied:
>
>
I'm not sure what you mean by "account info". I don't see where account info
>
comes into this at all.
>
I mean the way your script loops through accounts.
>
>
It may be that improvements to the OS (not OE, which has not changed in the
>
several years since 5.02 came out; 5.03 just added the Hotmail fix) have
>
improved responsiveness with respect to to key and menu emulation. It's not
>
that they don't work at all, but rather that they are, or were, very
>
unreliable. 'puppet menu' cannot be used more than once, or occasionally
>
twice, in quick succession. 'type text' and 'typetext" (Sigma's and Sandi's)
>
don't (or didn't ) work if you happened to be typing at the time or if
>
anything much was going on at all: they might work when OE was totally idle.
>
I don't think I ever tried 'input state': I certainly tried everything else.
>
'input state' fares no better but if all that's required is showing the
window then a one liner using any of the aforementioned OSAX in a compiled
script run in OE seems to work fine as you've alluded to, it's only when
trying to do more in a script problems arise in my experience. You did say
earlier it didn't work as you said of setting visibility of special windows
to true which isn't entirely true either as they toggle fine if they're open
or hidden.
>
In fact it was Eric Grant, creator of Sigma's Additions, who helped me at
>
the time and explained what was going on. The chief developers of OE, Jud
>
Spencer and Dan Crevier, have confirmed that it is designed not to allow
>
input from menu selection or keyboard equivalents while scripts are running.
hence the beachball
>
That is because the interaction between them could interfere with each
>
other. But often you can get in a "quick one".
100% of the time here under 8.6 with the one line script as the first
action.
>
perhaps with recent improvements to the OS and far greater allocations of RAM
>
than a few years ago, this now works most of the time. But you'll still find
>
that you can't do much with the keyboard or menu clicking while a long script
>
is running.
>
You can sometimes select an item in a list, but not much more. It's the same
>
with keyboard emulation: as the last, or next to last command in a script,
>
it works, but not if you have to follow it with lots of other script
>
commands: they seem to override it (puppet menu too). I tried all this
>
stuff, many times over, in many different contexts.
I'm glad you clarified that
>
>
If you find it works reliably, 100% of the time, that's certainly an
>
improvement form 2 years ago. neither Akua, Sigma's, Sandi's or OE has
>
changed, so it must be the OS. If it's reliable, then it's better, since it's
>
simpler. Why "far better" I wouldn't know.
1 not 2 OSAX, no applet and no loops is far better to my mind.
>
Have you really not had any complaints of unreliability from users on other
>
machines wit your method?
yes :) but results might differ if (users on other machines) > 0 = true
>
That's good. My "outdated' scripts have been downloaded by about 4000 users
>
(OE and Entourage versions). So far, I haven't received any complaint except
>
yours.
>
wow! no wait I've not run it once, I hope at least one said thanks :) It's
finally dawned on me your script is all about *closing* the "Progress"
window, a more descriptive name would be 'close progress window disconnect'.
Anyway I'm not complaining, I just found the subject interesting and my
findings didn't concur with some of the things you'd said earlier and even
if I did want the window to close I'd run an applet something like ...
tell application "Outlook Express"
puppet menu {"Window", "Progress"} --or whatever
repeat until connection in progress = false
delay 1
end repeat
close window "Progress"
end tell
and leave the rest to the user and schedules.
_____________________________ Andy
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.