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

Not keen on cursor change #3239

Open
Flapper01 opened this issue May 8, 2024 · 11 comments
Open

Not keen on cursor change #3239

Flapper01 opened this issue May 8, 2024 · 11 comments
Labels

Comments

@Flapper01
Copy link

Would it be possible to make it optional to change the cursor to indicate module clickability?
It seems inconsistent whether or not it changes anyway.

@github-actions github-actions bot added the custom label May 8, 2024
@deathtrip
Copy link

I would also like to have an option to disable it.
I think most ( if not all ) users know whether a module is clickable or not.
It should've been made optional, not forced down users' throat by changing the default behavior, with no option to go back.

@ordy
Copy link
Contributor

ordy commented May 9, 2024

The feature was introduced in #3108. Looking at the code, I think that should be possible, would have to introduce a new setting in the config to define if we want static cursors or not, then check for the value before setting the cursor type in AModule

bool AModule::handleMouseEnter(GdkEventCrossing* const& e) {
  if (auto* module = event_box_.get_child(); module != nullptr) {
    module->set_state_flags(Gtk::StateFlags::STATE_FLAG_PRELIGHT);
  }
  
  if (hasUserEvents_) {
    setCursor(Gdk::HAND2);
  }
  return false;
}

@bananaoomarang @haug1
Mentioning you because you worked on this. Does that sound reasonable to you or is there maybe a better approach?

@haug1
Copy link
Contributor

haug1 commented May 9, 2024

Looking at the code, I think that should be possible, would have to introduce a new setting in the config to define if we want static cursors or not, then check for the value before setting the cursor type in AModule

Yeah, it should be easy to hide the cursor effect behind a config flag. And I'm not sure it's necessary to set the cursor on the mouse enter/leave events. I think it can just be configured once in the constructor instead. So that's a welcome change as well, IMO. That will maybe make it work more consistently as well, in reference to OP's comment:

It seems inconsistent whether or not it changes anyway.

@v4u6h4n
Copy link

v4u6h4n commented May 9, 2024

Good to hear that should be possible, kinda makes it look like a webpage lol :-)

@ronasimi
Copy link

I get a horizontally flipped cursor in hyprland/workspaces since this was added in #3108. Personally I think this is an unecessary setting but please make it toggle-able.

haug1 added a commit to haug1/Waybar that referenced this issue May 15, 2024
also, statically configure the cursor type
@haug1
Copy link
Contributor

haug1 commented May 16, 2024

I've opened a PR that hides the cursor change behind a config flag and addresses my previous comment.

@deathtrip
Copy link

Why close the pull request so early without giving the developer time to look at it?
Many pull requests wait longer to get merged.
And we need to get this fixed.

@haug1
Copy link
Contributor

haug1 commented May 26, 2024

Pretty sure it's been seen. There's been activity on the repository. There are PRs in here from 2020. I don't want to have one of those. Also, I just felt I am not invested enough in this to follow up on feedback or merge conflicts if it will happen now or later on.

@haug1
Copy link
Contributor

haug1 commented May 26, 2024

Code is still linked, so if the issue is serious enough, that can help in the future.

@v4u6h4n
Copy link

v4u6h4n commented May 26, 2024

Damn, thats a pity, the hand cursor just makes waybar look so damn janky.

@Flapper01
Copy link
Author

Flapper01 commented May 26, 2024 via email

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

Successfully merging a pull request may close this issue.

6 participants