Re: [StrongED] Re: StrongEd v4.70a12 and Throwback

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <5633676dcalist01@xxxxxxxxxxxxxxxx>
          Martin <list01@xxxxxxxxxxxxxxxx> wrote:

> In article <637d553356.fjgraute@xxxxxxxxx>,
>    Fred Graute <fjgraute@xxxxxxxxx> wrote:
> > In message <5633483bf5list01@xxxxxxxxxxxxxxxx>
> >           Martin <list01@xxxxxxxxxxxxxxxx> wrote:
> 
> > > I have just had a Throwback window after an error in a Basic program.
> > > 
> > > A saved version of the window contained (on two lines)...
> > > 
> > > Errors in : ADFS::HardDisc4.$.!BOOT.Library.WaitPoll.Sect.Diary
> > > Processing: ** Error ** ERR=&1A Unknown or missing variable in
> > > "Sect.Diary" ERL=26019
> > > 
> > > However...
> > > 
> > > 1.  The !BOOT.Library.WaitPoll in the first line is ficticious.
> > >     The first line of Sect.Diary contains
> > >         REM Sect.Diary
> > >     which is relative to the directory of the main program.
> > >     Diary is a library. This worked with that other editor!
> 
> > Which program is casting the throwback messages? StrongED simply uses
> > the path that's passed to it in the throwback message. If the path is
> > wrong then it's probably down to the casting program.
> 
> Hmm. Very good question. It was probably (my) Reporter! 
> That picks up the command line used to start it, removes the initial
> program and adds what it finds in the library REM. 

I assumed that you were using Reporter so I tested with that and it
seems to work fine. Path was correct as was the throwback message type.

[snip]

> > > 3.  The window was only the width of the first line, so there was no 
> > >     way to see the vital "Sect.Diary" ERL=26019 at the end of the 
> > >     second line. How can I change the width?
> 
> > The width should be that of the widest line. Not sure why that isn't the
> > case. Any chance of you providing me with a (cut down) test case?
> 
> I tried a simple case, with a library in a directory ... worked ok.
> I tried with debugging in Reporter and the original case ... worked ok.

I found that if the target file is of type BASIC and can't be found then
the window width is indeed incorrect. This because SE tries to convert
the BASIC linenumber to a physical linenumber. If the file isn't there,
this errors before the correct width is calculated.

I'll make the code more robust so it doesn't error when the file can't
be found allowing the window width to be set correctly.

> I hate problems which hide!
> 
> I suspect my symptoms are all related - but to what I have no idea as yet.
> If (when) it happens again I will try and clarify matters.

I'm wondering if the casting program is using the CSD to get a complete
path. When the CSD points to the main program the path is correct, when
the CSD points somewhere else the path is wrong.

Cheers,
Fred.

-- 
StrongED Developer
http://www.stronged.iconbar.com/

--=20
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxx
List archives at http://www.Torrens.org/RO/StrongED/index.html