SpoutReceiver.exe /// full screen about spout2

[leadedge]

This was addressed back in 2017 by Tim Thompson, who changed the full screen function to allow for multiple monitors. It required some changes to use (MonitorFromWindow). If it's on a different monitor this function detects it. Default is the primary monitor. I can't see any changes since then that might affect it. Unfortunately I can't test it because I don't have a multiple monitor setup.
Check the version you are using. The changed occurred for Version 2.019. The latest version is 2.024. At that time it worked for him, so it should be same now. It might be possible with Openframeworks or something similar, but again I don't have the means to do anything with it. Perhaps you know somebody who might be able to help.

[nuclearsugar]

Thanks for the info.

I'm using SpoutReciever v2.023, as bundled with the latest Spout_2006_update-3 Install. Unfortunately SpoutReciever will currently only use the main display for full screening. This is confirmed from several different people using multi-monitor setups.

@nosuchtim - Would you be interested and willing to look at the SpoutReciever code again?

[leadedge]

2.024 is at https://github.com/leadedge/Spout2/tree/beta/DEMO. But I am sure it won't make any difference.
If Tim has the time, I am available by email to look at details.

[leadedge]

Try this version - 2.021 -

SpoutReceiver.zip

just after the modifications were made:

[nuclearsugar]

I just tested out SpoutReciever v2.021 and it will only use the main display for full screening. So perhaps something within Windows or a library has changed since then. Alas!

[leadedge]

Here is Version 2.020

SpoutReceiver_2020.zip

That goes back a little more. I can't find 2.019.

Edit : - I found it in backups. Try both of these and that will narrow down the code changes.

SpoutReceiver_2019.zip

[nosuchtim]

The SpoutReceiver.exe in SpoutReceiver_2020.zip seems to work fine with multiple monitors and fullscreen - I just invoked it and was able to fullscreen it on one monitor, then move it to another monitor, and do a fullscreen there (without exiting). I'm not sure I have the current source for SpoutReceiver anymore, and I don't see it in the github repo. I have the email where I sent Lynn the changes for multiple monitor fullscreen, this was the final version of my changes: HMONITOR monitor = MonitorFromWindow(g_hwnd, MONITOR_DEFAULTTOPRIMARY); MONITORINFO mi; mi.cbSize = sizeof(mi); GetMonitorInfo(monitor, &mi); SetWindowPos(g_hwnd, HWND_TOPMOST, mi.rcMonitor.left, mi.rcMonitor.top, mi.rcMonitor.right - mi.rcMonitor.left, mi.rcMonitor.bottom - mi.rcMonitor.top, SWP_SHOWWINDOW); SetMenu(g_hwnd, NULL); ...Tim...

…

On Fri, Jul 3, 2020 at 6:22 PM Lynn Jarvis ***@***.***> wrote: Here is Version 2.020 SpoutReceiver_2020.zip <https://github.com/leadedge/Spout2/files/4871958/SpoutReceiver_2020.zip> That goes back a little more. I can't find 2.019. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABESNWF2OVUF4JSPKP4U7LRZZ767ANCNFSM4OPCJKKA> .

[leadedge]

Thanks very much Tim.
The menu is now removed and the TaskBar put lowest order before the resizing.
Could you try both 2.021 and 2.024?
This should confirm where the problem is.
There is no repo for this, but I can send you a complete project for Visual Studio 2017.

[nosuchtim]

Neither 2.021 or 2.024 work. ...Tim...

…

On Fri, Jul 3, 2020 at 9:52 PM Lynn Jarvis ***@***.***> wrote: Thanks very much Tim. The menu is now removed and the TaskBar put lowest order before the resizing. Could you try both 2.021 and 2.024? This should confirm where the problem is. There is no repo for this, but I can send you a complete project for Visual Studio 2017. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABESNXYEQZDHVGTMV32MKDRZ2YRFANCNFSM4OPCJKKA> .

[nosuchtim]

By that I mean that they run, but the multi-monitor fullscreen behaviour is broken. 2.020 works fine. ...Tim...

…

On Sat, Jul 4, 2020 at 2:20 AM Tim Thompson ***@***.***> wrote: Neither 2.021 or 2.024 work. ...Tim... On Fri, Jul 3, 2020 at 9:52 PM Lynn Jarvis ***@***.***> wrote: > Thanks very much Tim. > The menu is now removed and the TaskBar put lowest order before the > resizing. > Could you try both 2.021 and 2.024? > This should confirm where the problem is. > There is no repo for this, but I can send you a complete project for > Visual Studio 2017. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <#52 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AABESNXYEQZDHVGTMV32MKDRZ2YRFANCNFSM4OPCJKKA> > . >

[leadedge]

