On Mon Nov 27 00:44:27 2023 +0000, Shmerl wrote:
> Sorry for slight off-topic, but is there a way to test it with current Wine?
> I was trying something like this:
> ```
> DISPLAY='' WAYLAND_DISPLAY='wayland-0' wine notepad.exe
> ```
> But it's not working:
> ```
> 009c:err:winediag:nodrv_CreateWindow Application tried to create a
> window, but no driver could be loaded.
> 009c:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
> 009c:err:systray:initialize_systray Could not create tray window
> 002c:err:winediag:nodrv_CreateWindow Application tried to create a
> window, but no driver could be loaded.
> 002c:err:winediag:nodrv_CreateWindow L"Make sure that your X server is
> running and that $DISPLAY is set correctly."
> ```
> Or it still needs more bits before it can be tested?
you need to modify regedit, for details see here
https://gitlab.winehq.org/wine/wine/-/merge_requests/3909#note_46166
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4456#note_53856
Fixes periodic crashes in PowerPoint 365
--
v7: d2d1: Acquire lock before attempt to draw to device context
d2d1: Add test for singlethreaded draw
d2d1: Add test for multithreaded draw
https://gitlab.winehq.org/wine/wine/-/merge_requests/4452
Sorry for slight off-topic, but is there a way to test it with current Wine?
I was trying something like this:
```
DISPLAY='' WAYLAND_DISPLAY='wayland-0' wine notepad.exe
```
But it's not working:
```
009c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
009c:err:winediag:nodrv_CreateWindow L"The explorer process failed to start."
009c:err:systray:initialize_systray Could not create tray window
002c:err:winediag:nodrv_CreateWindow Application tried to create a window, but no driver could be loaded.
002c:err:winediag:nodrv_CreateWindow L"Make sure that your X server is running and that $DISPLAY is set correctly."
```
Or it still needs more bits before it can be tested?
--
https://gitlab.winehq.org/wine/wine/-/merge_requests/4456#note_53850
Supersedes !482.
Instead of only storing the value that each variable's component has at
the moment of the instruction currently handled by copy-prop, we store
the trace of all the historic values with their timestamps, i.e. the
instruction index on which the value was stored.
This allow us to query the value that the variable's component had at the time of a swizzle's load instead of the swizzle instead, which also preempts copy-prop from getting stuck in an infinite loop, as which the added tests.
--
v4: vkd3d-shader/hlsl: Use values at the time of the swizzle's load in copy-propagation.
vkd3d-shader/hlsl: Record trace of stored values in copy-propagation.
vkd3d-shader/hlsl: Move index_instructions() up.
tests: Test current failure when propagating swizzles.
https://gitlab.winehq.org/wine/vkd3d/-/merge_requests/487