closefield-message lost
xbury.cs at clearstream.com
xbury.cs at clearstream.com
Tue Oct 21 05:24:19 EDT 2003
Richard,
You can use exitfield, mouseleave, tabkey, returnkey, and/or a card/stack
message to catch the openfield (which should still work) to
intercept this...
There's always an alternative!
---------------------=---------------------
Xavier Bury
TNS NT LAN Server
ext 6465
bleekerj at xs4all.nl
Sent by: use-revolution-bounces at lists.runrev.com
21/10/03 09:19
Please respond to How to use Revolution
To: use-revolution at lists.runrev.com
cc: ^
Subject: Re: closefield-message lost
> Hello list,
>
> in my current projekt there are two questions (Mac OSX, RR 2.1):
>
> 1) To save changed data in a stack, there is a ToBeSaved-Flag, which
> gets set, if the contents of a field is changed.
> Therefore each field has a closefield-handler, which sets the
> ToBeSaved-Flag.
> My problem: If I click the close-button immediatly after changing a
> field, there is no closefield-message. What to do?
>
>
Richard,
the closefield-message got 'damaged' in v2 See bug #302: no
closeField message sent after clicking a button.
You have to wait for a new release :-(
Greetings,
Jan Bleeker
_______________________________________________
use-revolution mailing list
use-revolution at lists.runrev.com
http://lists.runrev.com/mailman/listinfo/use-revolution
Visit us at http://www.clearstream.com
IMPORTANT MESSAGE
Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message.
The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries.
END OF DISCLAIMER
More information about the use-livecode
mailing list