Feat cam manager#3
Open
Pankovea wants to merge 4 commits into
Open
Conversation
feat: arrange batch views by buttons up and down feat: roll_Cams close event saves its position and size to an INI file. feat: fn compareCamNames to sort camera names alphabetically. feat: resizeFloater function: This private function resizes the Floater based on the height of its rollouts. add: viewData: This structure holds data for batch view settings UI Adjustments Listbox lst_views height increased to 20 for better visibility and usability. Buttons added for moving views up and down in the batch list (btn_up, btn_down), toggling enabled status (btn_togleEnabled). Enhanced UI elements such as labels, buttons, and checkboxes to ensure better user interaction. Miscellaneous Improvements Minor adjustments in event handling functions like on btn_s pressed, etc., to improve functionality based on new data structures and behaviors. This commit significantly improves the organization and interactivity of the Camera Manager tool, making it more user-friendly and better suited for managing multiple camera settings within a scene.
…th the previous active camera
* Some settings have been moved from Batch Render to roll_batch: - Duplicate View - Newt Render - Render - Scene state * Upon changing batch view settings, they are immediately applied. (if the Batch Render window is open, it will close because the data in the window does not automatically change) * You can add a separator (empty batch vew). * When roll_Cams is rolled up, roll_batch unfolds.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
feat: If active view without the camera, it tries to find the view with the previous active camera
feat: Restore scene state for the batch view
feat: arrange batch views by buttons up and down
feat: roll_Cams close event saves its position and size to an INI file.
feat: fn compareCamNames to sort camera names alphabetically.
feat: resizeFloater function: This private function resizes the Floater based on the height of its rollouts.
add: viewData: This structure holds data for batch view settings
UI Adjustments
Listbox lst_views height increased to 20 for better visibility and usability.
Buttons added for moving views up and down in the batch list (btn_up, btn_down), toggling enabled status (btn_togleEnabled).
Enhanced UI elements such as labels, buttons, and checkboxes to ensure better user interaction.
Miscellaneous Improvements
Minor adjustments in event handling functions like on btn_s pressed, etc., to improve functionality based on new data structures and behaviors.
This commit significantly improves the organization and interactivity of the Camera Manager tool, making it more user-friendly and better suited for managing multiple camera settings within a scene.
UPD:
(if the Batch Render window is open, it will close because the data in the window does not automatically change)