Feeling a bit "NumToCharred"...

[Richmond Mathewson]

Wl, here I go again; replying to my own message:

On 18/12/2009 19:58, Richmond Mathewson wrote:
> I popped this in a button:
>
> on mouseEnter
>    set the useunicode to true
>     set the unicodeText of fld "GUFF" to numToChar(43)
> end mouseEnter
>
> and I get a '+' in fld "GUFF" - exactly as wanted.
>
> BUT . . .
>
> on mouseEnter
>    set the useunicode to true
>    set the unicodeText of fld "GUFF" to numToChar(7749) && numToChar(43)
> end mouseEnter
>
> does not give me char 7749, a space and a '+'; it only gives me char 
> 7749 and a space
>
> I wonder why?
>
> Probably my syntax is incorrect . . .
----------------------------------

useUnicode throws a tantrum with "&&", as it does with " ", so
everything (which is incredibly tedious) has to be down the
numToChar way (i.e. no mixt forms):

on mouseEnter
    set the useunicode to true
    set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32) 
& numToChar(43)
end mouseEnter

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

What a pain in the bum!

To my mind a mixt syntax, whereby characters accessible only via 
numToChar could
be mixt with those directly accessible via the keyboard would be more 
intuitive.

Compare:

set the unicodeText of fld "GUFF" to numToChar(7749) && "a b c d."

to

set the unicodeText of fld "GUFF" to numToChar(7749) && "a" && "b" && 
"c" && "d" & "."

to

set the unicodeText of fld "GUFF" to numToChar(7749) & numToChar(32) & 
numToChar . . . . . . . . . . . . frankly cannot
even be bothered to work it out . . . time for some coffee . . . z z z

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

A mixt syntax would save me (even if no-one else) hours and hours of 
typing, fiddling around with unicode numbers
for trivial characters, and merry repetitive stress injury.