• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Scripting screendumps ...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Scripting screendumps ...


  • Subject: Re: Scripting screendumps ...
  • From: Paul Berkowitz <email@hidden>
  • Date: Tue, 21 Nov 2000 22:56:15 -0800

On 11/21/00 1:39 PM, I wrote:

> TypeText "4" with Capslock, Command and Shift
>
> compiles, but it doesn't operate the caps lock.
>
> Sigma's Additions' equivalent
>
> type text "4" holding down {caps lock, command, shift}
>
> compiles, but its execution errors, which is more honest ("Can't make some
> data into the expected type").

Correction:

That error appears only when running the script from within Smile. (Smile
has its own routines when the command button is held down, so that may be
interfering, I'd guess.) Running from within Script Editor, no error, but it
still doesn't "prepare" a screen shot to produce that bull's-eye thingy you
get if you depress caps lock and hold down 4-shift-command manually. You get
the "crosshairs" cursor, the same as if you hold down 4-shift-command
_without_ caps lock. (as with Sandi's Additions)

Eric Grant has written me to explain that "the screen capture routines read
the keyboard directly to test for the existence of some keys, rather than
looking in the event record that is created by tools like Sigma's
Additions".


--
Paul Berkowitz


References: 
 >Scripting screendumps ... (From: Jacco Rens <email@hidden>)

  • Prev by Date: Re: Scripting screendumps ...
  • Next by Date: script to convert this digest to FMP 5 database
  • Previous by thread: Re: Scripting screendumps ...
  • Next by thread: Re: Scripting screendumps ...
  • Index(es):
    • Date
    • Thread