Re: Hiding OE's window
Re: Hiding OE's window
- Subject: Re: Hiding OE's window
- From: Paul Berkowitz <email@hidden>
- Date: Sat, 02 Mar 2002 21:23:52 -0800
On 3/2/02 8:33 PM, "Andy Wylie" <email@hidden> wrote:
>
>
> it won't work for the Progress Window.
>
>
no kidding ;)
>
>
> You can save yourself several weeks' reinventing the wheel if you get
>
> Progress
>
> Window Connect script from
>
>
>
> AppleScript Central
>
> <http://www.applescriptcentral.com/>
>
>
>
> It requires very elaborate setup along the lines of what i discussed
>
> earlier in this thread.
>
>
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.
I'm not sure what you mean by "account info". I don't see where account info
comes into this at all.
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.
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
. That is because the interaction between them could interfere with each
other. But often you can get in a "quick one". 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.
>
>
A script using any of the keystroke OSAX you've mentioned or Akua's 'puppet
>
menu {"Window", "Progress"}' or 'input state {keys down:"3", modifier
>
keys:"C"}' will open the window and/or set it to the front. A far better
>
wheel when attached to a schedule IMO.
>
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. Have you really not had any
complaints of unreliability from users on other machines wit your method?
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.
--
Paul Berkowitz
_______________________________________________
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.