#ACCESS 1.4 comments
8 messages in this thread
Keith:
I Just downloaded your new Access! 1.4, and it looks pretty good. A
couple of comments, however:
1) When it does a NewCLI, it puts a close gadget in the cli window.
However, the close gadget doesn't get rid of the window; it just stops the cli.
So, I'm stuck with a window that doesn't do anything and that I can't get rid
of. And, if I try LACE with this window on the screen, it tells me to close all
windows first; but, since I can't close the window, the program just hangs.
2) I managed to get the program to GURU, by dialing a lot of numbers. I
think the problem had to do with hanging up while a script was still running,
and then dialing out on a new number (with its own script). If I can duplicate
this, I'll let you know.
3) I put the Access screen into the back, and moved Workbench to the
front (with a cli open). I tried using RD to look at a file (through the cli).
The screen flashed, but I didn't see the RD display; I just assumed that I
disn't have enough memory. When I switched to the back, where Access was, I
found the RD display. Perhaps RD should see which screen is in front before
assuming it was called from Access.
Well, that's it for now.
Jeffrey Cohen
Jeffrey,
Lemme' see if I can touch on those…
"NewCli window dies but doesn't go away" — yes, I've only recently seen this
myself, it's been working fine for me for the most part… I'm looking
into this now, but until I get it worked out you can also close that window
by entering 4 (5?) control '\' charactors.
"dial,script,hangup,script,guru" — hmmmm… I hadn't tried that, but thought
I had code in there to prevent just that sort of thing, I'll have to look
into it… in the mean time (grin), you can stop a script at any time by
clicking on the SCRIPT gadget while one is underway (you might also want
to make sure a script has stopped before quitting the program). ]."RD lives
on Acc!" — When I first made 'rd' a seporate program I wanted it
to find Acc!'s screen to pop up on so that you could get one going as a
seporate process from a CLI… now it detaches itself from the CLI it's
called from, so I guess it would make more sense to let it come up on the
'front screen' at the time it was called… ok, consider it done <grin>.
(btw, it doesn't actually assume it was called from Acc! currently, it
just looks to see if Acc!'s screen is up and opens there if so, otherwise
it comes up on Wbench).
Thanks for you comments,
Keith
Keith,
I have had a few hangups and crashes today, apparently involving the
multi-dial feature. No clear explanation (or even description). It may have
nothing to do w/multi-dial, but I was using that feature a lot today, and had
the hang (can't ESC out of the dial, cant use any of access!' features/buttons.
The only thing I can do is L-Amiga-N to bring the WB to fron, and do stuff
there. A! is totally dead. Also, an odd thing happened today. I was DLin
using QB, and got a disk full condition. I moved stuff off the target disk,
and resumed (took about 2 minutes). When QB restarted, it went at the rate of
1 block every 30 seconds! It finally timed out much later. I don't think this
is necessarily a problem with Access, since my system has been anomolous today.
Forinstance, When I told QB the filename was DLXXXXX:RIM.ARC, it started
writing to the disk in DF2:, which was not DLXXXXXX:. An INFO command showed
that the system thought I had three floppies in, my WB, my A! disk, and the
DLXXXXXX disk. I only have DF0: and DF2:, with DF1: ASSIGNDEVed to DF2:.
There may be an ASSIGNDEV problem, which screwed up the disk system, which
screwed up access, I'm not sure.
-tc
Hmmm… problems w/multi-dial… are you also using scripts with the numbers?
or are you having problems while it's just rotating through the numbers?
As to your second problem… I haven't a clue (sun spots? 8)
– Keith
I am using the same phone book as before, maybe there's an incompatibility (and
I did play w/scripts for a while earlier, that could have been it, too).
As for the second problem, again, It seems completely unrelated to Access
(please get rid of that damn !). If I did a DIR against DLXXXXX:, it
recognized the wrong disk, too (And yes, there was no assign to it). I only
had ASSIGNDEV for a DMCS or DPAINT compatibility, I think I'll call EA and do
it right, and forget about DF1:.
-tc
1.4 will use the same phone books as 1.3a…. maybe that problem too was
sun-spot related <grin>… Seriously, if you can narrow it down any ad/or it
happens again, lemme' know.
– Keith
Nah, couldn't be sunspots. I looked earlier today (yesterday actually) and
there were only 2 medium sized ones …. I didn't even see the mulit-small ones
that usually tag along with such groups.
Aha, maybe it was the _lack_ of the mulit-small ones that caused it.