I have added a "Copy To" menu item to the scenes right click context menu below "Copy".
When hovered over it will open a sub-menu where the user can then select the scene collection file the user wants to copy the selected scene to.
If there is a reference to a global source it will open a dialog asking the user if he/she wants to also copy the global sources the references point to.If the user clicks "No" the references are removed from the copied scene.If the global sources already exists in the target scene collection a dialog will open letting the user know but the scene is still copied.
A dialog will open telling the user the export was successful or the scene already exists in the selected scene collection.
I believe this is useful for users that want to copy or move scenes to a different scene collection.
The "Import" button opens a "Open" dialog where a user can open a scene collection file then it lists all Global Sources from the selected scene collection in a dialog.
You can Import multiple global sources by holding shift or Ctrl and clicking on the Global sources you want to import.
With this change scene collections have their own Global Sources but users can import Global Sources from other scene collections.
If you make any changes to a Global sources properties and want the change in another scene collection you will need to remove the global source in the other scene collection and then import it again.
You can't import Global Sources if there is already a Global Source with the same name.
Hopefully this makes it simple and fast for users to import their commonly used Global sources like for
example followers alerts.
This allows better backward compatibility with older versions. This
will keep the current scene collection set to default if the user ever
decides to downgrade OBS versions for whatever reason.
If a scene collection wasn't found at startup, it would create a
'(null)' scene due to a null pointer.
Also, moved scene collections to the scene collections folder rather
than the base folder to prevent conflicts with the older scenes.xconfig
file.
This hopefully resolves some conflicting opinions about how scene
collections should be handled, and removes it from the general settings
panel, where it felt a bit cluttered.
Actually, I would kind of like it if profiles were handled this way too.
This feels a lot cleaner than how profiles are handled in the general
settings. The profiles thing in the general settings definitely feels
clunky.
In the main menu, the scene collections menu now has the following menu
items:
- New
- Duplicate
- Rename
- Remove
- Import
- Export
Duplicate was something I personally added - I felt like it might be a
nice thing to have for the sake of convenience. Import/Export was
requested by dodgepong, and is also definitely nice to have. Due to how
easy new scene collections are to set up it didn't take very long to put
in.
We've decided not to release scene collections. It caused some backward
compatibility issues, as well as some ease-of-use concerns. We just
don't feel comfortable with it so we're just going to go with the
import/export style that will be implemented in OBS2.
Now able to Switch between different Scene collections.
All Scene ".Xconfig" files now stored in the "sceneCollection" folder.
Changed "GetApplicationName()" added "Profile: SceneCollection: " to the beginning of the app name.
Added "Scene Collection" Combo Box in Settings General
Can add/rename/remove new scenes collections in settings general.
Can add/rename/remove new scene collections while streaming.
Can change scenes Collections while streaming.
If a volume control was muted, the hidden 'unmute volume' value was not
saved to the configuration, meaning that if you exit while muted then
restart, it would unmute to 100% each time, causing annoyance for some
users.
The log file menu will now only contain log files that have at least logged
the system stats since too many people uploaded useless logs, unfortunately
This should allow plugins to implement their own version of a log window
without having to worry about providing lightweight-ish and non-blocking
callback functions for OBSApi.
@jp9000
Implement log window
Also made it so that the log window position/size is saved. Defaults to
600x500, centered to the main monitor if no configuration found.
@palana
Log system integration and callback behavior
No new log files will be added to prevent the current log file from
becoming the topmost entry, which would render the "Upload last Log File"
entry useless
