Hi Yuma,
Thanks much for your post, but please forgive a few follow up questions.
I understand that I need to locate errors by searching for color changes
(vo-command-k), but have not yet determined how to configure colors such that
errors will be unique.. The closest applicable VO configuration appears to be
under verbosity -> text. I also noticed where fonts can be customized in the
Script Editor prefferences , but none of the items under the formatting tab
list errors.
Under prefferences -> edit the "use script assistant" item is checked, which I
thought would suggest line completions, but perhaps this is more of a clutter
for voiceOver users since I've seen no sign of this occurring? Perhaps xCode
is the better solution.
I understood your example, to copy a parm from a list of possible values,
however was not clear about your suggestion of how to construct a text file?
How would the header strings be helpful? Wouldn't they serve to make me count
more text items to refference them properly <smile>?
Until I construct my text file, I'll need to cut and paste from the applicable
application dictionary. Which one (if any) should be used for scripting that
is not necessarily application specific? To clarify, yesterday I wanted to
display my hello world message, and thought the command was "display prompt",
rather than "display dialog". I opened the script editor dictionary, but could
not locate the proper command, so eventially located it in the script reference
manual. If I'm understanding you correctly, you're saying that until I have
the syntax memorized, I'll need to either consult the manual, or construct the
text file you spoke of?
Thanks again for taking the time to respond, and best regards.
Geoff
On Jan 8, 2011, at 3:17 AM, Yuma Decaux wrote:
> Hi Jeff,
>
> First off, you have no choice but to keep the library open and switch from
> editor to dictionary and refer yourself or copy paste with selections.
>
> As for debugging purposes, sighted people can see that a syntax error
> generates a color change where the error is. In the case of us blind users,
> one solution is to use the next changed attribute vo shortcut to find where
> the bug is. Before this actually becomes relevant, you have to go into the vo
> preferences and turn all texts except for error text to one color and error
> to any other color, so that you don't have to shuffle through all different
> attributes like verb, argument, etc before you get to the error color text.
>
> One more solution is to use xcode instead of the applescript editor and use
> xcode's own debugger.
>
> I will track back to the problem of copy pasting.
>
> Here is a snippet from the top of my head to perhaps alleviate the problem:
>
> set list_command to {arg1,arg2,arg3,etc}
> display list_command as list with default arg1
>
> On press button
> Copy selection
>
>
> You would compile the script and append it to a shortcut for quick reference.
>
> To make the thing more flexible, you can copy paste all the commands into a
> tex file with headers, distinguish the headers with long strings and commands
> as singular words.
>
> As you get more versed with commands, you just add them to the text file, and
> make an applescript which lists all the commands from the text file by using
> the item reference within the document class.
>
> Good luck.
>
>
> Best
>
> Yuma DX®
>
> --
> You received this message because you are subscribed to the Google Groups
> "MacVisionaries" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/macvisionaries?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"MacVisionaries" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/macvisionaries?hl=en.
