Description: B.Marcelly's "Programmation (Open/Libre)Office.." french book mentions two features I fear may be missing in Online/local help .. 1. Simulating tabbed dialog boxes using the Page/Step property of a dialog 2. Localising/Xlating UI messages to end-user (e.g. MsgBox Print..) using hidden controls/dialogs Note: <Access2Base>L10N> module exhibits an alternative to: - current dialogs localisation help page - the above feature #2 that are worth mentioning/documenting Actual Results: documantation issue Expected Results: documentation produced Reproducible: Always User Profile Reset: No Additional Info:
About feature #1 Dialogs do not propose "tabs UX". "Page (step)" property allows to mimic such similarly to a wizard UI that guide the end-user thru a stepped process. Dialogs (Model.Step) and controls all have that "Page(step)" property. Controls can be hidden are shown according to dialogs Step value: o Controls with Step=0 are always shown o When dialog Step=zero all controls are shown o When dialog Step equals n, all controls with step=n and controls with Step=0 are visible.
Some resources beloe that'll assist update help content for feature #1. 0 Dialog Step property: How to combine Labels into Group Box https://forum.openoffice.org/en/forum/viewtopic.php?f=20&t=94681&p=451291&hilit=dialog+step+property#p451291 o css.awt API alternative: How to get Active Tab/Page ID from a python dialog box? https://ask.libreoffice.org/en/question/174189/how-to-get-active-tabpage-id-from-a-python-dialog-box/ + tabs.py file
Created attachment 157320 [details] Tabbed UI dialog example using Python