-
-
Notifications
You must be signed in to change notification settings - Fork 842
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update SpoutLibrary #3450
Update SpoutLibrary #3450
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
How do I use / test Spout in Stellarium? |
Please read Stellarium User Guide |
Are there any functional changes in Spout2 since 2016? Or is "running on Win64/ARM" the only change? |
I'll need help from @leadedge to answer this. |
There have been many changes since 2016 but fundamentally it works in the same way. The SpoutLibrary example shows more recent functions but the existing methods can still be used. SpoutSettings should be run initially to set registry keys. |
@leadedge SpoutSettings was only required for SpoutPanel. But fi SpoutPanel is not used then running SpoutSettings once is not required, correct? At least during my testing I did not need running SpoutSetting for receivers to recognize senders. |
27434c2
to
6e159a6
Compare
@hmartinez82 - You are right that a receiver will work without any sender selection because it will detect the sender currently active. If SpoutSettings, or SpoutPanel itself, is run just once, the path to SpoutPanel is recorded in the registry so that receivers can read the path to open it. SpoutSettings sets up several other registry keys in "Computer\HKEY_CURRENT_USER\SOFTWARE\Leading Edge\Spout". If they are not set, defaults are used by senders and receivers. This will be OK for Stellarium on an Arm machine. If Stellarium is updated for an x86 machine, and a user has previously opened an older settings program (then called SpoutDXmode), keys for "DirectX9" and "Memoryshare" may be set . If there are problems, the user can run SpoutSettings which will erase these old keys and has diagnostics that are useful to trace the cause. |
Looks like we should add some enhancements of description / notifications into Stellarium User Guide for Spout2. |
@alex-w - I had a quick look at the user guide. The link to the Spout home page will lead to a download and it contains basic readme files. The SpoutSettings program itself has multiple help buttons. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does not break Win64 build, OK for me.
Hello @hmartinez82! Please check the fresh version (development snapshot) of Stellarium: |
Hello @hmartinez82! Please check the latest stable version of Stellarium: |
Description
Spout2 was very old. The version was from 2016! For the Windows on ARM support a newer version of Spout2 is required.
This adds a new optional CMake parameter to tell the configuration that it's building for ARM64. Unfortunately, the MSVC toolset does not set CMake's x-compiling variables for us to detect so this new optional parameter is required. If you imagine some other way, more automatic, to detect x-compilation I'm all ears :)
Type of change
How Has This Been Tested?
All unit tests pass
Checklist: