Sancho at 09:15, 6 September 2011

2011-09-06T09:15:21Z

Sancho: Основной текст

2011-09-06T06:24:37Z

Основной текст

New page

<section begin=title /><noinclude>{{DISPLAYTITLE:</noinclude>Properties<noinclude>}}</noinclude><section end=title />{{BreadCrumbL10n}}

{{Documentation/BASICGuideTOC
|ShowPrevNext=block
|ShowPrevPage=block
|PrevPage=EN/documentation/basic_guide/working_with_dialogs
|NextPage=EN/documentation/basic_guide/events
|dial=block
}}

__NOTOC__

== Name and Title ==

Every control element has its own name that can be queried using the following model property:

;<tt>Model.Name (String)</tt>:control element name

You can specify the title that appears in the title bar of a dialog with the following model property:

;<tt>Model.Title (String)</tt>:dialog title (only applies to dialogs)

== Position and Size ==

You can query the size and position of a control element using the following properties of the model object:

;<tt>Model.Height (long)</tt>:height of control element (in ma units)
;<tt>Model.Width (long)</tt>:width of control element (in ma units)
;<tt>Model.PositionX (long)</tt>:X-position of control element, measured from the left inner edge of the dialog (in ma units)
;<tt>Model.PositionY (long)</tt>:Y-position of control element, measured from top inner edge of the dialog (in ma units)

To ensure platform independence for the appearance of dialogs, {{OOo}} uses the '''Map AppFont (ma)''' internal unit to specify the position and size within dialogs. An ma unit is defined as being one eighth of the average height of a character from the system font defined in the operating system and one quarter of its width. By using ma units, {{OOo}} ensures that a dialog looks the same on different systems under different system settings.

If you want to change the size or position of control elements for runtime, determine the total size of the dialog and adjust the values for the control elements to the corresponding part ratios.

{{Documentation/Note|The Map AppFont (ma) replaces the Twips unit to achieve better platform independence.}}

== Focus and Tabulator Sequence ==

You can navigate through the control elements in any dialog by pressing the Tab key. The following properties are available in this context in the control elements model:

;<tt>Model.Enabled (Boolean)</tt>:activates the control element
;<tt>Model.Tabstop (Boolean)</tt>:allows the control element to be reached through the Tab key
;<tt>Model.TabIndex (Long)</tt>:position of control element in the order of activation

Finally, the control element provides a <tt>setFocus</tt> method that ensures that the underlying control element receives the focus:

;<tt>setFocus</tt>:control element receives the focus (only for dialogs)

== Multi-Page Dialogs ==

A dialog in {{OOo}} can have more than one tab page. The <tt>Step</tt> property of a dialog defines the current tab page of the dialog whereas the <tt>Step</tt> property for a control element specifies the tab page where the control element is to be displayed.

The <tt>Step</tt>-value of 0 is a special case. If you set this value to zero in a dialog, all of the control elements are visible regardless of their <tt>Step</tt> value. Similarly, if you set this value to zero for a control element, the element is displayed on all of the tab pages in a dialog.

[[Image:documentation_basicguide_dlg_03.gif|none|thumb|500px|Designing Page 1 of the dialog]]

In the preceding example, you can also assign the <tt>Step</tt> value of 0 to the dividing line as well as the <tt>Cancel</tt>, <tt>Prev</tt>, <tt>Next</tt>, and <tt>Done</tt> buttons to display these elements on all pages. You can also assign the elements to an individual tab page (for example page 1).

The following program code shows how the <tt>Step</tt> value in event handlers of the <tt>Next</tt> and <tt>Prev</tt> buttons can be increased or reduced and changes the status of the buttons.

<source lang="oobas">
Sub cmdNext_Initiated

Dim cmdNext As Object
Dim cmdPrev As Object

cmdPrev = Dlg.getControl("cmdPrev")
cmdNext = Dlg.getControl("cmdNext")
cmdPrev.Model.Enabled = Not cmdPrev.Model.Enabled
cmdNext.Model.Enabled = False
Dlg.Model.Step = Dlg.Model.Step + 1

End Sub

Sub cmdPrev_Initiated

Dim cmdNext As Object
Dim cmdPrev As Object

cmdPrev = Dlg.getControl("cmdPrev")
cmdNext = Dlg.getControl("cmdNext")
cmdPrev.Model.Enabled = False
cmdNext.Model.Enabled = True
Dlg.Model.Step = Dlg.Model.Step - 1

End Sub
</source>

A global <tt>Dlg</tt> variable that references an open dialog must be included to make this example possible. The dialog then changes its appearance as follows:

[[Image:documentation_basicguide_dlg_05.gif|none|thumb|400px|Page 1]]

[[Image:documentation_basicguide_dlg_06.gif|none|thumb|400px|Page 2]]
{{Documentation/Tip|You can find an [[EN/going_further_with_dialog_and_component#Multi-Page_Dialog|other OOoBasic example here]].}}

== Dialogs supporting several languages ==

The strings of a Dialog can be localized, see the Developer's Guide chapter [[EN/documentation/devguide/basic/dialog_localization|Dialog Localization]].

{{PDL1}}

← Older revision		Revision as of 09:15, 6 September 2011
Line 93:		Line 93:

	[[Image:documentation_basicguide_dlg_06.gif\|none\|thumb\|400px\|Page 2]]		[[Image:documentation_basicguide_dlg_06.gif\|none\|thumb\|400px\|Page 2]]
−	{{~~Documentation/~~Tip\|You can find an [[EN/going_further_with_dialog_and_component#Multi-Page_Dialog\|other OOoBasic example here]].}}	+	{{Tip\|You can find an [[EN/going_further_with_dialog_and_component#Multi-Page_Dialog\|other OOoBasic example here]].}}

EN/documentation/basic guide/properties - Revision history

Sancho at 09:15, 6 September 2011

Sancho: Основной текст