Licho

Results 13 comments of Licho

It indeed is because the final assembly is missing and AssemblyInformationalVersion and you can add this attribute to your assembly as a workaround.

This would be super useful. For example NVIDIA and AMD drivers use variable to decide when to switch to dedicated video card. ``` extern "C" { __declspec(dllexport) unsigned long NvOptimusEnablement...

> whoops, never mind. It doesn't throw an exception, but it does stop working.... Yeah exception is caught internally.. sorry for bad explanation

I can reproduce on my machine with two screens of different resolutions and vertical taskbars on right and left.sides After exiting fullscreen, windows think that maximized area is a strip...

Reproduced.with alpha centauri GOG game and immersed VR remote access

Sure. Basically it happens after game that uses fullscreen and changes resolution to lower resolution exits. After it exits, primary screen has "maximized window" area in top section - chrome...

This is screenshot of just the primary screen: ![image](https://github.com/valinet/ExplorerPatcher/assets/3185783/1263c87c-4961-48a2-8912-18ef05efc544) (note primary taskbar is on secondary screen)

So two anomalies: 1) maximized area is quite narrow looks basically like a difference between first and second screen vertical size? 2) area is "behind" taskbar, taskbar obscures all windows...

Tested it, it does not happen without EP -> caused by EP

![image](https://github.com/valinet/ExplorerPatcher/assets/3185783/e930ccf0-0c75-4130-88c4-80b30e89f3a9) Nothing odd. It feels like some logic bug.