I'd like to define what I view as project corruption:
What was described in the previous emails (to me) isn't project corruption,
rather a missing file. It's simple. You just don't save, put the plugins
where they were previously and reopen. No big deal (and no offense intended
to those who are having problems with this).
Here's what I see as project corruption:
You save a project. It saves fine.
Quit RB. Reopen the project and RB instantly crashes.
THAT is project corruption.
And it's happened to me 3 times in the last week.
I've been using quite a bit of external file references for my "stock"
classes (app framework stuff).
Has anyone else seen this?
Here's another fun item:
Project has app class.
App class has an exception handler in the UnhandledException event.
Yet the built application unexpected quits when the user opens the prefs
window. There isn't a single peep out of the error handler. I have
extremely extensive error checking in every class, method, control, window,
etc. I subclass my own errors and add properties for which class, method,
and other information. There are options for debug messages, logging, error
messages, logging, etc. It's worked very well. I have (until now) never
had a built application fail without me knowing exactly when, where and why.
Why would a built app just die like this? It runs completely fine in the
IDE, and I'm not getting any exceptions of any type there. My log files
show all the classes instantiating correctly, the methods being called
correctly etc. Yet the built application's log file doesn't have a single
entry (outside of the header line that gets written on the file's creation).
Am I alone on these items or are other people experiencing them as well?
Mark
|