Thanks Tim.
The only thing different between 2.020 and 2.021 is -

		GetMonitorInfoA(monitor, &mi);
		int w = (int)(mi.rcMonitor.right - mi.rcMonitor.left); // rcMonitor dimensions are LONG
		int h = (int)(mi.rcMonitor.bottom - mi.rcMonitor.top);
		// Setting topmost causes a grey screen for Windows 10
		// If scaling is set larger than 100% e.g. 125%
		// Also there seems to be a delay in receiving keystrokes even if set to 100%
		// SetWindowPos(g_hwnd, HWND_TOPMOST, 0, 0, w, h, SWP_SHOWWINDOW);
		// This seems to fix it.
		SetWindowPos(g_hwnd, HWND_NOTOPMOST, 0, 0, w, h, SWP_SHOWWINDOW);
		SetWindowPos(g_hwnd, HWND_TOP, 0, 0, w, h, SWP_SHOWWINDOW);

So I removed the NOTOPMOST/TOP and went back to a single TOPMOST. It no longer goes grey for me at this time. Could have been be a driver issue.

SpoutReceiver_2005.zip

If that still doesn't work, I am not sure where to look.

[nosuchtim]

The 2.025 version doesn't work. ...Tim...

…

On Sat, Jul 4, 2020 at 6:43 AM Lynn Jarvis ***@***.***> wrote: Thanks Tim. The only thing different between 2.020 and 2.021 is - GetMonitorInfoA(monitor, &mi); int w = (int)(mi.rcMonitor.right - mi.rcMonitor.left); // rcMonitor dimensions are LONG int h = (int)(mi.rcMonitor.bottom - mi.rcMonitor.top); // Setting topmost causes a grey screen for Windows 10 // If scaling is set larger than 100% e.g. 125% // Also there seems to be a delay in receiving keystrokes even if set to 100% // SetWindowPos(g_hwnd, HWND_TOPMOST, 0, 0, w, h, SWP_SHOWWINDOW); // This seems to fix it. SetWindowPos(g_hwnd, HWND_NOTOPMOST, 0, 0, w, h, SWP_SHOWWINDOW); SetWindowPos(g_hwnd, HWND_TOP, 0, 0, w, h, SWP_SHOWWINDOW); So I removed the NOTOPMOST/TOP and went back to a single TOPMOST. It no longer goes grey for me at this time. Could have been be a driver issue. SpoutReceiver_2005.zip <https://github.com/leadedge/Spout2/files/4872922/SpoutReceiver_2005.zip> If that still doesn't work, I am not sure where to look. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABESNQL33VE4AGXKEJJM4LRZ4WZBANCNFSM4OPCJKKA> .

[nuclearsugar]

I tested each version and SpoutReceiver v2.020 is the only version that will fullscreen to any monitor.

@pom256 - have any experience with this?

[leadedge]

I think I found the problem. While I was trying to solve the grey screen effect, I forgot to include the monitor origin in the moves.

		int x = (int)mi.rcMonitor.left;
		int y = (int)mi.rcMonitor.top;
		int w = (int)(mi.rcMonitor.right - mi.rcMonitor.left);
		int h = (int)(mi.rcMonitor.bottom - mi.rcMonitor.top);
		SetWindowPos(g_hwnd, HWND_NOTOPMOST, x, y, w, h, SWP_SHOWWINDOW);
		SetWindowPos(g_hwnd, HWND_TOP, x, y, w, h, SWP_SHOWWINDOW);

SpoutReceiver_2026.zip

[nuclearsugar]

SpoutReceiver v2.026 fixed the issue! Nicely done.

[pom256]

I always think that the demo receiver was designed for the main monitor only so I didn't try on a second monitor. But many NestDrop user tell me the same as NuclearSugar regards as even if they drag the Window on the second screen, it will go back to the primary in fullscreen mode. So I just tell them that they change the main monitor in Window setup... But it's more a patch for the moment then a real fix.

I confirm that the receiver which came with Spout 2.0.0.6 go back to my main monitor in full screen when I press f on it, and return to my second monitor when I exit the full screen.

I know that the real 'fullscreen' mode in Directx was targeted the main monitor only. But I remember read some comment in spout code that the fullscreen was just replaced by a floating window with the same size than the screen... But this is old stuff and I'm sure that leadedge is already far beyond that...

[leadedge]

OK @nuclearsugar. That's got it working for you.
@pom256 - yes it's not real fullscreen. The window menu and borders are removed and the remainder is resized and put on top. This was always intended as a demo testing program and the code is ancient. There will come a time when it won't work but until then it does the job.
I read that there is more involved with DPI and scaling, but it's going too far for this program. I have enabled "Per Monitor High DPI Aware" in the project settings, so hopefully that will look after it.
@nosuchtim many thanks for your help.