Hello Muhammad,
Yes, the Synopsis field is for a quick, short description of what the script
does, such as "Copys screen material to clipboard."
The Description field is for a more detailed description, as well as any
info specific to this script/function, such as if the function was
version-specific, etc. An example might be, "Grabs specific amount of
screen data and writes it to the clipboard for pasting into an editor.
Tested in 3.3x and higher."
The Category field just gives it a classification of what purpose the
function performs; does it say text, does it effect the cursor, does it
change options, etc. At present, this field isn't used for anything, but in
later releases, may be used in cataloging scripts and functions.
The Assign to Hotkey field is where you do just that--assign it to a
keystroke.
The only critical fields here is the Script name, Can be assigned to
keystroke, and Assign to Hotkey. If you hit Control+s to compile the script
prior to hitting the Control+D to edit it's properties, then the Script name
and the Can be assigned to keystroke fields are already taken care of--all
you need to do is give it a keystroke. Since you are the only one going to
use your script files, you can leave the Synopsis and Description fields
blank, and don't worry about the Category field.
----- Original Message -----
From: Muhammad Fazil <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 08, 1999 7:50 PM
Subject: Re: script tip # 110, step 4
> Hi Dennis,
> I also tried to use this script and went as far as where I was supposed to
> fill in some edit fields, check an uncheck box and so forth. I'm not sure
> what I should write in the first edit field and what choice to pick up
from
> the list box. In the synopsis and description fields, I'm suppose to
write
> the detail of the script-functionality, isn't it?
> ----- Original Message -----
> From: Dennis Brown <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, September 08, 1999 7:54 PM
> Subject: Re: script tip # 110, step 4
>
>
> > Hello Stan,
> >
> > Can you attach your c:\jfw33\settings\enu\default.jss file to a private
> > message to [EMAIL PROTECTED]? We'll see if we can track that puppy
> > down!
> > The script works like a dream! I'm doing contract work on a set of
> scripts
> > for a network, and even though the login screen speaks poorly at
present,
> > using that script to capture that window's contents has been fantastic
at
> > giving me the ability to see that screen's contents to determine how to
> > approach writing a script for that login screen! It doesn't preserve
> > carriage returns, but it has shown me text that JFW didn't pick up the
> first
> > couple of times through!
> >
> >
> > Thanks,
> > Dennis Brown, [EMAIL PROTECTED]
> > Visit the Blind Programming site at http://brown99.home.mindspring.com/
> >
> > ----- Original Message -----
> > From: Stan Holdeman <[EMAIL PROTECTED]>
> > To: JAWS List <[EMAIL PROTECTED]>
> > Sent: Wednesday, September 08, 1999 12:19 PM
> > Subject: Re: script tip # 110, step 4
> >
> >
> > > Friends: Yes, Daine, when I made sure the cursor was on text the
> > > documentation feature was available. Then I ran into a compile error.
> The
> > > message said: "Expected window to be a variable of type int not
string."
> > > Does this have something to do with category in the documentation
> window?
> > At
> > > first I left that blank. Then I tried it with application. Got the
same
> > > error message either way.
> > > I have now recycled JAWS from memory and find that my assigned hotkey
> > > responds saying, "unknown script called to copy text from screen." It
> > > appears that I have succeeded in saving a half-a---- script into the
> > default
> > > script. Can anyone help me out here?
> > >
> > > Stan
> > >
> > > -----Original Message-----
> > > From: Daine Pearson <[EMAIL PROTECTED]>
> > > To: Jaws Mail List <[EMAIL PROTECTED]>
> > > Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> > > Date: Wednesday, September 08, 1999 3:50 AM
> > > Subject: script tip # 110, step 4
> > >
> > >
> > > >
> > > >Stan,
> > > >
> > > >I suspect the only thing that went wrong is that the cursor needs to
> > > >actually be in the body of a script or function for the documentation
> > > >feature to be available.
> > > >In this case, you need to be below the line :Script
CopyTextFromScreen
> > ()
> > > >
> > > >Daine
> > > >
> > > >
> > > >> -----Original Message-----
> > > >> From: "Stan Holdeman" <[EMAIL PROTECTED]>
> > > >> Date: Tue, 7 Sep 1999 14:12:32 -0500
> > > >> Subject: script tip # 110, step 4
> > > >>
> > > >> I am running JFW 3.2031 in Windows 95.
> > > >>
> > > >> I recently unsuccessfully attempted to load up Dennis Browns script
> tip
> > > >> #110. I bogged down at step 4. Here is what I did:
> > > >> I did steps 1 thru 3. For step 3, I copied all the script material
> > > between
> > > >> steps 3 & 4 into clip board and pasted that into the script
manager.
> > Then
> > > >> when I attempted step 4, edit the properties, I hit control + D
> > > >> and nothing
> > > >> happened. The view documentation line in the View pull-down menu
> > > >> was grayed.
> > > >> What did I do wrong.
> > > >>
> > > >> I am obviously a novice at this script business.
> > > >>
> > > >> Stan
> > > >
> > > >-
> > > >Visit the jfw ml web page: http://jfw.cjb.net
> > >
> > >
> > >
> > >
> > >
> > > -
> > > Visit the jfw ml web page: http://jfw.cjb.net
> >
> > -
> > Visit the jfw ml web page: http://jfw.cjb.net
> >
>
> -
> Visit the jfw ml web page: http://jfw.cjb.net
-
Visit the jfw ml web page: http://jfw.cjb.net
