* Since I'm experimenting with checking memory for both strings, files, and pushspace with arrays, I have more than once crashed the B4GL IDE.
Suggest that when you run your program to check it, you autosave to a file like, just that, saved.gb, no prompt for overwrite or anything, it doesn't interfere with the filename you save manually, it's there just to help you.
Additionally suggest that you also use this autosave feature every 5 or 10 minutes of coding to a file like autosave.gb. Hard-drive's are quite speedy now and there's no need not to backup something you've worked on for hours every 5 to 10 minutes to a single recovery file, maybe add config for # of minutes before autosave.gb file is written to.
If other coders are annoyed by creating two additional files on their HD, you could add config to have either or both turned ON or OFF. I guarantee it'll make someone happy who's been writing code for hours and their computer powers down, or some other background task kills or hangs their OS beyond recovery.
* Ah, but what if you're called away ? Answering the phone or something. You leave for an hour. It might be convenient to have the option for auto-save. Perhaps the option could be if you leave the editor up for a long time without any keystrokes, it saves then.
I guarantee you are working on more than just code. You have a different task up, maybe 20+ like I do all the time. When the phone rings, you don't sit down and hold [ALT] [Tab] to find the B4GL IDE and whack CTRL-S before the phone or answering the front door. If you still can't see the use of this, you're a unique person.
Post by UNDISCLOSED on Apr 22, 2009 13:37:24 GMT -5
With windows 7 it take a fraction of a second to find basic 4 gl: and that is just with one B4GL window, if more than one are opened they show in that wee box and if you hover over it all the other windows go see-through.