RFR: 8320563: Remove D3D9 code paths in favor of D3D9Ex [v2]
Lukasz Kostyra
lkostyra at openjdk.org
Fri Apr 26 07:51:05 UTC 2024
> JFX minimum requirements guarantee 9Ex availability, so old non-Ex paths are no longer needed.
>
> In multiple parts (ex. Mesh, Graphics, etc.) where the Device is acquired I changed the type to explicitly use `IDirect3DDevice9Ex`. Technically it doesn't matter much (`IDirect3DDevice9Ex` inherits `IDirect3DDevice` - it was leveraged to transparently use the Ex device in the backend) but now we don't have the non-Ex device, so that keeps it a bit more consistent and clear IMO.
>
> Verified by running tests on Windows 11, did not notice any regressions. Unfortunately I have no way to test this on older systems.
Lukasz Kostyra has updated the pull request incrementally with two additional commits since the last revision:
- Cleanup leftover "Ex" suffixes in variable names
- Remove leftover disableD3D9Ex Prism setting
-------------
Changes:
- all: https://git.openjdk.org/jfx/pull/1445/files
- new: https://git.openjdk.org/jfx/pull/1445/files/2dbed83d..4a9605fc
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jfx&pr=1445&range=01
- incr: https://webrevs.openjdk.org/?repo=jfx&pr=1445&range=00-01
Stats: 7 lines in 3 files changed: 0 ins; 3 del; 4 mod
Patch: https://git.openjdk.org/jfx/pull/1445.diff
Fetch: git fetch https://git.openjdk.org/jfx.git pull/1445/head:pull/1445
PR: https://git.openjdk.org/jfx/pull/1445
More information about the openjfx-dev
mailing list