…I had a look at stdswitcher1, and let me describe the behaviour I want to see more clearly
To observe: Download example or DIY
1.Set up a comp, multiple custom pages, each page at least one par to populate the page.
2.Create a par chop linked to the previous comp, looking only at stdswitcher1 and have a popout floating active viewer
-
Change pages in the native (p) parameter window. Notice how the stdwitcher1 value does not change, delete and recreate the par chop, now that it has recooked, notice it’s zero is based on all pages, custom and built it
-
Open a Parameter Comp, link it to the same comp in step one: Page Names ON, Built in OFF, Custom ON
5.Node select any other operator than comp in step one, (to simulate perform mode, ie dont populate stdswitcher1 with the page selected on the customcomp, but the Parcomp)
- Open viewer on Parameter Comp, change pages from there:
Notice how the stdwitcher1 value does not change, delete and recreate the par chop, notice how now it’s zero is based on custom pages only
So if you are using the Par COMP in a Perform UI, and then go into the network your par chops stdswtich will have different value behaviour based on what nodes pars you are looking at. This could lead to confusing or worse situations where things act different in perform vs network.
In conclusion the RFE for two new seperate values stands, something like stdswitch1 and custswitch1. Or they could be new names in an entirely new location; And if you could pimp out the new numbers to selectively cook only when changing pages that would be great too!
Examplestdswitcher.tox (1.29 KB)
…I hadn’t thought about a custom parameter that displays TOP data, I was thinking little interactive widgets and informative text, whom’s containers were toggled on or off based on what page was active… but now that you mention it…Along that train of thought: give all custom parameters a new toggle, similar to the read only. The new toggle would be parviewer, another read-only mode that displays a selected-from-anywhere parameter of matching type (sting or value or RGB),( not OP or Menu or Toggle Or Pulse, those seem unnecessary. )