Skip to content
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

连接Windows Server 2019时,开始正常,过会会恢复到默认的分辨率 #4

Open
youxiaohou opened this issue Oct 13, 2023 · 3 comments
Labels
Issue Identified source of the problem has been pinpointed

Comments

@youxiaohou
Copy link

连接Windows Server 2019时,设置屏幕2为主屏幕,过一分钟左右又变成了屏幕1,屏幕2又不见了

@nomi-san
Copy link

This relates the bug in my original demo.cc, also this EasyVD is closed program and never know how it is implemented.

@KtzeAbyss
Copy link
Owner

This relates the bug in my original demo.cc, also this EasyVD is closed program and never know how it is implemented.

The EVD program is quite straightforward, primarily composed of your demo.cc and a tray management program I wrote. It's clear that the core functionality code directly comes from your demo.cc, and I haven’t made many modifications (admittedly, and rather shamefully, the primary reason for not altering it is my lack of knowledge in this area). For ease of maintenance, I crafted a separate tray management program to manage your demo.cc, as well as handle some driver and process monitoring operations. When time permits, I'll organize and release the complete source code for the new demo.cc and my tray management program, making it accessible for anyone to refer to or modify.

@KtzeAbyss KtzeAbyss added the Issue Identified source of the problem has been pinpointed label Oct 13, 2023
@nomi-san
Copy link

Confirmed, this issue occurred on some versions of Windows.
The behavior is that the VDD would die even though the update loop was still alive.

Btw, you should support English when users choose this language in the setup.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue Identified source of the problem has been pinpointed
Projects
None yet
Development

No branches or pull requests

3 participants