Reassurance re: crashing

Wolfgang M. Bereuter wmb at
Fri Jun 7 03:11:01 EDT 2002

am 06.06.2002 23:59 Uhr schrieb use-revolution-request at
unter use-revolution-request at

> One other suggestion: become familiar with the Application Overview
> window and all it's facilities.
I m still working on a description of Application Overview´s problems. (see
post to improve list). Because Application Overview could/should be the hart
of rev, but is still its 'Archilles heel. I m fighting for improvment of it
since 2 years. It seems that the rev team does not understand the
importancte of a good Appl ov. I think this can decide the future of the
programm. So pls help me to make it clearer to them...
>> I think that--except for those cases--Revolution should not crash.
>> Ever.  So I would not characterize "non-crashing" approaches as
>> "correct" approaches, but simply temporary workarounds.  This might
>> sound like I "demand perfection", and maybe so, but only in a
>> positive sense,
> I agree.  And to that end, the better we are at identifying "crash
> courses" the quicker the RunRev team can generate fixes to protect us
> from ourselves.  Once a "crash course" can be verified & replicated,
> programming a lock out should be higher priority than new
> development.  Unfortunately, none of the issues I raised above are
> described in enough detail to replicate.


Wolfgang M. Bereuter

Learn easy with trainingsmaps©

INTERNETTRAINER Wolfgang M. Bereuter
Edelhofg. 17/11, A-1180 Wien, Austria
..............................., wmb at
Tel: ++43/1/ 961 0418, Fax: ++43/1/ 479 2539

More information about the Use-livecode mailing list