Resolution resets to panel-native after presenting with Powerpoint.app

[vividfog]

I'll say up front that this is not a biggie, but if it happens to others and every time, it's an annoyance that devalues the otherwise major benefits that BD provides. I don't know if this is caused by using BD, or if it's an effect of using it, exposing misbehavior in Powerpoint and/or Monterey.

How to reproduce:

1. Set up your extra monitors with BD just the way you like them: resolutions, positions
2. Present with Powerpoint, with Slides on any monitor and the Presenter View (with notes etc.) on a BD monitor
3. Quit Powerpoint
4. The BD monitor has now been reset to its native panel resolution, even though the dropdown tickmark says it's still in the preferred resolution from step 1
5. Quit BD
6. Restart BD
7. The BD monitor is now set back to the preferred resolution, set in step 1

The expected behavior in step 4 would be "no change", i.e. the resolution set in step 1 would remain, without having to quit and restart BD. Even if Powerpoint fiddles with the resolutions in its dual-screen presentation mode.

Without BD, Powerpoint probably does that too, but once done presenting, the resolutions and windows are back to normal. With BD they are not.

Can you reproduce this? Any idea what might be causing it, and if there's anything that can be done about it?

Workaround: I can set up a BetterTouchTool hotkey to terminate and restart BD after presenting with Powerpoint 🤓

[waydabber]

It's just a PowerPoint bug, it does not handle some mirrored setups well. There should be an option not to fiddle with resolutions at all in PP. Maybe this could be reported as an issue to Microsoft.

[vividfog]

Ok, I'll report it to MS once I get the motivation to create an account to do so. Feel free to close this issue.

[waydabber]

All right. I did try the PowerPoint thing as it came up once. I don't understand why PowerPoint changes the display configuration programmatically even when "Always start Presenter View with 2 displays" is disabled. But even if it is enabled, it should restore the previous configuration or if it can't then it should make the user aware of the fact that the functionality is limited. But I think it just works this way since ages and for most users its fine, so I don't know how easily MS will fix this.

[waydabber]

I'll move this over to discussion. See this previous discussion about this as well #74 .