Parameter pagination left dropdown acting weirdly
-
@Christoph-Hart The new pagination system is awesome!
Just a little glitch, in the node list on the left, the arrow dropdowns are acting a life of their own...
-
@Christoph-Hart And it seems the name of a group is limited to a certain amount of characters or they refuse to group. Is this intended?
-
@ustk yup go easy on the name length (16 characters).
But yeah the behaviour in the node list is super weird, it's actually how I intended it to be, but coming back to it now feels like I was drunk when implementing it.
-
@Christoph-Hart Oktoberfest is coming...
-
@Christoph-Hart Another weird thing is that when you have pages already, add add a parameter, this one goes in the last page despite it doesn't have a page name yet.
There should be a "no page yet" page at the start -
@Christoph-Hart Oh and more, when connecting a newly added parameter
that has no page set yetto a node, the connection is taken from a parameter of another page...This happens from the left node list, not when dragging from the parameter itself
Pay attention to the names, I am dragging Alg_0_Mix (which should be the third last knob), but the cable comes from elsewhere:
-
There should be a "no page yet" page at the start
No if you add a parameter, it goes to the end of the list, and every parameter is added to the page that was defined by the last parameter that had a non-empty page name.
The pagination is just an "overlay" over the existing parameter layout so I can't change the order of things without breaking stuff.
when connecting a newly added parameter that has no page set yet to a node, the connection is taken from a parameter of another page...
I tried to replicate the issue, but I can't break it here and from just looking at the code I can't spot what could cause this. Can you send me a minimal network that exhibits this behaviour
-
@Christoph-Hart PMing you my network... (note that it's a 6 channels)
From the left Node List, try to connectFX->Alg_0,Alg_1orAlg_2to themath.mulnode I placed at the top of the network. You'll see the connections will be made from parameters in pageSet2ToAlgoI have the vague impression the issue comes from the order they have in the XML. In there, these 3 parameters are placed between the ' Set2ToAlgo
andFILTER` pages (might be me when manually editing the xml, or changing the page name afterward, I can't be sure...) -
@Christoph-Hart Confirmed. Re-organising the parameters per pages in the XML resolved the issue
-
@Christoph-Hart Ok now playing with
SubGroup, if a group is not set to all parameters, the last existing group is displayed for all following parametersIn this case,
ENV:
-
@ustk yes, again a expected behavior, there is currently no clear flag so the parameters retain their subgroup across pages (but I think I can safely clear the subgroup at a page break).
-
@Christoph-Hart Not a big deal, but as soon as you use sub groups, it forces you to do so for all parameters which you might not want...
