Difference between revisions of "Documentation/DevGuide/GUI/Text Field Extensions"
From Apache OpenOffice Wiki
< Documentation | DevGuide
(Initial author Sun Microsystems, Inc.) |
m |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
|NextPage=Documentation/DevGuide/GUI/Formatted Field | |NextPage=Documentation/DevGuide/GUI/Formatted Field | ||
}} | }} | ||
| − | {{DISPLAYTITLE:Text Field Extensions}} | + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/GUI/{{SUBPAGENAME}}}} |
| + | {{DISPLAYTITLE:Text Field Extensions}} | ||
A user can enter any kind of data into a text field. These values are always stored as a string in the <code>Text</code> property. This can cause some problems when you are evaluating the user input. These controls offer specific solutions to this issue: | A user can enter any kind of data into a text field. These values are always stored as a string in the <code>Text</code> property. This can cause some problems when you are evaluating the user input. These controls offer specific solutions to this issue: | ||
| Line 18: | Line 19: | ||
{|border="1" cellpadding=4 style="border-collapse:collapse;" | {|border="1" cellpadding=4 style="border-collapse:collapse;" | ||
|-bgcolor=#EDEDED | |-bgcolor=#EDEDED | ||
| − | !colspan="2"|Common Properties of Extensions of a <code> | + | !colspan="2"|Common Properties of Extensions of a <code>UnoControlEdit</code> (text field) |
|- | |- | ||
|[IDLS:StrictFormat] | |[IDLS:StrictFormat] | ||
| Line 24: | Line 25: | ||
|- | |- | ||
|[IDLS:EnforceFormat] | |[IDLS:EnforceFormat] | ||
| − | |boolean. If set to true,the allowed characters are checked when leaving the focus. | + | |boolean. If set to true, the allowed characters are checked when leaving the focus. |
|- | |- | ||
|[IDLS:Spin] | |[IDLS:Spin] | ||
| Line 31: | Line 32: | ||
{{PDL1}} | {{PDL1}} | ||
| − | [[Category: Graphical User Interfaces]] | + | |
| + | [[Category:Documentation/Developer's Guide/Graphical User Interfaces]] | ||
Latest revision as of 13:13, 22 December 2020
- Common Properties
- Font-specific Properties
- Other Common Properties
- Property Propagation Between Model and Control
- Common Workflow to add Controls
- The Example Listings
- Label Field
- Command Button
- Image Control
- Check Box
- Radio Button
- Scroll Bar
- List Box
- Combo Box
- Progress Bar
- Horizontal/Vertical Line Control
- Group Box
- Text Field
- Text Field Extensions
- Formatted Field
- Numeric Field
- Currency Field
- Date Field
- Time Field
- Pattern Field
- Roadmap Control
- File Control
- File Picker
- Message Box
A user can enter any kind of data into a text field. These values are always stored as a string in the Text property. This can cause some problems when you are evaluating the user input. These controls offer specific solutions to this issue:
- Formatted field.
- Date field.
- Time field.
- Currency field.
- Numeric field.
- Pattern field.
Common Properties of Extensions of a UnoControlEdit (text field)
| |
|---|---|
| [IDLS:StrictFormat] | boolean. If set to true, only the allowed characters as defined by the format of the control are accepted. All other entries typed with the keyboard are ignored. |
| [IDLS:EnforceFormat] | boolean. If set to true, the allowed characters are checked when leaving the focus. |
| [IDLS:Spin] | boolean. The Spin property defines whether the control displays a spin button. |
| Content on this page is licensed under the Public Documentation License (PDL). |
