Hi Mark,
Yes, your script works very fine, but I cant type the text into field when its lockText property is set to true.
Once more from the beginning, I'd like to have possibility of this field to:
-
type into (with unicode characters - like ąśźĄŚŻŁ etc.)
- select chunks (all words or continuous groups of words - by doubleClick or mouseDown-drag)
- select line (not problem if I can do the rest of this points)
- delete or copy selected chunks
- paste into selected chunks (replace or correct them after paste)
- remove or ignore any formatings when paste text from different sources with applied text formats
I don't understand what you mean with "if there are ASCII character only"
I can do it without problem
"if there are ASCII characters only" - means that I can do it until there are unicode chars in the text. Even one of chars as "ąśźĄŚŻŁ" in the text makes my script impossible to work correctly (fulfills all 6 rules from points above)
If I use your text like śmióaśw and even ąśźĄŚŻŁ then my script seems to work fine.
Yes, but you can't type into replace selected text because the textLock set to true.
RunRev staff made great job introducing unicode text manipulation in LC5.5. Do you think that this stupid probably small and easy to catch bug should fall down their hard work? If I am on their place I'll make it the highest priority to finnish completely one block of new futures.
This bug makes new text manipulating futures of LiveCode v.5.5 useful in few percent only when using unicode (even UTF-16 native for LC). In my opinion it's worth additional time to finnish such expected futures as unicode conformity. Without that we are still limited to use english language only in our software. As I see it's the only limitation of LC to be perfect for developing of text manipulating software all lover the world (not only english language as now).
I have not your private email address. If you decide to "speak" about it outside of the forum, please feel free to contact me on my mail: [nm at studionm dot pl]
Marek