Mouse cursor is not visible in Fltk

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Mouse cursor is not visible in Fltk

1,559 Views
foxsquirrel
Contributor II

Mouse cursor is visible in weston however when a trivial test using screen and button in Fltk is opened the mouse cursor disappears when it moves into the Fltk screen. Callback works fine with touchscreen and if I can find the button and click with the mouse the callback works.

Installed the Fltk 1.4 as was suggested on their site and that did not resolve the issue.

I have ran out of options of places to look for clues on how to make the cursor visible when in the Fltk screen.This might be some system setting that I am not aware of.

 

Tags (3)
0 Kudos
Reply
3 Replies

1,299 Views
BrianCharlis
Contributor I

Ensure that Fltk's cursor settings are configured correctly to display the cursor when in its screen. Check Fltk's documentation or settings for options related to cursor visibility. It's possible Fltk is overriding system defaults. Ensure your system settings allow cursor visibility across applications. If issues persist, consult Fltk's community or support for specific troubleshooting steps related to cursor visibility.

Best Wishes dollar tree.pro
0 Kudos
Reply

1,405 Views
Cassiebratt
Contributor I

Hello @foxsquirrelmarykayintouch,

The invisible mouse cursor issue in your Fltk application running on Weston can be frustrating. Here are some potential causes and solutions to explore:

1. Fltk Cursor Handling:

By default, Fltk might not explicitly manage the mouse cursor visibility. You might need to enable cursor visibility within your Fltk application.
Solution:

Check the Fltk documentation or search online forums for methods related to managing the mouse cursor. There might be functions like Fl_Cursor(FL_CURSOR_DEFAULT) or similar to set the cursor visibility.
2. Conflicting Window Manager Settings:

Weston might have specific settings related to cursor behavior within applications.
Solution:

Investigate Weston's configuration options. Look for settings that control the mouse cursor behavior within applications or window management. You might find an option to force cursor visibility for all applications.
3. Graphics Driver Issue:

In rare cases, the issue might be related to a bug in the graphics driver for your system.
Solution:

Update your graphics driver to the latest version. Check your system's documentation or manufacturer's website for instructions on updating drivers.
4. Debugging with Print Statements:

If none of the above solutions work, consider adding print statements to your Fltk code to track the cursor behavior.
Solution:

Add print statements within your Fltk event handlers (e.g., when() callbacks) for mouse events like FL_PUSH or FL_MOTION. This can help you see if the events are being triggered despite the cursor being invisible.

Search Online Forums: Look for similar issues reported on Fltk forums or communities.

Minimal Reproducible Example: Create a minimal Fltk application that only uses a screen and button to reproduce the issue. This can help isolate the problem and share it for easier troubleshooting.

Fltk Version Compatibility: Double-check if your Fltk version (1.4) is compatible with your Weston version. Sometimes, outdated versions might have bugs or limitations.

By systematically exploring these possibilities and potentially providing more details about your system and Fltk code structure if needed, you should be able to identify the cause of the invisible cursor issue and get it working correctly in your Fltk application.

I hope the solution may help you. 

Best regards,
Dennis Leon

 

 

0 Kudos
Reply

1,310 Views
foxsquirrel
Contributor II

Hi Dennis,

 

Thank you for responding, we dropped that project a few months back because of that issue. I did notice the mouse click is actually tracked, if you can guess about where it is by placing a button close to the edge it works. Just not visible, its seems like the actual cursor is on the wrong layer??.

At this point its just a guess, we are doing a re-visit of that project and hopefully this time it will resolved. Also bumping the kernel upto 6.x and testing again. Either way I wlll follow up with the results.

 

Regards,

Fred

Tags (1)
0 Kudos
Reply