Dear BetterTouchTool Support Team,
I hope this message finds you well.
I am experiencing an issue with the hover effect on the Floating Menus container in BetterTouchTool. I have a custom JavaScript-based animated menu within a WebView HTML element, and the hover effect from the Floating Menus container is conflicting with the animation. Specifically, when hovering over the buttons in the WebView, the animation does not function correctly because it is being interfered with by the Floating Menus hover effect.
Could you please assist me in disabling or modifying the hover behavior on the Floating Menus container? Any guidance on how to resolve this conflict would be greatly appreciated.
Additionally, I would like to inquire if there is a way to automatically activate the WebView or enable hover functionality within the WebView when interacting with it. Specifically, I need assistance with making sure that the WebView menu gets activated properly on hover, without interference from the Floating Menus container. Any advice or solutions on how to achieve this would be very helpful.
Thank you for your support.
Best regards,
can you post an example of what conflicts? I can’t think of any possible conflicts
Thank you for your response. I have a menu in HTML and JavaScript, and I've noticed that when I click outside the menu or on another application, the animation in the script either bugs out or stops working correctly.
for such menus I‘d really recommend to use the standard buttons/menu items. Webviews can be quite problematic to make interactive if they are not in the „active“ window. Thus when you activate some other window they don‘t receive mouse events anymore.
For the standard items BTT uses various tricks to allow for hover effects etc.
I see but in the classic floating web view I don't have this problem, I think the hover in the container of the floating menu is the reason and generate this problem.
it‘s not the hover that‘s causing this. In the old webview I had some extra hacks that can make this work, however they cost quite a bit of CPU. I think I can make this an option for the webview item!
Mhh I just checked the old code - and while there were some hacks that would allow this, they have never been activated. Could you maybe share your old classic floating web view setup that was working?
