FIXED: showCustomOnly - page header disappears [TD 2021.12380]

[tekt]

When using showCustomOnly, the parameter page header is no longer visible.
In previous versions (such as 2021.10330), the page tabs for custom pages would still be visible.
Is there some other new setting to control that, or is it a bug?

[ben]

Can’t reproduce this here, Custom Tabs are showing up in Parameter COMP. Can you show your settings or a file? What are you referring to with showCustomOnly?

[tekt]

Steps to reproduce:

• Create a Base COMP
• Open Customize Component
• Add a parameter page “Page 1”
• Add a parameter “Foo” in that page
• Add another page “Page 2”
• Add a parameter “Bar” in that page
• Create a text DAT with this script: op('base1').showCustomOnly=True
• Right click and run the script
• Select the base COMP

page page bug.toe (3.4 KB)

Looks like the Parameter COMP will show them correctly, but not the network editor.

[ben]

Ok thanks, can reproduce now.

[tekt]

Possibly related:
The behavior of the pageindex parameter seems to be handled inconsistently between the network editor parameter dialog and the parameter COMP if the “Built-In” toggle on the parameter COMP is switched off.
If you have a parameter COMP that has that setting switched off, and use it to select the second custom page, pageindex gets set to 1. But if you have “Built-In” switched on and select the second custom page, it will set pageindex to len(o.pages) + 1.

[ben]

@tekt We just retested this issue in the latest official 2021.16410 and it is no longer reproducible. Do you still have this problem on your end?

We still have to address the ‘possibly related’ one.

[rob]

@tekt

Possibly related:
The behavior of the pageindex parameter seems to be handled inconsistently between the network editor parameter dialog and the parameter COMP if the “Built-In” toggle on the parameter COMP is switched off.
If you have a parameter COMP that has that setting switched off, and use it to select the second custom page, pageindex gets set to 1. But if you have “Built-In” switched on and select the second custom page, it will set pageindex to len(o.pages) + 1 .

So in both cases pageindex will equal 1 whenever the second visible page is selected, whether that page is custom or built-in.

Are you instead expecting pageindex to be based on the full list of available pages so that it’s always constant?
For example hitting the first page could result in a value of 5?

Thanks for the clarification,
Rob.

[tekt]

I haven’t been able to reproduce this myself recently, but I’ve gotten bug reports about it from one or two RayTK users. I’ll try to get some details from them.

[rob]

We have now changed this in our upcoming experimental build, so that pageindex will have the same value regardless of which pages are currently displayed or not.

Similary, we’ve added a new OP member: .currentPage which can be used to get or set the current page, even as a string.

Example: n.currentPage = ‘About’

[tekt]

Awesome. Thanks!
That’ll be easier than scanning through the pages and calculating indices.