PopMenu documentation and bugs

Hi. I’m starting to explore UI’s and reading about built-in options. I was following this guide on PopMenu and had some issues, it seems like some of the code may have changed since it was written, and maybe some bugs in the component.

In example 2, this codeblock should read “onOffToOn”

def offToOn(panelValue):
	op('popMenu').Open(callback=onMenuChoice)
	return

The Null DAT at the end seems to select one element lower in the menu than selected:

After creating the Table DAT as directed and wiring it up, there’s this persistent error in the lister element inside, that won’t go away:

If I change the Input Table option to Include All Rows, Column 0 is Items first, before wiring, the error doesn’t appear, but if it’s set to another option, the error appears and won’t go away even after changing the option.

Hi @michaeljohnson.tv,

thank you for reporting this, the wiki is amended and the bug logged for us to look at.

cheers
Markus

1 Like

Thanks for report! This will be fixed in next release

1 Like

Ah, sorry I just missed the window for today’s release. Fix will be in the NEXT release. If you need a workaround for this stuff, I can help you develop one.

For what it’s worth, almost all uses of pop menu are done from script, not using wiring. This is why the bug you reported has been unnoticed for so long!

no worries, I’m just exploring and not actively developing anything yet… so I can wait for the next release :slight_smile: and thanks for the tip on using scripting.