Unhandled Exception about displaymagician

[terrymacdonald]

Huh. This one is weird. The error is coming from the WindowsDisplayAPI which is the library that I use for changing the displays within Windows. Not sure what could be causing that, as the exception is showing that it's faulting somewhere.

Could you please generate a TRACE DisplayMagician.log file using the instructions below, and upload it here for me to review? Also please upload your DisplayProfiles_1.0.json and Shortcuts_1.0.json files too (they are in the Profiles and Shortcuts subdirectories near to where you will find the DisplayMagician.log file.

NOTE: The DisplayMagician.log file is unfortunately just the default DisplayMagician.log file. If you open it you'll see that it only has 'WARN' entries in it. I need the TRACE entries in it too.

To generate a DisplayMagician.log file with TRACE entries in it, please do the following:

• Press WindowsKey + R to bring up a Run prompt
• Click the Browse button
• Navigate to C:\Program Files\DisplayMagician\DisplayMagician.exe, and click the Open button
• Go to the end of the command, and add a space, and then add --trace on the end.
• The whole command should read "C:\Program Files\DisplayMagician\DisplayMagician.exe" --trace
• Press the Run button.

This will force DisplayMagician to start logging TRACE commands until DisplayMagician is closed down.

Now. perform the actions that don't work. In your case, please open up the Display Profile window, and then close it down, and then open up the Shortcut Library and then edit a Shortcut (but don't change anything). Then close down DisplayMagician.

Then straight away please zip up the DisplayMagician.log file and upload it here with the DisplayProfiles_1.0.json and Shortcuts_1.0.json files. Please make sure that it has TRACE commands in the log file, because then we know that the --trace option worked properly.

Once I have the DisplayMagician.log file with TRACE commands in it I'll be able to see if there is anything wrong.

[terrymacdonald]

@gitagogaming I've researched this as much as I can, and I've decided I won't fix this particular issue. The reason is that all the display manipulation code is changing as part of the improvements being made to the next release, DisplayMagician v2.0.0. This will record as much information as possible about a display layout, and will have completely new NVIDIA support as well.

As all of the code will be replaced anyway, it's not worth me fixing this at this moment. I will instead spend the time developing v2.0.0 which should make this issue go away.

Thanks
Terry

[gitagogaming]

@gitagogaming I've researched this as much as I can, and I've decided I won't fix this particular issue. The reason is that all the display manipulation code is changing as part of the improvements being made to the next release, DisplayMagician v2.0.0. This will record as much information as possible about a display layout, and will have completely new NVIDIA support as well.

As all of the code will be replaced anyway, it's not worth me fixing this at this moment. I will instead spend the time developing v2.0.0 which should make this issue go away.

Thanks
Terry

Alright, sounds good.. i appreciate you taking the time and looking into it... and sorry for not getting back to ye sooner with this.. I didn't take notice until today.

technically it does work just fine it just throws that error every so often.. I believe this is why it takes roughly a minute for it to complete its transformation.

[terrymacdonald]

Hi @gitogaming, I've managed to get the windows only (no NVIDIA) screen change down to 3.5 seconds, so it will be interesting to see how quick I can get the NVIDIA change down to. I'm working on AMD next though, and then NVIDIA after that. Please keep an eye out for the v2.0.0 update. The upgrade will be manual as v2.0.0 will require everyone to recreate their display profiles. I don't want to I think I'll create a v1.1.5 just to announce that there is a V2.0.0 when it's ready, as not everyone visits the website. But that's a later problem 😁. Thanks Terry

…

On Mon, 12 Jul 2021, 04:08 gitagogaming, ***@***.***> wrote: @gitagogaming <https://github.com/gitagogaming> I've researched this as much as I can, and I've decided I won't fix this particular issue. The reason is that all the display manipulation code is changing as part of the improvements being made to the next release, DisplayMagician v2.0.0. This will record as much information as possible about a display layout, and will have completely new NVIDIA support as well. As all of the code will be replaced anyway, it's not worth me fixing this at this moment. I will instead spend the time developing v2.0.0 which should make this issue go away. Thanks Terry Alright, sounds good.. i appreciate you taking the time and looking into it... technically it does work just fine it just throws that error every so often.. I believe this is why it takes roughly a minute for it to complete its transformation. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABLU5LHDE6FA7XMDRZO7S4DTXG6XVANCNFSM473HVRKQ> .

[terrymacdonald]

Great news! DisplayMagician v2.0.1 has been released, and it should fix this very issue. Please test it out, and if you still have any issues please log a new issue. You can get DIsplayMagician v2.0.1 from here: https://github.com/terrymacdonald/DisplayMagician/releases/tag/v2.0.1

I'm closing this issue as the fix is in DisplayMagician v2.0.1, and I need to clear out the completed issues so I am able to work on the new issues that come in.

Thanks
Terry