#ACCESS1.4
5 messages in this thread
I downloaded ACCESS V1.4 (Oh so slowly with Compuserve B) and have been getting
familiar with it some. You have really provided a beautiful colorful user
interface! It may be confusing to some that your Access!me file says that the
files in the archive include Acc!.keys when it doesn't. I discovered that I
could get Access! to generate one for me. I have been trying to learn about
setting up some script files. I haven't solved a problem: How can I tell
Access! to send a ^C (control-C) code? The Script language is a good start,
but I miss the ability of OnLine! to call MENU functions; like after I
disconnect, all my OnLine! scripts use the MENU functions to close and clear
the last capture bufferand then display the dialing (Phone Book) menu for the
next call. I also miss the function key gadgets at the bottom of the OnLine!
screen that let me use the mouse to hit various function keys (yeah, I'm
lazy!). You are right about the Access! documentation being a bit fragmented
and in need of a comprehensive reorganization, but I have been jumping around
in it and getting my bearings. But please let me know when you have a new set.
Would you like me to "beta test (spell check, etc.) [D" for you? I'd be
willing. I am still using OnLine!, but I am trying to get Access! set up so I
can use it. A nice feature of OnLine! for generating scripts, is the "Learn
Mode". Well, If I like OnLine! so much, why am I writing to you? OnLine! has
warts! Its a sort of love/hate thing. Access! is better in many ways, but
deficient in a few. I am optimistic that Access! will become the BEST terminal
program for the Amiga. Keep at it! Rene'
Rene',
To send a ^C, just: SEND ^C (that should work, just use a '^' and a 'C',
both charactors, a carret (sp) and a C ).
"Learn mode for the scripts"… uh… err…. <shudder>… ok, I'll keep
that in mind <grin>.
I think we've already talked about (I know *I* have in the docs _somewhere_
8) most of your other points (one of which _being_ the docs 8) so I'll not
comment on them (unless there's something you'd like me to comment on).
Thanks for the kind words, I'll keep at it… – Keith
Oh! just use "^C" just like OnLine! does. Good! I couldn't find it in your docs
and never got around to trying it out. Another question: How can I send a
"BREAK" signal with Access?
You can send a BREAK by either using the menu item (in the serial menu) or
through a macro key ( \l for line break)… should this be in the scripts
also? Would be easy enough to do…
– Keith
Thanks for the reply. After I asked, I found that in the document, but yeah,
don't you think that anything you can do with a macro key should be able to be
done from within the script? I think it should be possible to reference a macro
key from within a script and conversely, it should be possible to call a script
by operating a macro key. With OnLine! I have my scripts set up so that when
the system enters OnLine! the dialing menu comes up automatically. Then, when I
dial the number I want, the associated script takes over and get all logged on
with the properly named capture buffer open and all without ever touching a
key. Then, while in the session, I use the function (macro) keys to make
various selections about what I am doing on the board. This is where OnLine!
is very weak, because I can't tailor the macro keys for each number (board) I
dial. I would like to be able to have certain macro keys programmed to call
special scripts that interact with the board for various standard functions
like downloading or browsing messages, etc. Then, when I am ready to get off, I
would like to have a "GET-OFF" script that interacts with the board as
necessary to tell it I want off, no I don't want to leave a message for the
sysop, and yes, I really mean I want to get off. Then it should close my
capture buffer and then bring the phone menu back up again. I can do most, but
not all of this with OnLine. I must use ABORT in the script to make it wait
until I use the menu to RESUME to get into the OFF portion of the script where
it does take care of the OFF stuff and then bring the Phone menu up again, but
I can't set up intermediate scripts to be invoked from the function keys. ALSO,
I can't reference a function key from within the script. These limitations
really make a big dent in the neat things that could be possible. So far, with
ACCESS! I haven't found a way to bring a phone menu up with the script
commands. I haven't done it yet, but I think I can set up a macro key to kick
off the "OFF" function, and then within the script use the ON command to watch
for the proper