Invisible insertion point in field

David Wilkinson dwilk at globalnet.co.uk
Wed Jul 20 17:07:53 EDT 2005


On Wednesday 20 July 2005 6:00 pm, Jacqueline Landman Gay wrote:

> To lock/unlock a field you need to set three field properties:
> locktext, autohilite, traversalOn. The last two should be set to
> the opposite of the first one.

Unfortunately they are opposite

As a test, as a result of Jonathon's post, I created a new stack, 
dragged a table field onto it along with a ordinary one.  I grouped 
them, edited the group and dragged another single field into the 
group.  All was as expected - insertion point etc.

I also tried edting the group of the uploaded teststack and dragging 
a new field into the group.  This new field  had no insertion 
point.

That suggests some sort of inheritance issue, but I could not see any 
obvious differences between the properties in the group, card or 
stack of the two examples.  If the edit field is copied from the 
group and pasted onto the card, the insertion point then becomes 
visible.

BTW in order to get left mouse drag of the field, I only needed to 
set the locktext to true - those associated props do not appear to 
change when this is done.

Thanks for your rapid response.  The problem isn't critical but gives 
this table component an additional element of flakiness it could do 
without!

David 



More information about the use-livecode mailing list