Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core/gtk/opengl: report the cursor position to the apprt #5123

Closed
wants to merge 1 commit into from

Conversation

jcollie
Copy link
Member

@jcollie jcollie commented Jan 15, 2025

Not sure if this is the best/right way to do this. Wasn't sure if the de-duplication should happen in the renderer or the surface thread. Or maybe there's a better way to do this that I missed because I don't know this part of the code very well.

tristan957
tristan957 previously approved these changes Jan 15, 2025
Copy link
Contributor

@mitchellh mitchellh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd do the de-duping within the renderer. The way this is written today will result in a lot of wasted CPU cycles across threads since every single frame would result in a mailbox message and subsequent thread wakeup (which is likely on another core).

I'd also like to pair this with an actual use case, because I'm not convinced an apprt action and evented system is even necessary or correct for this. It's all just potentially very noisy and I'm concerned about power/cpu usage with all of this.

I think your designated use case is to move the URL overlay when the screen cursor is around it, right? Let me think about that...

@jcollie
Copy link
Member Author

jcollie commented Feb 15, 2025

Closing this as there doesn't seem to be much of a need for this at this time.

@jcollie jcollie closed this Feb 15, 2025
@tristan957
Copy link
Member

I still think it would be good to do this so we can show the url overlay on the other side of the terminal if the cursor is in the way

@mitchellh
Copy link
Contributor

I think eventually yes but I wasn't happy enough with this approach to merge this. I want to think more critically about how to surface this information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants