-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8354077: Get rid of offscreenSharingEnabled windows flag #24534
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
Conversation
|
👋 Welcome back serb! A progress list of the required criteria for merging this PR into |
|
@mrserb This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been no new commits pushed to the ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
prrace
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine.
But much worse than these being in the code is that we still document them !
https://docs.oracle.com/en/java/javase/17/troubleshoot/java-2d-pipeline-rendering-and-properties.html#GUID-DEA4F3FC-87F5-4196-A295-30A559982B10
I have it on my to-do list to re-write that entire out of date doc.
|
/integrate |
|
Going to push as commit c7c77eb.
Your commit was automatically rebased without conflicts. |
Another unused obsoleted flag removed (offscreenSharingEnabled) from WindowsFlags. Its last usage was eliminated by JDK-6725214 ("D3D: forward-port the new pipeline from 6u10"), see commit.
Interestingly, the original JDK 6u10 changes marked many options as "Obsoleted" (see System Properties for Java 2D Technology). Some of them later were removed in JDK 9 via JDK-8155682 ("Get rid of legacy Windows Flags for DX").
However, two obsoleted flags remain:
Intended use: To turn off the Java 2D system's use of DirectDraw and Direct3D completely.
Introduced: 1.2
Default value: false
How to use: Setting this flag to true turns off DirectDraw usage, which sometimes helps to get rid of rendering problems on Win32.
Intended use: To turn on hardware-accelerated scaling when the DirectDraw/Direct3D pipeline is in use.
Introduced: 1.2
Default value: false
How to use: Setting this flag to true enables hardware-accelerated scaling if the DirectDraw/Direct3D pipeline is in use. DirectDraw/Direct3D hardware scaling is disabled by default to avoid rendering artifacts in existing applications. These rendering artifacts are caused by possible inconsistencies between the scale method that the software scaling operation uses (nearest neighbor) and the different scale methods that video cards use. Certain events that occur while an application is running might cause a scaled image to be rendered partially with hardware scaling operations and partially with software scaling operations, resulting in an inconsistent appearance. For now, you can enable acceleration by setting the ddscale flag to true.
Should we:
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24534/head:pull/24534$ git checkout pull/24534Update a local copy of the PR:
$ git checkout pull/24534$ git pull https://git.openjdk.org/jdk.git pull/24534/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24534View PR using the GUI difftool:
$ git pr show -t 24534Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24534.diff
Using Webrev
Link to Webrev Comment