More 2.5 weirdness

Marian Petrides mpetrides at
Tue Sep 28 07:53:38 EDT 2004

Ummm.... I haven't used 2.5 enought to have run into this anomaly, but 
it sounds like several people have encountered it but not bugzilla'd it 
because of lack of recipe.  How can we expect RunRev to fix something 
that they haven't even been informed of?  Shouldn't someone bugzilla 


On Sep 28, 2004, at 7:50 AM, Dan Soneson wrote:

>> On Sep 27, 2004, at 5:18 PM, J. Landman Gay wrote:
>>> On 9/27/04 4:39 PM, Howard Bornstein wrote:
>>>> Boy, V2.5 is now starting to act very squirly. I get into a 
>>>> situation
>>>> where combo and popup buttons will no longer pop open. Not only the
>>>> buttons on my stack, but also the buttons on the property inspector.
>>>> So the little Arrow button at the top-right of the inspector no 
>>>> longer
>>>> works, the popup, which show Basic Properties as its first choice
>>>> doesn't work, etc.
>>>> Most other things seem to work. This happens after my script sets 
>>>> the
>>>> labels of some combo-buttons in my stack. That's about the only 
>>>> thing
>>>> related that I'm doing that I can think of. Closing a stack and
>>>> re-opening it doesn't fix this. I have to quit and restart Rev.
>>>> Anybody seen this?
>>> Yeah. In the property inspector, same as you describe, where the 
>>> popup
>>> that lets you change from "basic properties" to the other sets 
>>> doesn't
>>> pop down. I wasn't changing any labels on anything, so I have no clue
>>> what caused it. I haven't bugzilla'ed it yet because I can't figure
>>> out a recipe.
>> I saw this for a while but like you was never able to come up with a
>> recipe so never Bugzilla'ed it.  I will say, however, that the problem
>> arose at the same time that I created a really wierd infinite 
>> recursion
>> through a preOpenStack handler in a main stack which did a time 
>> delayed
>> call to another handler which opened a different stack which did not
>> have a preOpenStack handler so the main stack's preOpenStack handler
>> got called, etc. etc. etc.  When I got rid of the recursion, my
>> property inspector worked again too although I can't begin to explain
>> why the recursion would cause the behavior I saw in the inspector.
> I get it too, but there seems to be no consistency. Luckily, I can 
> still
> save the current stack, quit Rev and re-start it and all is well for 
> awhile,
> but it is disconcerting.
> Daniel B. Soneson
> Director, Language Lab
> Southern CT State University
> _______________________________________________
> use-revolution mailing list
> use-revolution at

More information about the use-livecode mailing list