FLTK logo

STR #2698

FLTK matrix user chat room
(using Element browser app)   FLTK gitter user chat room   GitHub FLTK Project   FLTK News RSS Feed  
  FLTK Apps      FLTK Library      Forums      Links     Login 
 Home  |  Articles & FAQs  |  Bugs & Features  |  Documentation  |  Download  |  Screenshots  ]
 

Return to Bugs & Features | Roadmap 2.0 | Post Text | Post File | SVN ⇄ GIT ]

STR #2698

Application:FLTK Library
Status:4 - Pending
Priority:4 - High, e.g. key functionality not working
Scope:2 - Specific to an operating system
Subsystem:Core Library
Summary:ENTER and LEAVE events are always generated by mouse movement
Version:2.0-current
Created By:jsg4z
Assigned To:bgbnbigben
Fix Version:Unassigned
Update Notification:

Receive EMails Don't Receive EMails

Trouble Report Files:

Post File ]

No files


Trouble Report Comments:

Post Text ]
Name/Time/Date Text  
 
#1 jsg4z
16:03 Aug 10, 2011
On our RHEL5 linux machines, ENTER and LEAVE events are sent to widgets when ever the mouse moves within them.  This can be seen in the test/subwindow.cxx program by moving the mouse inside the inner window.   This makes highlighting on mouse over impossible to deal with.  
 
#2 bgbnbigben
21:25 Aug 11, 2011
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.
 
 
#3 jsg4z
10:51 Aug 12, 2011
I have a Group containing 5 Widgets and want to show a sixth Widget in the Group when the mouse is within the Group. So I call show() on ENTER and hide() on LEAVE on this Widget.  Since the system is calling MOVE,ENTER,LEAVE,MOVE,ENTER,LEAVE,MOVE,ENTER,LEAVE  instead of ENTER,MOVE,MOVE,MOVE,MOVE,LEAVE as I expected it to, the drawing looks strange.  It kinda flickers.  
     

Return to Bugs & Features | Post Text | Post File ]

 
 

Comments are owned by the poster. All other content is copyright 1998-2024 by Bill Spitzak and others. This project is hosted by The FLTK Team. Please report site problems to 'erco@seriss.com'.