interesting conundrum...

[Chipp Walters]

Hi Richard, not sure how rawKeyDown works for this as the text in a field is
changed via script, not a keypress.
Yes, the setProp for built-in properties would do just fine, Or as Scott
mentioned a textChanged message.

Funny story. All of a sudden my fields in my Matrix project quit reacting to
the mouse scroll wheel. The thing is, this particular project has tons of
scrolling fields, but none of the vscrollbars are shown, as they use my
custom color schemed implementation of scroll bars-- which worked fine pre
3.5.

Then I remembered a thread on the subject over at Improve, looked it up, and
saw where in 3.5 no longer fields w/out scrollbars react to the scroll
wheel. A long discussion ensued where Kevin finally agreed it is the proper
behavior, with the last message an affirmation by me of his decision. Hah!
Had to go back and use a rawKeyDown handler in my custom scrollbar library
to fix it.

Now, I just need the custom scrollbars to update themselves when text is put
in their linked field via script. I can of course do it anytime someone
clicks in the field, just not automatically via script. I suppose I'll need
to edit those scripts which udpate the fields.

On Mon, Apr 27, 2009 at 8:30 PM, Richard Gaskin
<ambassador at fourthworld.com>wrote:
>
>
> Short term (I know you'll love this <g>):  use a frontScript with a filter
> to trap rawKeyDown and update some global whenever the key event is
> modifying a field.
>
> Long term: getProp and setProp for built-in properties
> http://quality.runrev.com/qacenter/show_bug.cgi?id=3126
>
>
> In other words:  situation FUBAR. ;)