Please suggest an easy way to deactivate a fields scripts

Mark Schonewille m.schonewille at economy-x-talk.com
Tue Mar 17 16:07:12 EDT 2009


Hi Willam,

Something like this?


local lSwitch

on rawkeyDown
   if the shiftKey is down and the optionkey is down and the  
environment contains "dev" then
     put (lSwitch is false) into lSwitch // switch on-off
     exit rawKeyDown
   else if lSwitch is false and the environemtn contains "dev" then
     -- run short version of your script here or do nothing
     pass rawKeyDown -- if you want
   else if lSwitch is not false or the environment contains  
"standalone" then
     -- run script as normal
     pass rawKeyDown
   end if
end rawKeyDown

on rawKeyUp
   if lSwitch is not false or the environment contains "standalone" then
     -- run script as normal
     pass rawKeyUp
   else
     -- run short version of your script here or do nothing
     pass rawKeyUp -- if you want
   end if
end rawKeyUp

--
Best regards,

Mark Schonewille

Economy-x-Talk Consulting and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Dutch forum: http://runrev.info/rrforum

Snapper Screen Recorder is now available for Windows! Download it at <http://snapper.economy-x-talk.com 
 >.

On 17 mrt 2009, at 20:31, william humphrey wrote:

> I have a data entry field with a bunch of scripts in it that do  
> things like
> search through a set of data by watching each key stroke. This is  
> fine must
> of the time but occasionally I just want to quickly put some data in  
> it that
> is not evaluated. Presently I use "contents" of the inspector to do  
> that but
> for the final program would like a button you press that says "edit  
> field no
> checks" or something and that button turns off all the scripts in  
> that field
> so you can quickly put in some data. The only way I can think to do  
> it is to
> have another field that pops up and you put the data is and then it  
> closes
> and enters the data in the field with all the scripts. I was just  
> wondering
> if there was a quicker way to do that.






More information about the use-livecode mailing list