FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Remove the need for “Disable HiDPI Scaling” on Windows · Issue #342 · processing/processing4 · GitHub

Repository navigation

Remove the need for “Disable HiDPI Scaling” on Windows #342

Closed

Description

Created by: benfry

As a temporary resolution for #226, 4.0 beta 3 includes an option in Preferences (on Windows) to disable HiDPI scaling. This makes the UI behave properly, but is a temporary workaround because it leaves things fuzzy and still requires users to find the option.

Unfortunately, detecting when it's necessary to select this option is extremely difficult, and it appears, cannot be done consistently. If this sticks around much longer, maybe we can add a dialog box that suggests using the option.

See also #231.

Activity

  1. processing-bot commented on Jan 16, 2022

    CollaboratorAuthor

    Created by: benfry

    Based on further comments in #226, this seems to come down to the editor cursor position offset to the right with fractional Windows scaling. It's not a low- or high-res issue specifically, it's just that the metrics are a little funky when not using an even multiple like 200%.

    Luckily, that's easier to detect, though JEditSyntax sure is killing us here. (But can't do a jump to RSyntaxArea without breaking all Modes from 3.x…)

    It's also an issue with our custom components (EditorHeader and EditorFooter) which are stretched and pixelated when using strange fractions.

  2. processing-bot commented on Jan 20, 2022

    CollaboratorAuthor

    Created by: benfry

    With the last three commits, I think we have the Windows scaling issue resolved for 4.0 beta 4.

  3. processing-bot commented on Jan 29, 2022

    CollaboratorAuthor

    Created by: benfry

    More fixes for this coming in beta 5 if anyone runs into trouble…

  4. processing-bot commented on Mar 1, 2022

    CollaboratorAuthor

    Created by: github-actions[bot]

    This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.

  5. locked as resolved and limited conversation to collaborators on Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL