Editor error message

Archiver

Editor version 2 beta 2.1 using PBASIC 2.5 and bs2p stamp.

While saving files I got "List Index out of bounds" error message.
It apparently did not cause any damage but I am still curious what it
means and how to avoid it. I could not find any reference to this
message in the documentation and I was unable to duplicate the error
in subsequent editor sessions.

Marylou

Archiver

In a message dated 12/13/2003 2:50:39 PM Eastern Standard Time,
astumpf999@y... writes:


> While saving files I got "List Index out of bounds" error message.
> It apparently did not cause any damage but I am still curious what it
> means and how to avoid it. I could not find any reference to this
> message in the documentation and I was unable to duplicate the error
> in subsequent editor sessions.
>

This error will occur sometimes when you replace the programs in the various
slots with another program. I simply ignore it, reopen the Editor and call up
my program. It is apparently harmless.

Sid Weaver
W4EKQ
Port Richey, FL


[noparse][[/noparse]Non-text portions of this message have been removed]

Archiver

> > While saving files I got "List Index out of bounds" error message.
>> It apparently did not cause any damage but I am still curious what it
>> means and how to avoid it. I could not find any reference to this
>> message in the documentation and I was unable to duplicate the error
>> in subsequent editor sessions.
>>
>
>This error will occur sometimes when you replace the programs in the various
>slots with another program. I simply ignore it, reopen the Editor and call up
>my program. It is apparently harmless.
>
>Sid Weaver
>W4EKQ
>Port Richey, FL
>

I too see that error, quite often. It happens when I have a
multibank program written and working, and I want to use that as a
starting point for a new program. I "save as" each of the program
banks under a new name, and in the bank zero program edit the {$STAMP
...} directive to refer to the new names. But when I close that
program (now confused because of the name changes), up pops that
error message. I think Sid is referring to a similar thing. And
like he says, it is apparently harmless. After I close the error
dialog, I can immediately load in the program under the new name and
commence to revise it. Maybe someone else knows, is there a more
elegant way to use one program as the starting point for another,
with multiple banks?

-- Tracy


-- regards,
Tracy Allen
electronically monitored ecosystems
mailto:tracy@e...
http://www.emesystems.com