DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR Pending]

Link: http://www.fltk.org/str.php?L2698
Version: 2.0-current


What sort of highlighting are you attempting? fltk::drawflags() has the
HIGHLIGHT flag, which allows you to work all sorts of magic from inside
your (overridden) draw() function. The damage(DAMAGE_HIGHLIGHT); function
call also forces your widget to redraw its highlight.

With reference to the test/subwindow.cxx example, Both ENTER and LEAVE
events are sent, however they're actually sent in the order LEAVE / ENTER.
This means you should still be able to have highlighting on mouse over
working fine - assuming you highlight on ENTER.

FWIW, if you add "theme(xp_theme);" as the first line of main() to
test/button.cxx, you should see the attempt at an XP theme being enabled.
This should also be a fairly decent test of the highlight functionality on
your machine; the Button's all have a separate image for highlighting
(which is apparent on my machine, anyway).
If the test/button.cxx example doesn't highlight for you, then I might
have to dig a little deeper, but ATPIT what you've described isn't
unexpected.


Link: http://www.fltk.org/str.php?L2698
Version: 2.0-current

_______________________________________________
fltk-bugs mailing list
fltk-bugs@easysw.com
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to