Skip to content

Only display the overlays for nodes that are in the viewer render path and have their properties panel maximized - #745

Merged
devernay merged 2 commits into
RB-2.4from
overlays-in-viewer-path
Jan 11, 2022
Merged

devernay merged 2 commits into
RB-2.4from
overlays-in-viewer-path

Conversation

@devernay

@devernay devernay commented Jan 8, 2022

Copy link
Copy Markdown
Member

…h and have their properties panel maximized

fixes #744

…h and have their properties panel maximized

fixes #744

@YakoYakoYokuYoku YakoYakoYokuYoku left a comment •

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future I'd like to see previews for newer features/fixes if it's possible and relevant. Also the button groups for minimized nodes not in any of the render paths are still shown in the viewer panel.

Aside from that this LGTM.

@devernay

Copy link
Copy Markdown
Member Author

Screenshots added to #744

@devernay
devernay merged commit 264d212 into RB-2.4 Jan 11, 2022
devernay added a commit that referenced this pull request Jan 11, 2022
- addresses issue commented in #745 (review)
- when panel maximized, buttons are displayed even if viewer is not in render path (see #744 for an explanation of that feature). This is not 100% satisfcatory, but better than before IMHO
- minimized() and maximized() were originally two separate signals (in NodeSettingsPanel), so I kept it that way, but we could have simpler definitions of NodeGui::onSettingsPanelMinimized() and NodeGui::onSettingsPanelMaximized() that simply call NodeGui::onSettingsPanelClosed(true) or NodeGui::onSettingsPanelClosed(false).
devernay added a commit that referenced this pull request Jan 11, 2022
…748)

- addresses issue commented in [#745 (review)](#745 (review))
- when panel is maximized, buttons are displayed even if viewer is not in render path (see #744 for an explanation of that feature). This is not 100% satisfactory, but better than before IMHO
- do not show the viewer buttons if a node is selected in the nodegraph but has its properties panel minimized
- maximize properties panel when double-clicking a node in the nodegraph
- minimized() and maximized() were originally two separate signals (in NodeSettingsPanel), so I kept it that way, but we could have simpler definitions of NodeGui::onSettingsPanelMinimized() and NodeGui::onSettingsPanelMaximized() that simply call NodeGui::onSettingsPanelClosed(true) or NodeGui::onSettingsPanelClosed(false).
@YakoYakoYokuYoku
YakoYakoYokuYoku deleted the overlays-in-viewer-path branch June 18, 2022 19:05
Niik-l pushed a commit to Niik-l/Natron that referenced this pull request Apr 8, 2026
…h and have their properties panel maximized (NatronGitHub#745)

* Only display the overlays for nodes that are in the viewer render path and have their properties panel maximized

fixes NatronGitHub#744

* make NatronGitHub#744 switchable in preferences
Niik-l pushed a commit to Niik-l/Natron that referenced this pull request Apr 8, 2026
…atronGitHub#748)

- addresses issue commented in [NatronGitHub#745 (review)](NatronGitHub#745 (review))
- when panel is maximized, buttons are displayed even if viewer is not in render path (see NatronGitHub#744 for an explanation of that feature). This is not 100% satisfactory, but better than before IMHO
- do not show the viewer buttons if a node is selected in the nodegraph but has its properties panel minimized
- maximize properties panel when double-clicking a node in the nodegraph
- minimized() and maximized() were originally two separate signals (in NodeSettingsPanel), so I kept it that way, but we could have simpler definitions of NodeGui::onSettingsPanelMinimized() and NodeGui::onSettingsPanelMaximized() that simply call NodeGui::onSettingsPanelClosed(true) or NodeGui::onSettingsPanelClosed(false).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants