Have you ever received one of these dialogs saying something like:
"Internal error..... You may continue if you wish but should quit
RealBasic as soon as possible..." ? It has buttons for Continue and
Quit.
Running an expendible demo, I elected to Continue and subsequently
lost the project completely. (ohagvxve)
I've never lost a project in Rb before.
I have, in some previous releases of 2005. An easy way to survive
the problem is to always save before you compile, and if that message
pops up and you didn't save, click quit, and when rb asks if you want
to save changes, go to Finder and move or rename the project file,
then click save in rb.
Personally, I haven't seen this nearly as much as in the previous
versions. RB2005r4 has major disk access problems when working in a
disk image - like, NilObjectException EVERY time you compile, and it
also has trouble on my FAT32 thumb drive actually saving a project
file. I don't know if any of this was fixed in 2006, but in 2004,
simply doing all work on an HFS-based volume (except a disk image)
avoided all problems.
Andrew Keller
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
