textChanged missing in Dictionary

[snm]

It seems that there is missing "textChanged" message in Dictionary entry (LC 5.5.1, Mac Os X)

Marek

[Klaus]

Hi Marek,

no wonder, this new message is called "selectionchanged"


Best

Klaus

[snm]

Hi Klaus,

I don't think so, in my opinion they are two different messages:

The selectionChanged message is sent to a field whenever the user makes a text selection or moves the insertion point in the field, after the selection is changed.

This message is sent even if you click inside the field even without typing or change the text. It was introduced in LC 1.0

From 5.5-dp1 release notes:

The field will now dispatch a message textChanged whenever a user (or simulated user) action may
have caused the content of the field to change.
In particular, the following actions will result in a textChanged message being sent:
• typing into the field (whether non-Unicode or Unicode text)
• using the type command to type into a field
• pasting text into a field (whether via built-in keyboard shortcut, or the paste command)
• cutting text from fields (whether via built-in keyboard shortcut, or the cut command)
• drag drop operations on fields

So this message is sent if you change some content of field and is new one (not selectionChanged replacement).

Marek

[Klaus]

Hi Marek,

you are abolutely correct, my fault, sorry!
Well, the docs are obviously not up-to-date


Best

Klaus

[snm]

What is the most efficient way to claim it?

Marek

[sturgis]

If you click help, release notes, page 14 of the release notes contains information about textChanged. There is also page 36 which mentions that undo does not trigger textchanged.

[snm]

Hi Sturgis,

I know it, but it's easier and quicker to have it all in dictionary, then looking for it in release notes. Specially for people starting with LC.
If newbies can't find it in dictionary they mean that there is not such keyword in the language.
It's not lot of work to do it, I think that somebody forgot to put "textChanged" description in Dictionary, so maybe it's good idea to send kind of remainder somewhere.

Marek

[sturgis]

If you have access to report bugs you can report a documentation bug there, otherwise you could send mail to support@runrev.com detailing the issue. Hopefully the docs will get caught up with the new changes before too awful long.

[snm]

I reported it in QCC.

Marek