LiveCode Forums.

I just set up a stack containing a scrolling list field "SLF"
and 2 other fields: "KLICKT" and "LNVAL"

The field "SLF" contains this script:

on mouseDown
put the clickLine into fld "KLICKT"
put the value of the clickLine into fld "LNVAL"
end mouseDown

According to the prefs palette for fld "SLF" the text is locked.

-----------------------------------------------------------------------

Then I set up 2 buttons; "Lock Fields" and "unLock Fields" containing these scripts respectively;

on mouseUp
set the lockLocation of fld "SLF" to true
set the lockLocation of fld "KLICKT" to true
set the lockLocation of fld "LNVAL" to true
end mouseUp

on mouseUp
set the lockLocation of fld "SLF" to false
set the lockLocation of fld "KLICKT" to false
set the lockLocation of fld "LNVAL" to false
end mouseUp

The script in fld "SLF" did what is was meant to do regardless of whether the fields
were locked or not.

--------------------------------------------------------------------

My stack is here: https://www.dropbox.com/sh/ja47l87gg87s ... C5ORa?dl=0

File "locked.livecode.zip"

Hi Richmond,

sure you didn't want to set the LOCKTEXT of your fields to true/false?


Best

Klaus

Klaus . . . possibly.

New version here: https://www.dropbox.com/sh/ja47l87gg87s ... C5ORa?dl=0

2 buttons: "LockText" and "unLockText"; they don't seem to make ANY difference
whatsoever to the 'clickability' of the textLines.

Richmond...

2 buttons: "LockText" and "unLockText"; they don't seem to make ANY difference
whatsoever to the 'clickability' of the textLines.

They won't make any difference since you are using a 'list' field !.. That is what a 'list' field is for... You will only see a difference if you use a 'text Entry field', it will then only return the clickline and its value if 'locktext' is set to true...

Aha.

So, why was Dr Hawkins "going all funny" about clickability of fields?

Maybe ALL he had to do was change the type of field he was using??????????????