Again, I tested this and it works as expected. Going to another card does in
fact send the closeField message to an edited field that has focus, which not
being trapped, makes it's way to the card script and executes.
Bob
On Dec 19, 2010, at 4:04 PM, Robert Brenstein wrote:
> I can second th
Bob,
This is indeed not working as expected, and nothing else is intercepting the
message first. It just isn't being sent. I've been trying to mess with
Jacque's suggestion, but that didn't help matters, so because I'm less
interested in figuring out what weirdness is in play and more interested
Instead of changing the behavior of closeField (and all the hoopla that would
arise by everyone's stacks suddenly acting differently), how about a new
handler? Something like alterField or changeField? Seems to me, closeField is
just that. The field is closed. Setting the text of a field is not
Well... hmmm... I dunno. I like to enable special behaviors for my fields in
the card script or the stack script, check for the existence of a custom prop,
if it exists handle it, if not pass closeField. That way new fields work just
fine, but I can add a custom prop to enable the special behavi
Just tested works fine. I have a closeField handler in the card script, a field
and a button. The button goes to card 2. The closeField handler beeps twice.
When I click the button after editing the field contents it beeps twice. That
means the card script is in fact getting the message.
I sus
On 18.12.2010 at 23:02 Uhr -0600 J. Landman Gay apparently wrote:
If you can't find the reason in your scripts, it might have to do
with the message hierarchy. I've hit the same snag before and ended
up adding a check for "the selectedfield" at the top of the button
script that navigates. I.e.:
I agree completely. It would be good to have a message sent whenever the field
changes for any reason.
Bill Vlahos
_
InfoWallet (http://www.infowallet.com) is about keeping your important life
information with you, accessible, and secure.
On Dec 18, 2010, at 11:53 PM, p...@molly
Thanks for chiming in, everyone!
Joe
I don't want to bore everyone with the details, but this is exactly what I
want - a generic closeField handler. Thanks for looking out for my well
being, though!
Jacqui,
After fiddling around for hours and hours, this is what I suspect as well.
I just haven't
Lots of input on this already but the bottom line is that closeField does
not get sent unless the user, not a script, changes the contents of a
field. In your example, if the script of your button changes the content
of a field, no closeField event will be generated. I get round this by
sending a
On 12/18/10 10:18 PM, Mike Kerner wrote:
Hold up on that answer for a second. I have encountered
something...odd...that I don't understand yet. Perhaps there's some other
handler somewhere that I don't see because trapping this condition
inconsistently demonstrates this problem.
If you can't
Hi Mike,
First, you're not going to want to put a "closeField" handler anyplace other
than the field to which it applies unless all of the fields on the card, or
stack are going to implement something when that message is sent. Really
unusual I should think. I would read the description of "clos
Hold up on that answer for a second. I have encountered
something...odd...that I don't understand yet. Perhaps there's some other
handler somewhere that I don't see because trapping this condition
inconsistently demonstrates this problem.
___
use-liveco
ok, then riddle me this:
I have a field, but instead of putting the closeField handler in the field,
I put it in the card. On that card I have a button that goes to another
card. In that case, the closeField message is not passed to the card, only
if i have the closeField handler in the field.
CloseField is sent only when something in the field has changed. If you
only have focus in a field, and click on a button that sends you to another
card, trap exitfield instead. it is sent when focus is lost, and nothing has
changed.
But in either case, the appropriate message is sent. If you h
OK, if I understand previous threads correctly, closeField does not get send
when you click on a button. So what happens if you click on a button that
does something that causes the field to lose the focus - e.g. navigating to
another card, putting different text in the field, selecting the text o
15 matches
Mail list logo
