TxEd+ bug
12 messages in this thread
I'd like to report the following problem with TxEd+. Using the following
startup-sequence:
mount vd0: dir > nil: vd0: runback -4 c/FaccII RTClock /R c/ScreenBlanker2
240 c/ff Resident c/copy c/dir c/list c/info c/cd c/delete runback -S2000
c/funkeys -R "ram:qs\N" "ram:rm\N" stack 4000 c/setfont clean 8
and then running TxEd+, if I highlight the "User" menu option of Txed+, I
will get guru 00000003.00C02672 every time. If I run the same sequence
without either the Vd0: or faccII, then no problems. If I use both VD0: and
faccII then I get the guru. However, if I mount VD0: use TxEd+ and then
FaccII, I can run TxEd+ plus again after that without problems. Also,
several people now (me included) have found that the userdocs.arc file will
not unarc, as the disk has a read/write error, which would indicate a problem
with the master disk.
George Glines 74206,2624
Sorry about the USERDOCS.ARC file error; you can send back the disk
and I'll copy it over for you, also the same USERDOCS.ARC file
is in DL9 here.
.
The menu thing seems to be an Intuition bug, having to do with
an empty menu strip. I guess nobody else has included an empty
menu strip before; it only shows up when some combination of
programs has run. I'm going to work on that for the bugfix
release coming RSN-
…cheath
Cheath, whenever I open TxEd+ I get an "ARexx macro" error. Any idea why?
Marlene
Marlene,
Create a "Start.TxEd" file, even if it doesn't do much (like set the
TAB size). Then put it where TxEd can find it. I have mine on my REXX:
subdirectory (properly ASSIGNED). That should do it.
Lloyd
Lloyd, clearly a case of "RTFM" – I just found out that TxEd+ is looking for
Startup.txed in Chapter 4 of the manual. Thanks, Marlene
Marlene,
Don't worry. I was about to leave the same type of message myself
until I tried it!
Lloyd
Twas a minor misjudgement on my part; if you've got AREXX running,
I assumed you would have a startup macro so issue the error
warning. In the next rev, I'm only going to issue the warning
if you have explicitly specified the name of the startup file,
and it is either not there or AREXX isn't up. You can just
ignore the error message, or create a "rexx:startup.txed" file
to make it happy-
…cheath
Thanks Charlie, I had just installed the new version of ARexx and TxED+ and
hadn't gotten around to a startup macro – I found the answer in the manual –
but I agree it shouldn't issue and error because there isn't one.
BTW, TxEd+ looks great. ARP, WSHell, ConMan, ARexx and TxEd+ are an
incredibly powerful combination that I hope everyone will take advantage of.
Marlene
Charlie, if you want to wait on sending mine to send me the bugfix release, I
won't mind if it isn't too long!
Ron
The bugfix will follow ASAP, but not that soon, I need a couple
weeks of work to put together AREXX macros as well as fixing
the bugs and misjudgements. Hope I'll finish the stragglers
tomorrow and make a sweep of my email baskets on Thursday-
…cheath
Thanks, I appreciate the reply.
George
George,
I had seen the same problem, but I had attributed the flaw to WShell. If I
read your message correctly, you found the same solution I did, which was to
move FaccII to the end of your startup-sequence. But that seems to only
postpone the guru in my case, although I rarely go so long as to actually hit
it. Marathon sessions will bring it out. If it is an intuition error, I
guess we need to fill up those user-defined menu options!
… Brian