As far as I can tell, there is nothing unusual this file association that would cause this behavior. I also tried removing the "Command" value shown in the second image from the registry, which had no impact.
See the following screenshots (associated file type is. I have inspected the relevant registry entries for the file association and nothing seems out of the ordinary. NET, which corresponds to the user's system display settings. The code requests the primary monitor from. NET application written using the WPF framework that targets. I'm not sure if it matters, but this is a. After that, opening the same associated file again results in the same behavior described in methods 1-3, once again depending on how the file is opened. Then after about 5 minutes, the application opens on the correct display and behaves normally. Nothing at all appears to happen at first. Browse to the installed application and select it: Right-click associated file in File Explorer and choose "Open With.". Launch the application from a command prompt by running name_of_application.exe "file_to_open": Portions of the UI are also missing when trying to interact with the application.ĭrag and drop an associated file onto the application exe in File Explorer:Īpplication opens on the correct display and behaves normally. Here are the methods of launching I have tried and the resulting behavior:ĭouble-click an associated file in File Explorer:Īpplication launches, but the UI opens on whichever monitor File Explorer is on rather than on the primary display, as it has been written to do. Each method involves opening a file that has been associated to the application. My expectation is that it should behave identically for each method of launching. I have a custom-built Windows desktop application that unexpectedly behaves differently on a system with multiple monitors, depending on how it has been launched.
0 kommentar(er)
