Folks,
I've had to forward this to my iPad to send it. I had to update my ssl 
certificate and it buggered the email from my server and I can't send from my 
Mac laptop, but I can from my iPad. Go figure! 

Thanks for your feedback, here is what I found out:

> The long ID of a field looks something like this. I haven’t saved the stack 
> yet, so there is no filename.
> 
> field id 1006 of card id 1002 of stack "Untitled 1”
> 
> I can do:
> put “myEmail” into field “email” and it works fine and to me, serves as a 
> model for syntax variations.
> 
> I can copy that long id to the message box and do:
> 
> put "my email" into field id 1006 of card id 1002 of stack "Untitled 1” and 
> it works.
> 
> I can do, but it doesn’t work:
> 
>    put the long id of fld "email" into tLongID
>    put quote&tLongID&quote into tx
>    put "myEmail" into tx
>  
> This works: (thanks, Jacqueline)
>    put the long id of fld "email" into tLongID
>    do "put" &&quote& "my email" &quote&& "into" && tlongid
> 
> So, this may be obvious to experienced livecoders, but it is bizarre to those 
> less experienced, like me. I'm not complaining, mind you, but there are many 
> such non-intuitive operations in livecode. That's ok, but sometimes the 
> effort to make livecode natural language-like creates new confusions. I also 
> get confused about whether to call something an object, a control, a key, an 
> item (ok, items are obvious), and I only point this out because sometimes 
> information about what hangs up beginners is very useful when creating 
> documentation. 
> 
> Best,
> Bill
> 
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to