At 9:49 PM +1000 10/25/02, Tim James wrote:
1. Am I breaking a RB standard in assuming that control should pass
to the next front window on closing the frontmost. (In IDE that
window's activate event does fire before the crash.)
No, your assumption is correct (except that in OS X, the next
frontmost window may belong to some other app).
2. I ensure that the self.close statement is at the end of the event
handler (an editfield) that received the escape character from the
user that triggers the window close.
That's good.
In various tests I have shown that the crash comes after the the
execution of the windows.close event. Is this legal code behaviour?
I don't understand your question. But the crash might be caused by
something in the close event of one of your controls, or in the
destructor of something your window has (directly or indirectly) a
reference to.
3. Because the application runs faultlessly in classic mode but
disastrously in OS X I have presumed the problem is not in my code -
but is this correct.
No. OS X has protected memory (as does Win32), and so is a lot less
forgiving; the same bug might be occurring in OS 9 but be hidden
there.
However, if you see ANY kind of crash (not an unhandled exception,
but an actual crash) in OS X, then it is probably not your code,
unless your code uses Declares.
OSX 10.2 ,RB 4.5.1fc1 Mac OS X,G4 733Mhz, Valentina Plugin
I'd be interested to hear whether you can reproduce the problem in a
project that doesn't use the plugin.
Cheers,
- Joe
--
,------------------------------------------------------------------.
| Joseph J. Strout REAL Software, Inc. |
| joe at realsoftware dot com http://www.realsoftware.com |
`------------------------------------------------------------------'
---
A searchable archive of this list is available at:
<http://dbserver.realsoftware.com/KBDB/search.php>
Unsubscribe:
<mailto:realbasic-betas-off at lists dot realsoftware dot com>
Subscribe to the digest:
<mailto:realbasic-betas-digest at lists dot realsoftware dot com>
.
|