Kexi/Handbook/Building Simple Databases/Designing Forms/Using the Widgets tab/en: Difference between revisions

From KDE UserBase Wiki
(Updating to match new version of source page)
 
(Updating to match new version of source page)
 
(4 intermediate revisions by the same user not shown)
Line 2: Line 2:
====Using the Widgets tab====
====Using the Widgets tab====


The '''Widgets''' tab in the <menuchoice>Property</menuchoice> pane provides a list of form widgets and their hierarchy. Each widget is presented within the hierarchy beside other widgets being on the same level (the same parent container). Child widgets (inside containers) are presented using indented names.  
The widgets tab {{Icon|action-widgets}} in the '''Properties''' pane provides a tree list of widgets on the form design page and their hierarchy. Each widget is presented within the hierarchy beside other widgets on the same level (in the same parent container). Child widgets (inside containers) are presented using indented names.  


Each widget has displayed its name and type. The type has also an icon displayed - the same as the one displayed on the toolbar used while form designing is performed.  
Each widget has its name and type displayed. The type also shows an icon - the same as displayed on the Widgets toolbar.  


{{Note|
{{<!--}}-->Note|
* Changing the current selection on the list causes appropriate selection on the designed form. This allows for easier widget lookup by name and easier navigation. For example, it is possible to select a widget by name, and then switch to the Properties tab to change the widget's properties.
* Keeping the <keycap>Ctrl</keycap> key pressed while an item on the widgets list is being selected allows to select multiple widgets at a time. Keeping the <keycap>Shift</keycap> key pressed allows to select entire lists of widgets.}}


Giving widgets reasonable names can be useful but is not mandatory. Note that widget's name is a property that is not visible to the user of your form. Users will only see a widget text, provided by '''Text''' property or similar.
* Changing the current selection on the list is synchronised to the selection on the form design page. This allows for easier widget lookup by name and easier navigation. For example, it is possible to select a widget by name, and then switch to the <menuchoice>Properties</menuchoice> tab to change the widget's properties.
 
* Keeping the <keycap>Ctrl</keycap> key pressed while an item on the widgets list is being selected allows to select multiple widgets at a time. Keeping the <keycap>Shift</keycap> key pressed allows to select entire lists of widgets.}}<!--{{-->
 
Giving widgets reasonable names can be useful in complex forms but is not mandatory. Note that a widget's name is a property that is not visible to the user of your form. Users will only see a widget text, provided by '''Text''' property or similar.


{{Prevnext2
{{Prevnext2

Latest revision as of 16:28, 28 August 2015

Other languages:

Using the Widgets tab

The widgets tab in the Properties pane provides a tree list of widgets on the form design page and their hierarchy. Each widget is presented within the hierarchy beside other widgets on the same level (in the same parent container). Child widgets (inside containers) are presented using indented names.

Each widget has its name and type displayed. The type also shows an icon - the same as displayed on the Widgets toolbar.

Note

* Changing the current selection on the list is synchronised to the selection on the form design page. This allows for easier widget lookup by name and easier navigation. For example, it is possible to select a widget by name, and then switch to the Properties tab to change the widget's properties.
  • Keeping the Ctrl key pressed while an item on the widgets list is being selected allows to select multiple widgets at a time. Keeping the Shift key pressed allows to select entire lists of widgets.


Giving widgets reasonable names can be useful in complex forms but is not mandatory. Note that a widget's name is a property that is not visible to the user of your form. Users will only see a widget text, provided by Text property or similar.