Skip to content

fix(display): restore full monitor config when re-enabling internal display#5328

Closed
noahterenzianii wants to merge 32 commits into
basecamp:devfrom
noahterenzianii:fix/display-restore-monitor-config
Closed

fix(display): restore full monitor config when re-enabling internal display#5328
noahterenzianii wants to merge 32 commits into
basecamp:devfrom
noahterenzianii:fix/display-restore-monitor-config

Conversation

@noahterenzianii
Copy link
Copy Markdown

What

When re-enabling the internal display, restore the original resolution,
scale and bit depth instead of falling back to preferred/auto defaults.

Why

The previous preferred,auto,auto reset scale and bit depth on every toggle,
causing the display to come back with wrong settings.

How

Read availableModes[0] and currentFormat from hyprctl to rebuild
the full monitor config string before re-enabling.

Test

  1. Connect external monitor
  2. Run script → internal display off
  3. Run script again → internal display on with correct scale and bit depth

dhh and others added 2 commits April 16, 2026 16:12
…isplay

Previously used preferred/auto which ignored scale and bit depth.
Now reads availableModes and currentFormat from hyprctl to rebuild
the correct config string.
Copilot AI review requested due to automatic review settings April 16, 2026 18:51
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@noahterenzianii noahterenzianii changed the base branch from dev to master April 16, 2026 21:04
@noahterenzianii noahterenzianii changed the base branch from master to dev April 16, 2026 21:09
@dhh
Copy link
Copy Markdown
Member

dhh commented Apr 22, 2026

No longer needed since dev moved to a permanent config file being added/removed.

@dhh dhh closed this Apr 22, 2026
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