Quitting standalone, is this a bug?

Mark Smith mark at maseurope.net
Fri May 18 12:35:01 EDT 2007


Michael, I certainly don't claim to have the ultimate wisdom  
regarding this, but if memory serves, there have been a number of  
discussions on this list regarding ambiguities in the use of 'me',  
'this', 'the target' and other words in Revolution.

I think the consensus has been that these ambiguities arise as a  
result of historical issues in xTalks (particularly Hypercard), and  
that there isn't much agreement on how, or even if, these ambiguities  
could or should be eliminated.

The solution is to use explicit references where these ambiguities  
arise, and though you may well be right in calling what you have  
encountered a bug, it does seem that there isn't an obvious or  
generally acceptable way to resolve these ambiguities - explicit  
references work well, so I can't see the situation changing very soon.

see http://quality.runrev.com/qacenter/show_bug.cgi?id=3419

best,

Mark



On 18 May 2007, at 17:10, Michael Binder wrote:

> Hi everyone,
> after another round of research I have found that I am not the  
> first to
> stumble on this bug....
>
> On Jan 19, 2006 at 10:35 PM Steve Wagenseller posted to the list:
>
>> I'm trapping the Quit message from the menubar via a shutdownrequest
>> handler, but in the standalone, something curious occurs. The first
>> time I choose "Quit" I can get the trap script to run (basically, an
>> "Are you sure?" prompt along with some save options). The second time
>> I choose Quit from the menu, the trap is not implemented.
>>
>> I am not passing the handler along, it sits at the stack level, and I
>> am using an "exit to top" to get out of the shutdownrequest handler
>> when "Cancel" is chosen.
>>
>> Have any of you experienced this strange problem -- that the trap
>> only works once -- and do you have suggestions?
>>
>> --Steve
>
> I do wonder if this bug is more prevalent than just the two of us.
> In order to find this bug you have to quit, cancel quit, and then quit
> your standalone a second time.  You won't catch this bug in the
> development environment.  How many standalone developers have actually
> tested their apps in this way?  One more thing... I do not have
> access to a windows system, so for all I know this bug is specific
> to the mac.
>
> --Michael Binder
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the use-livecode mailing list