Unexpected scrollbarDrag message

[Peter Haworth]

On Wed, May 22, 2013 at 5:13 PM, Alex Tweedly <alex at tweedly.net> wrote:

> Then make the field very slightly less tall - and now simply clicking in
> the field causes a tiny scroll because the insertion cursor is being put in
> the field. And that generates a 'scrollbardrag' which is picked up by the
> handler in the card script. I prsume that because it is generated *from*
> the field, it wouldn't be seen by a handler attached to the field itself
> (to avoid possible recursion ??)


You nailed it Alex, thanks.  The key is that the field is "less tall".
 Actually it's also right justified, not sure if that would cause the same
behavior.

I did put a scrollbardrag message in the field and it does trigger under
these circumstances.  I guess I could use that approach and not pass the
message to stop the card handler from being triggered.


Pete
lcSQL Software <http://www.lcsql.com>