On Jun 29, 2013, at 2:12 AM, Richmond wrote:
> The main reason we need to be able to put unicode in a script is so that one
> can write:
>
> put "!@#$%^&*() into fld "output1"
>
> rather than a whole chain of extremely tedious numToChar statements.
That particular example works now and doesn't
Richmond, unicode in script is what I'm waiting also, but you can set substack
with "library" of fields containing Unicode text and then use "put unicode" in
your scripts to populate the text into your destination fields. You don't need
to use numToChar.
Marek
__
On 06/29/2013 04:07 AM, Mark Wieder wrote:
Richmond-
Friday, June 28, 2013, 11:27:41 AM, you wrote:
set the script of btn "unicodeTest" to fld "Nonsense"
Because "set the script of" doesn't put text into the script editor's
script field, but instead it triggers the engine to compile the
scrip
Richmond-
Friday, June 28, 2013, 11:27:41 AM, you wrote:
> set the script of btn "unicodeTest" to fld "Nonsense"
Because "set the script of" doesn't put text into the script editor's
script field, but instead it triggers the engine to compile the
script. So your beef isn't with the Script Editor
On 06/28/2013 09:24 PM, Mark Schonewille wrote:
Hi Richmond,
Almost every current development tool can do that, except for
LiveCode. What we need is a UTF8 script editor.
Um!
That doesn't sound all that good.
What I do not understand is, if the script editor contains a field
"Scripts" in w
Hi Richmond,
Almost every current development tool can do that, except for LiveCode.
What we need is a UTF8 script editor.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK:
I wonder how one can enter unicodeText directly into the script editor?
When one wants to put a script into an object without opening the script
editor one does this sort of thing:
set the script of btn "unicodeTest" to fld "Nonsense"
now, if fld "nonsense" contains unicodeText that just ends
