beta 5.605 won't close file

Or rather, it doesn't clear the screen when it closes the file being worked on.

P4, WinXP

Roger

Comments

Closing windows

Hi,

Since issuing version 5.605 it has been brought to my attention by Rick Tarara, that there are numerous other bugs. I made the foolish assumption that once a particular feature could be demonstrated to work correctly that it was safe to proceed to the next feature. It now appears that when you multiple windows open with very large files in the text editor, then all sorts of problems occur. The second discovery is that testing a feature several times is not good enough. After 256 times the find-replace feature crashes. After 20 or more maximize and return to normal actions, the system also crashes. There are several other features that fail to work after long repeated usage. Most of these problems are also common to version 5.5b19 and since the new editor uses this version as its basis these problems will persist. In some cases I have found a way to intercept the crash before it happens but the remainder are still there.

Version 5.5b19 has several other bugs, for example text highlighting using the keyboard doesn't self cancel. You cannot highlight the last line of code. The delete key crashes the system if it is used at the very last character in the text editor. Again some of these problems can be overcome but not all.

I am working on version 5.606 which will include many work arounds for the above problems, including the one that you reported.

I have been aware that the textedit control in version 5.5b19 is flawed so I have written my own version of the textedit control that doesn't use the OBJECT sub-routine. Essentially this should be free of most of the above problems but it takes time to test out the new control and even more time to substitute this into the new editor. It obviously cannot sort out the bugs in the interpreter in version 5.5b19.

For many years I have been an advocate of version 5.31 as the most stable and bug free version ever produced. I am now even more convinced. Sadly the source code for this version no longer exists.

Big John

Big John; How about scrap it

Big John;

How about scrap it and adopt Crimson?

Save yourself a lot of grief that way.

Roger

Crimson

Hi Roger,

Believe me, I thought about it many times!

Big John

Crimson

Just looked at this (for all of 5 minutes). If someone could customize the editor to run the TB do programs (I only ever use DO FORMAT), and then link to the tbsystem to run the file, I think I could live without an error window (errors are backlogged in the Command window).

The big advantage of the embedded editor is for those of us who tend to write large programs but programs that can be run and tested as they are being written. That is, structuring with lots of subroutines, each of which can be tested as soon as written. Having to move the source file from one editor to another constantly would not suit my style of programming well. I'm going to assume that no one here has actually outlined a program since their first programming class--if then. TrueBasic is especially good for the 'stream of conciousness' programmer, but the embedded editor, even a buggy one, is all but essential. [I have to admit to never actually trying to work with an external editor--but can project the problems.]

;-)

Rick
www.saintmarys.edu/~rtarara/software.html

Crimson

Rick;

Crimson can run DO FORMAT as well as the TB system, just as the TB editor can.

Personally, I still prefer the DOS TB editor. It makes duplicating lines and moving blocks of text around much easier that the Windows select-cut-paste routine.

Roger

Cut/copy/paste

Hi Roger,

Unfortunately the standard TextEdit control suppresses the function keys (F1 to F10) otherwise the new editor could duplicate the action of the old DOS editor.

When I get my own version of the TextEdit control fully operational, then you can have F4, F5 and F6 working just like the DOS editor. You can also have right click menus too.

A recent change in the new editor allows me to use any previous version of TB as the core. Until now I have been restricted to version 5.5b19 but this has so many bugs that it has hindered progress. Currently I am using version 5.31 as the core and this is much more stable.

Regards
Big John

Re: Crimson

I would be interested in how to do this. I can setup the TBSYSTEM as a tool in Crimson, but that opens a file dialog box to open a file. Is there a way to get TB to directly run the file in Crimson.

What about the DO FORMAT. This do program seems to be embedded in the editor/system--that is, I don't see a separate file for this. So how does one get Crimson (or another external editor) to run something like that.

Rick

Do Format

Hi Rick,

DO FORMAT is included in the editor as a built-in sub-routine, but it is also available as a stand alone DO program.

I have revised the new editor (5.606) so that it can use any version of TrueBASIC as its core. In other words it works like Crimson and chains to the TBsystem file, although this is transparent to the user. The new editor generates a coded argument that it sends to TB system.exe that suppresses the usual dialog box so the user is not aware that the compile/run/bind operation has been chained. Older versions of the TB editor also worked this way. I can let you have details of the coded argument because I am sure that it would work with Crimson or any other third party editor.

Regards
Big John

Rick; Yes, Crimson can run

Rick;

Yes, Crimson can run TB on the file opened by Crimson. Under the Conf tool menu there is a line called Argument which needs to be set to filename. The next line should be set to directory.

Do Format needs to be run by the TB editor. I think Crimson can do it but the directions have been lost in my many HD reformats.

Roger