-
Notifications
You must be signed in to change notification settings - Fork 23
Set refresh rate? #29
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
Comments
Solution 2 does not work well. xrander events from that command triggers endless loop in some situations. |
Implemented solution 1 and fixed some other issues as well. Expect PR :) |
jonaz
pushed a commit
to jonaz/grobi
that referenced
this issue
Dec 3, 2020
Also fixed a few other things: - bugs in active mode detection with my display (144hz and 60hz) - Turn off changed displays in a smarter way. Im using usb-c daisychain and had trouble with the current approach. it disabled my screen as soon as the screen went into hibernate because xrandr stopped detecting the display. - some autoformatting of comments and code according to efficient go guidelines - if xrand (ApplyRule) fails, try 3 times with a little more sleep each time. This also solved issues with my daisychained displays. Fixes fd0#29
jonaz
pushed a commit
to jonaz/grobi
that referenced
this issue
Dec 3, 2020
Also fixed a few other things: - bugs in active mode detection with my display (144hz and 60hz) - Turn off changed displays in a smarter way. Im using usb-c daisychain and had trouble with the current approach. it disabled my screen as soon as the screen went into hibernate because xrandr stopped detecting the display. - some autoformatting of comments and code according to efficient go guidelines - if xrand (ApplyRule) fails, try 3 times with a little more sleep each time. This also solved issues with my daisychained displays. Fixes fd0#29
jonaz
pushed a commit
to jonaz/grobi
that referenced
this issue
Dec 3, 2020
Also fixed a few other things: - bugs in active mode detection with my display (144hz and 60hz) - Turn off changed displays in a smarter way. Im using usb-c daisychain and had trouble with the current approach. it disabled my screen as soon as the screen went into hibernate because xrandr stopped detecting the display. - some autoformatting of comments and code according to efficient go guidelines - if xrand (ApplyRule) fails, try 3 times with a little more sleep each time. This also solved issues with my daisychained displays. Fixes fd0#29
fd0
pushed a commit
that referenced
this issue
Feb 27, 2021
Also fixed a few other things: - bugs in active mode detection with my display (144hz and 60hz) - Turn off changed displays in a smarter way. Im using usb-c daisychain and had trouble with the current approach. it disabled my screen as soon as the screen went into hibernate because xrandr stopped detecting the display. - some autoformatting of comments and code according to efficient go guidelines - if xrand (ApplyRule) fails, try 3 times with a little more sleep each time. This also solved issues with my daisychained displays. Fixes #29
jonaz
pushed a commit
to jonaz/grobi
that referenced
this issue
Mar 9, 2021
Also fixed a few other things: - bugs in active mode detection with my display (144hz and 60hz) - Turn off changed displays in a smarter way. Im using usb-c daisychain and had trouble with the current approach. it disabled my screen as soon as the screen went into hibernate because xrandr stopped detecting the display. - some autoformatting of comments and code according to efficient go guidelines - if xrand (ApplyRule) fails, try 3 times with a little more sleep each time. This also solved issues with my daisychained displays. Fixes fd0#29
Could this be added to docs? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now i had to use this hack:
I have 2 suggestions.
1
Implement
DP-2-1@1920x1080@60
and then we just change the SplitN to be 3 and take the last one as --rate.2
Implement environment variables that is sent to execute_after. Then we can add for example GROBI_ROW_1=eDP-1 , GROBI_ROW_1=DP-2-1 , GROBI_ROW_3=DP-2-8
The execute_after could then look like this:
Then we can always customize our xrandr in the execute_after. Which means stuff like i saw discussed in #8 like --pos can also be solved like this.
I can implement ether solution and make a PR!
The text was updated successfully, but these errors were encountered: