New App Developed in LiveCode

Pete pete at mollysrevenge.com
Fri Aug 19 12:53:48 EDT 2011


Good spot Bob!  I am relying on the same closeField logic and hadn't come
across that little glitch.

There is an argument that this behavior is correct because the cursor stays
in the field when you click the button so technically, the field hasn't been
closed.

I just used the message watcher to see what messages are sent in these
circumstances and you may be able to use the mouseLeave message to trigger
your validation although it could be that the user hasn't finished entering
text in the field at that point so not sure if that would work correctly or
not.

Pete
Molly's Revenge <http://www.mollysrevenge.com>




On Fri, Aug 19, 2011 at 9:27 AM, Bob Sneidar <bobs at twft.com> wrote:

> Now that you mention this, I ran into a similar *bug* or *absence of a
> feature* where if a user types text into a field, and then clicks a button
> without leaving the field, the field gets updated, but the closeField
> message NEVER GETS SENT to that field. I think this is a grievous oversight,
> as I trap closeField to do on the fly validations, and now I will have to
> tell users of my app to tab out before clicking the button! That is not
> going to work. I will probably have to send closeField explicitly to every
> editable field when I go to save my record. Very dirty.
>
> Bob
>
>
> On Aug 19, 2011, at 9:04 AM, Trevor DeVore wrote:
>
> > * No message sent after text has been entered by the user and stored in
> the
> > field by the engine but BEFORE the text is displayed to the user.
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>



More information about the Use-livecode mailing list