Cannot enter data in field
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller, robinmiller
-
- VIP Livecode Opensource Backer
- Posts: 7216
- Joined: Sat Apr 08, 2006 8:31 pm
- Location: Minneapolis MN
- Contact:
Re: Cannot enter data in field
Well, the behavior sounds like a field with traversalOn set to false, so I'd check those. If the fields are in a group, check the traversalOn of the group. And if that's not it, check the traversalOn of the stack itself. Somewhere in the object hierarchy, traversalOn seems to be set to false. I'm betting on the stack.
Jacqueline Landman Gay | jacque at hyperactivesw dot com
HyperActive Software | http://www.hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
-
- Posts: 719
- Joined: Thu Sep 11, 2014 1:49 pm
- Location: The Netherlands
Re: Cannot enter data in field
I tried to as last statement in the open Stack section but no luck.
All TraversalOn statements i searched for in the stack are in the picture attached to this post. Cannot find any that could have impact on traversal settings of this stack
I also tried to 'set the travesalOn of this card to true' in the open card section of the card with my test field in it but no luck. problem still persists.
Then I specifically 'set the travesalOn of fld "MyTestField" to true' in the open card section of the card with my test field in it but no luck. problem still persists.
The only clue I have got is the fact that the new card does not have this problem....
Code: Select all
set the travesalOn of this stack to true
All TraversalOn statements i searched for in the stack are in the picture attached to this post. Cannot find any that could have impact on traversal settings of this stack
I also tried to 'set the travesalOn of this card to true' in the open card section of the card with my test field in it but no luck. problem still persists.
Then I specifically 'set the travesalOn of fld "MyTestField" to true' in the open card section of the card with my test field in it but no luck. problem still persists.
The only clue I have got is the fact that the new card does not have this problem....