Parameter pagination left dropdown acting weirdly

[ustk]

@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?

[Christoph Hart]

@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.

[ustk]

@Christoph-Hart Oktoberfest is coming...

[ustk]

@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

[ustk]

@Christoph-Hart Oh and more, 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...

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:

[Christoph Hart]

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

[ustk]

@Christoph-Hart PMing you my network... (note that it's a 6 channels)
From the left Node List, try to connect FX->Alg_0, Alg_1 or Alg_2 to the math.mul node I placed at the top of the network. You'll see the connections will be made from parameters in page Set2ToAlgo

I have the vague impression the issue comes from the order they have in the XML. In there, these 3 parameters are placed between the ' Set2ToAlgoand FILTER` pages (might be me when manually editing the xml, or changing the page name afterward, I can't be sure...)

[ustk]

@Christoph-Hart Confirmed. Re-organising the parameters per pages in the XML resolved the issue

[ustk]

@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 parameters

In this case, ENV:

[Christoph Hart]

@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).

[ustk]

@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...