realbasic-nug
[Top] [All Lists]

Event timing conflict bug (was:Module property bug)?

To: RB_NUG Group <realbasic-nug at lists dot realsoftware dot com>
Subject: Event timing conflict bug (was:Module property bug)?
From: Boris Segerstahl <boris dot segerstahl at pp dot inet dot fi>
Date: Sun, 29 Feb 2004 17:49:30 +0200
The following bug has now been confirmed by three testers:

Possible timing conflict in editfield.textchange?

Bug ID: pfsrgjia
----------------
Window1 with one property "theprop" as string, editfield1, editfield2.
   Window1.open
        theprop = "test"
        EditField1.Text = theprop
        EditField2.Text = theprop

   Editfield1.textchange
       theprop = me.text

   Editfield2.textchange
       theprop = me.text
----------------
Ide run will not start app but only say "The application... has unexpectedly quit...".
Debugger does not catch it.
In more complicated tests I got the message "dump.ccp: 132 0 overwrote end of block"

One tester assumed it is an Apple bug and not a RB bug. It would, however, be nice if RB protected us from these or at least let us stay on in the debugger. Debugging dies suddenly with the app.

The good news is that this is the probable reason for Richard Rhyan's crashes and everything is OK with the public properties. Richard could try to use an openflag as boolean (I tested it - it works) or change the way he uses the textchange event. I would, of course, recommend both or at least the second.

I might, as always, be wrong. I would be happy if a wise guru can contribute to my education on these matters.

Boris
Ona is howling like a wolf at fullmoon time downstairs. She wants out again.

________________________________
Boris Segerståhl
boris.segerstahl at pp.inet.fi
10.3.2 and 5.5.1fc1

- - -
Unsubscribe or switch delivery mode:
<http://support.realsoftware.com/listmanager/>

Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>

<Prev in Thread] Current Thread [Next in Thread>