You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Valve files should not be included in this project for the following reasons:
This aims to be simple to install on any SDK version. Portability should be a high priority. Copying the file from a specific SDK does not guarantee support with later versions, nor does it help with forward-compatibility with the Source SDK. The more code that we need to maintain from Valve's SDK files, the more work will be needed on our end to support new SDK versions or possibly licensed Source games interested in the project.
There Source SDK's license seems to be unannounced based on my searching. I'm not sure if we can legally provide modified copies their files.
Instead, we should have a routing class in a file of our own that we can have users include with a few short lines in an installation documentation file explaining the rerouting process and any limitations that maybe be imposed from this method.
The text was updated successfully, but these errors were encountered:
The router can't be moved outside of SoundEmitterSystem.cpp because the class CSoundEmitterSystem is defined in the .cpp file itself. This makes it difficult to use this class or a pointer to this class outside of that file. This is necessary for handling the script sounds.
Unless we can redistribute the entire file ourselves, it'll have to be done as part of the installation procedures. There is currently no way as I can see where we'd be able to access CSoundEmitterSystem from outside that file.
Alright. That's a bad design decision on Valve's part that we're going to have to roll with and keep the Valve file in our project. Not sure why they would declare that class in the cpp file!
Valve files should not be included in this project for the following reasons:
Instead, we should have a routing class in a file of our own that we can have users include with a few short lines in an installation documentation file explaining the rerouting process and any limitations that maybe be imposed from this method.
The text was updated successfully, but these errors were encountered: