Goodness...delete the entire script file for what is probably just a typo in
one of the scripts! Throw out the baby with the bathwater! <grin>
Where did you get those scripts--I'll take a look at them, if you like.
Or if you'd like to tackle it own your own machine, try this:
1) Hit Insert+Q to get the script file name.
2) Hit Insert+8 to bring up the Keyboard Manager.
3) You're probably on the correct script file name by default, but if not,
hit the beginning letter, (probably "N") and keep hitting it until the
correct filename appears.
4) Hit Tab to get into the list of key assignments in the Notepad script.
Find out which script the PageDown is assigned to.
Now, if you don't want to tackle the actual cause of the error within the
actual script file, delete that assignment from the PageDown key...but I do
urge you to take the plunge and try tracking down that little bugger! Here
is how to take it one step further.
1) Save and Close the Keyboard Manager with an Alt+F4, and select "Yes" when
prompted to save the changes. (If you didn't delete that assignment, then
it will simply close without prompting.)
2) Back in Notepad, hit Insert+0. You'll be dumped into the Notepad's
script file.
3) There can't be that many scripts in this file, so you can use the down
arrow key to move down the listings, stopping on the one that you noticed
assigned to the PageDown key in the Keyboard Manager.
It's a good idea to hit Insert+6 and then hit Alt+S to get to the Settings
menu of the JFW configuration Manager and hit Up Arrow to Synthesizer... In
here, set Punctuation to All and whack Enter.
Hit Alt+F4 and answer "Yes" when prompted to save settings for the Script
manager program's own script file.
Where were we...oh yes...Now hit Control+S and see if the script file
compiles without any errors. It will probably have one--the one causing the
error to begin with, and it will place you on the offending line.
Here is where you'll start getting queasy, especially if you don't write
scripts enough to know if there is a left or right paren missing, a quote
out of place, or a comma in the wrong place. These types of errors are the
most common, and the error message itself will give you an indication of
what type of problem you're facing--albeit cryptically.
One that I've found most is the "Extra command" error, (or words to that
effect), and it is when there are a set of parenthesis on the line that says
"EndScript()". Those puppies shouldn't be there!
See why we set punctuation to All setting?!
Also, another frequent glitch is the ending right paren is on the line below
the function's name and left paren, like this:
SayFrameAtCursor(
)
And at this stage, if you can't locate the problem, then I'd Suggest exiting
that file without compiling, and go back to the Keyboard Manager and delete
the assignment as mentioned above, and contact HJ via a nastygram, then
since you'll get a "Wish you were here..." e-mail message as a response, one
of us users here will have it fixed and e-mailed to you within a couple of
hours. And when HJ does get back to you, you can let them know that it was
fixed back in 1999.
Hope this helps!
A question for a script guru on this list...is there a easy means of going
directly from finding the key assignment in the Keyboard Manager to the
Script Manager and still have the correct script file loaded when entering
the Script Manager? Sure beats exiting the KM back to the application, then
invoking the SM to get to the appropriate script.
What about a setup on the same lines of the SysEdit, where it gives the
Autoexec.bat, win.ini, system.ini, and config.sys all in a window where the
user just Control+Tab to each file? Having the Keyboard Manager, Script
Manager, Frame Manager, and Configuration Manager all in an area with the
appropriate file loaded would speed things up a bit!
Thanks,
Dennis Brown
[EMAIL PROTECTED]
-----Original Message-----
From: Scott Van Gorp <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wednesday, February 03, 1999 5:42 PM
Subject: call to function question
>Hi List,
> Ever since installing the notepad scripts, I've encountered a strange, but
>not unfamiliar behavior. When I press the pgdn key, I hear the message
>"Unknown Function Call to Check". This appears to be similar to the
>"Unknown function call to extended selection status" in Word '97 which can
>be fixed by deleting the .jf* files associated with the winword scripts.
>Where is the fix for this problem in the notepad scripts? Are there some
>frame files which can be deleted, or is there another culprit for this
>minor bug?
>
> Thanks
>
>Scott
>
>Scott Van Gorp
>NWC/RSC box 1179
>208 8th Street S. W.
>Orange City, Ia 51041-1919
>(712) 737-1424
>e-mail: [EMAIL PROTECTED]
>-
>Visit the jfw ml web page: http://yoyo.cc.monash.edu.au/~nallan/jfw
-
Visit the jfw ml web page: http://yoyo.cc.monash.edu.au/~nallan/jfw
