the mouseText and Unicode
Mark Schonewille
m.schonewille at economy-x-talk.com
Sat Jun 18 05:27:39 EDT 2011
Hi Jacque,
That's wrong for unicode, because it will catch one NULL too many, either at the beginning or the end of the string, depending on whether it is small or big endian (which depends on the processor that LiveCode is running on).
If you're really desperate, you might use this approach and and delete that extra NULL.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
KvK: 50277553
New: Download the Installer Maker Plugin 1.6 for LiveCode here http://qery.us/ce
On 18 jun 2011, at 06:33, J. Landman Gay wrote:
> On 6/17/11 11:07 PM, Slava Paperno wrote:
>
>> Is there an equivalent to the mouseText, or the mouseChunk, or the
>> mouseCharChunk that is Unicode-aware? Or some ingenious way to retrieve the
>> word that the user clicked?
>
> Does the "word" delimiter work? If so, you could try this in the field:
>
> on mouseUp
> get word 2 of the mouseCharChunk
> put the number of words in char 1 to it of me into tWordNum
> put word tWordNum of me into tWordClicked
> -- do something with tWordClicked
> end mouseUp
More information about the use-livecode
mailing list