Filter for CreateBrowser

It would be nice if CreateBrowser offered the option not only to display waves in general, but also to specify more detailed requirements for the waves (or variables etc.), such as the number of dimensions. (In the Data Browser, some properties can be displayed as Visible Columns, which could be used as filter criteria.)

kris

You are right, CreateBrowser does not currently support filtering by wave properties such as dimension count, data type, or size. It can show or hide object classes (waves, variables, strings) and do name-based selection, but not property-based filtering.

Current options:

  1. Use a WaveSelectorWidget / PopupWaveSelector -based custom panel (procedure code)
  • Pros:
    • Most powerful filtering (dimensions, numeric type, size, custom checks).

      Can be tailored to the exact workflow.

      Reusable once built.

  • Cons:
    • More implementation complexity.

      Higher maintenance burden than a built-in command.

      Can be overkill for simple one-off tasks.

  1. Use CreateBrowser plus naming conventions and selection patterns
  • Pros:
    • No new UI code required.

      Fast to adopt for teams already using structured naming.

      Works with existing CreateBrowser/ModifyBrowser workflow.

  • Cons:
    • Depends on naming discipline rather than true metadata filtering.

      Can miss edge cases or include false matches.

    • Harder to scale when many waves share similar names.
  1. Build a lightweight custom chooser for a specific task
  • Pros:
    • Simpler than a full WaveSelectorWidget / PopupWaveSelector integration.

      Very focused user experience.

    • Good middle ground between flexibility and effort.
  • Cons:
    • Usually less general and less reusable.

      You still need custom code to gather and validate candidates.

    • May need updates as requirements evolve.

If you need help implementing whatever you choose, let us know and we'll work together on it.

Thanks,
Kris