Zum Hauptinhalt gehen

Kommentare

2 Kommentare

  • Phil MacIntyre

    Hi Berend,

    Thank you for your question. This is unfortunately a known bug. We have a ticket filed in our backlog and will look to resolve it in a future release. The initially hidden setting on the panel may get applied to its nested children components, but not the panel itself. Knowing that you're encountering this, I'll bump the priority up.

    Have a nice day,

    Phil MacIntyre

    1
  • Phil MacIntyre

    Hi Berend,

    We have completed some work which will be included in our upcoming 5.24 release (tentative mid-June date) which has introduced a new toggle and property in Designer for hiding taskbar buttons:

    If 'Initially Available' is toggle on, your panel/component will appear in the taskbar by default. If it is toggled off, it will be hidden. You can make the component available (i.e., its button will show up) or unavailable with the 'ui.make-available' or 'ui.make-unavailable' commands targeting the component in question. For example, to show/hide the Search panel in our default template, you could create a custom command like so:

    The available/unavailable commands simply refer to the button in the taskbar. The existing ui.activate/deactivate commands can be used to make the buttons appear AND the panels/components open/activate.

    By combining these two sets of commands, you should be able to selectively show/hide the buttons in the taskbar and the corresponding components.

    Please let me know if you have any other questions or concerns,

    Phil

    0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.