Reply to thread

Message

Thanks for the report. I'm not really up to speed on how the results of QueryDisplayConfig should be interpreted, do you have some experience with it? We currently get the index of the screen that MP2 is being displayed on by checking for the index of the screen in System.Windows.Forms.AllScreens, do you know if that will be the same index in the pathArray returned in QueryDisplayConfig? If so, is it then just a case of reading the correct modeInfoIdx from the source and target info contained in the path info at that index?

Edit: looks like the indices in the System.Windows.Forms.AllScreens array and pathArray are not necessarily comparable (and that AllScreens is not necessarily in any particular order in general) so I need to find a way of linking them, possibly with a call to DisplayConfigGetDeviceInfo

<blockquote data-quote="Brownard" data-source="post: 1284764" data-attributes="member: 48291">Thanks for the report. I'm not really up to speed on how the results of QueryDisplayConfig should be interpreted, do you have some experience with it? We currently get the index of the screen that MP2 is being displayed on by checking for the index of the screen in <a href="https://github.com/MediaPortal/MediaPortal-2/blob/WIP_2.4/MediaPortal/Source/UI/Players/RefreshRateChanger/VideoFpsWatcher.cs#L56" target="_blank">System.Windows.Forms.AllScreens</a>, do you know if that will be the same index in the pathArray returned in QueryDisplayConfig? If so, is it then just a case of reading the correct modeInfoIdx from the source and target info contained in the path info at that index?Edit: looks like the indices in the <a href="https://github.com/MediaPortal/MediaPortal-2/blob/WIP_2.4/MediaPortal/Source/UI/Players/RefreshRateChanger/VideoFpsWatcher.cs#L56" target="_blank">System.Windows.Forms.AllScreens</a> array and pathArray are not necessarily comparable (and that AllScreens is not necessarily in any particular order in general) so I need to find a way of linking them, possibly with a call to <a href="https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-displayconfiggetdeviceinfo" target="_blank">DisplayConfigGetDeviceInfo</a></blockquote>

[QUOTE="Brownard, post: 1284764, member: 48291"] Thanks for the report. I'm not really up to speed on how the results of QueryDisplayConfig should be interpreted, do you have some experience with it? We currently get the index of the screen that MP2 is being displayed on by checking for the index of the screen in [URL='https://github.com/MediaPortal/MediaPortal-2/blob/WIP_2.4/MediaPortal/Source/UI/Players/RefreshRateChanger/VideoFpsWatcher.cs#L56']System.Windows.Forms.AllScreens[/URL], do you know if that will be the same index in the pathArray returned in QueryDisplayConfig? If so, is it then just a case of reading the correct modeInfoIdx from the source and target info contained in the path info at that index? Edit: looks like the indices in the [URL='https://github.com/MediaPortal/MediaPortal-2/blob/WIP_2.4/MediaPortal/Source/UI/Players/RefreshRateChanger/VideoFpsWatcher.cs#L56']System.Windows.Forms.AllScreens[/URL] array and pathArray are not necessarily comparable (and that AllScreens is not necessarily in any particular order in general) so I need to find a way of linking them, possibly with a call to [URL='https://docs.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-displayconfiggetdeviceinfo']DisplayConfigGetDeviceInfo[/URL] [/QUOTE]