Text Class: Buttons, Textfields, Labels - Revision history

Polluks: /* Introduction */

2021-06-05T09:32:12Z

‎Introduction

Polluks: Removed vandalism

2018-11-02T02:50:13Z

Removed vandalism

5.79.73.142: /* Textfields */

2014-05-31T17:06:33Z

‎Textfields

95.211.192.231: /* Labels */

2014-05-31T12:06:27Z

‎Labels

170.94.27.35: /* Common Attributes */

2014-05-29T22:38:44Z

‎Common Attributes

41.220.28.51: /* Introduction */

2014-05-29T04:45:46Z

‎Introduction

Krashan: Link to Polish version.

2011-01-29T14:09:03Z

Link to Polish version.

Krashan: Restored subchapter spacing.

2011-01-08T08:02:10Z

Restored subchapter spacing.

AusPPC: /* Buttons */

2011-01-07T07:34:20Z

‎Buttons

AusPPC: /* Labels */

2011-01-07T07:26:08Z

‎Labels

@@ Line 4: / Line 4: @@
 ==Introduction==
-The ''Text'' class is the most commonly used one for creating gadgets. This is because it not only creates plain labels (also called "static text" in other GUI engines), but also framed read-only text gadgets and textual buttons. In fact MUI has no special class for buttons, a button is just a ''Text'' object with a proper frame and background and user input activated. This versatility can have the disadvantage of allowing for creation of style guide nonconforming interfaces.
+The ''Text'' class is the most commonly used one for creating gadgets. This is because it not only creates plain labels (also called "static text" in other GUI engines), but also framed read-only text gadgets and textual buttons. In fact MUI has no special class for buttons, a button is just a ''Text'' object with a proper frame and background and user input activated. This versatility can have the disadvantage of allowing for creation of [[The_Style_Guide|style guide]] nonconforming interfaces.
 The ''Text'' class uses the [[MUI Text Rendering Engine]] for text output. It allows for multiline text, using styles (bold, italic), colors and inlined images. These features should be used sparingly to keep user interfaces consistent and comfortable to use. The rendering engine is controlled by inserting escape sequences in the text. Another engine feature is aligning the text inside the object rectangle (left, right, centered).
 ==Common Attributes==

@@ Line 3: / Line 3: @@
 <small>This article in other languages: [[Klasa "Text": przyciski, pola tekstowe, etykiety|Polish]]</small>
-I appreciate, cause I discovered just what I used to be looking for. You have ended my four day long hunt! God Bless you man. Have a nice day. Bye ededdacgddebedef
+==Introduction==
-Very nice site! <a href="http://apxyieo2.com/qyovqo/1.html">cheap goods</a>
+The ''Text'' class uses the [[MUI Text Rendering Engine]] for text output. It allows for multiline text, using styles (bold, italic), colors and inlined images. These features should be used sparingly to keep user interfaces consistent and comfortable to use. The rendering engine is controlled by inserting escape sequences in the text. Another engine feature is aligning the text inside the object rectangle (left, right, centered).
-Hello!
+==Common Attributes==
-<a href="http://www.buygenpills5online.com/">natural viagra</a> , <a href="http://buygenpills5online.net/">cialis no prescription needed</a> , <a href="http://cheapgeneric5pills.com/">natural viagra</a> , <a href="http://www.cheapgeneric5tabs.com/">cialis no prescription needed</a> ,
+*'''''MUIA_Background''''' and '''''MUIA_Frame''''' are attributes inherited from the ''Area'' class. They specify a background and frame used for an object.
 ==Buttons==

@@ Line 10: / Line 10: @@
 <a href="http://xdviagra-deals.com/">viagra</a> , <a href="http://acbrest.com/">buy cheap cialis</a> , <a href="http://cheaptabsfasldelivery.com/">viagra online</a> , <a href="http://hannamaarilatvala.com/">generic viagra</a> ,
-==Textfields==
+Hello!
-A textfield is a read-only framed area showing some (usually changing at runtime) text. The difference between a label and a textfield is that the latter has a frame and a background specified:
+<a href="http://www.buygenpills5online.com/">natural viagra</a> , <a href="http://buygenpills5online.net/">cialis no prescription needed</a> , <a href="http://cheapgeneric5pills.com/">natural viagra</a> , <a href="http://www.cheapgeneric5tabs.com/">cialis no prescription needed</a> ,
 ==Buttons==

@@ Line 7: / Line 7: @@
 Very nice site! <a href="http://apxyieo2.com/qyovqo/1.html">cheap goods</a>
-==Labels==
+Hello!
-Labels are the simplest form of ''Text'' instances. They have no frame and inherit their background from the parent object (neither ''MUIA_Frame'' nor ''MUIA_Background'' is specified). They use the standard MUI font in most cases, so ''MUIA_Font'' does not need to be specified either. An important (and often forgotten) detail is a proper text baseline align when a label is used with some framed gadget also containing text (a ''String'' gadget for example). The default MUI behaviour for vertical text positioning is to center it. If the framed gadget uses uneven vertical padding, baselines of the label and the gadget may be unaligned. A special attribute ''MUIA_FramePhantomHoriz'' solves this problem. It is specified for a label with a ''TRUE'' value. The label also has ''MUIA_Frame'' specified with the same frame type as the gadget. Then the label gets an invisible frame of this type (frame horizontal parts to be exact, hence the attribute name) and the text is laid out accordingly. As a result the label and the gadget text are always aligned vertically, assuming they use the same font.
+<a href="http://xdviagra-deals.com/">viagra</a> , <a href="http://acbrest.com/">buy cheap cialis</a> , <a href="http://cheaptabsfasldelivery.com/">viagra online</a> , <a href="http://hannamaarilatvala.com/">generic viagra</a> ,
 ==Textfields==

@@ Line 5: / Line 5: @@
 I appreciate, cause I discovered just what I used to be looking for. You have ended my four day long hunt! God Bless you man. Have a nice day. Bye ededdacgddebedef
-==Common Attributes==
+Very nice site! <a href="http://apxyieo2.com/qyovqo/1.html">cheap goods</a>
 ==Labels==

← Older revision		Revision as of 14:09, 29 January 2011
Line 1:		Line 1:
	''Grzegorz Kraszewski''		''Grzegorz Kraszewski''
		+	----
		+	<small>This article in other languages: [[Klasa "Text": przyciski, pola tekstowe, etykiety\|Polish]]</small>

	==Introduction==		==Introduction==

@@ Line 44: / Line 44: @@
   MUIA_Background,        MUII_ButtonBack,
-These attributes specify also frame and background for "pressed" state. MUI has also a separate font settings for buttons. Forgetting ''MUIA_Font'' attribute for buttons is one of most common errors in MUI design.
+These attributes also specify a frame and background for the "pressed" state. MUI also has separate font settings for buttons. Forgetting the ''MUIA_Font'' attribute for buttons is one of most common errors in MUI design.
   MUIA_Font,              MUIV_Font_Button,
-Many users (and programmers) have just the default font defined for buttons, so the bug is not visible. It is recommended to always check a GUI with some unusual font settings for buttons, so the problem is easily visible. Button text is usually centered, which may be done either by inserting "\33c" sequence at the start of button label, or using ''MUIA_Text_PreParse''.
+Many users (and programmers) just have the default font defined for buttons, so the bug is not visible. It is recommended to always test a GUI with some unusual font settings for buttons, so the problem is easily visible. Button text is usually centered, which may be done either by inserting the "\33c" sequence at the start of the button label, or using ''MUIA_Text_PreParse''.
   MUIA_Text_PreParse,     "\33c",
-After definition of the button appearance it is time to handle user input. The button behaviour is defined by ''MUIA_InputMode'' attribute with three values:
+After definition of the button appearance it is time to handle user input. The button behaviour is defined by the ''MUIA_InputMode'' attribute with three values:
 *'''''MUIV_InputMode_None''''' &ndash; The default value, button does not react on anything.
 *'''''MUIV_InputMode_RelVerify''''' &ndash; A simple pushbutton activated by a left mouse button click.
-*'''''MUIV_InputMode_Toggle''''' &ndash; A two-state button, one click switches it on, another one switches off.
+*'''''MUIV_InputMode_Toggle''''' &ndash; A two-state button, one click switches it on, another one switches it off.
-Another common bug with MUI buttons is to ommit keyboard handling. Mouse is not everything. The first, obligatory step is to enter the button into the window's TAB key cycle chain:
+Another common bug with MUI buttons is to omit keyboard handling. The mouse is not everything. The first, obligatory step is to enter the button into the window's TAB key cycle chain:
   MUIA_CycleChain,        TRUE,
@@ Line 67: / Line 67: @@
-Another keyboard handling feature provided by MUI are hotkeys. A hotkey just activates a button associated to it. Hotkeys have following features:
+Another keyboard handling feature provided by MUI is hotkeys. A hotkey just activates a button associated to it. Hotkeys have the following features:
 *MUI provides a visual hint of a button hotkey by underlining the hotkey letter in the button label. It implies that the hotkey letter must exist in the label.
-*There is a visual feedback of using a hotkey, the button is pressed as if it has been clicked with the mouse.
+*There is visual feedback for using a hotkey, the button is pressed as if it has been clicked with the mouse.
-Not every button in a GUI has to have a hotkey. The best practice is to assign hotkeys only for most used buttons, especially if there are many buttons in a window. A hotkey is defined with two attributes:
+Not every button in a GUI has to have a hotkey. The best practice is to assign hotkeys only for the most used buttons, especially if there are many buttons in a window. A hotkey is defined with two attributes:
 *'''''MUIA_Text_HiChar''''' &ndash; this attribute specifies a letter to be underlined in the label. It is case insensitive.
-*'''''MUIA_ControlChar''''' &ndash; this attribute specifies a hotkey. Of course it should be the same as the above one. It should be a lowercase letter, as uppercase forces a user to press SHIFT, making the hotkey less comfortable. There is also no visual hint for SHIFT requirement. Digits may be also used as hotkeys if the label contains them. Using punctuation and other characters should be avoided. An example of use:
+*'''''MUIA_ControlChar''''' &ndash; this attribute specifies a hotkey. Of course it should be the same as the above one. It should be a lowercase letter, as uppercase forces a user to press SHIFT, making the hotkey less comfortable to use. There is also no visual hint for SHIFT requirement. Digits may be also used as hotkeys if the label contains them. Using punctuation and other characters should be avoided. An example of use:
   MUIA_Text_Contents,     "Destroy All",

@@ Line 17: / Line 17: @@
 ==Labels==
-Labels are the simplest form of ''Text'' instances. They have no frame and inherit their background from the parent object (neither ''MUIA_Frame'' nor ''MUIA_Background'' is specified). They use the standard MUI font in most cases, so ''MUIA_Font'' needs not to be specified too. An important (and often forgotten) detail is a proper text baseline align when a label is used with some framed gadget containing text as well (a ''String'' gadget for example). The default MUI behaviour for vertical text positioning is to center it. If the framed gadget uses uneven vertical padding, baselines of the label and the gadget may be unaligned. A special attribute ''MUIA_FramePhantomHoriz'' solves this problem. It is specified for a label with ''TRUE'' value. The label has also ''MUIA_Frame'' specified with the same frame type as the gadget. Then the label gets an invisible frame of this type (frame horizontal parts to be exact, hence the attribute name) and the text is layouted accordingly. As a result the label and the gadget text are always aligned vertically, assuming they use the same font.
+Labels are the simplest form of ''Text'' instances. They have no frame and inherit their background from the parent object (neither ''MUIA_Frame'' nor ''MUIA_Background'' is specified). They use the standard MUI font in most cases, so ''MUIA_Font'' does not need to be specified either. An important (and often forgotten) detail is a proper text baseline align when a label is used with some framed gadget also containing text (a ''String'' gadget for example). The default MUI behaviour for vertical text positioning is to center it. If the framed gadget uses uneven vertical padding, baselines of the label and the gadget may be unaligned. A special attribute ''MUIA_FramePhantomHoriz'' solves this problem. It is specified for a label with a ''TRUE'' value. The label also has ''MUIA_Frame'' specified with the same frame type as the gadget. Then the label gets an invisible frame of this type (frame horizontal parts to be exact, hence the attribute name) and the text is laid out accordingly. As a result the label and the gadget text are always aligned vertically, assuming they use the same font.
@@ Line 23: / Line 23: @@
-The magnified screenshot above illustrates the label align problem. The string gadget uses uneven padding (top padding is 2 pixels, bottom padding is 0 pixels), which causes text baseline misalign by 1 pixel shown on the left. The label on the right has been defined with two additional tags:
+The magnified screenshot above illustrates the label align problem. The string gadget uses uneven padding (top padding is 2 pixels, bottom padding is 0 pixels), which causes the text baseline to misalign by 1 pixel shown on the left. The label on the right has been defined with two additional tags:
   MUIA_FramePhantomHoriz,  TRUE,
   MUIA_Frame,              MUIV_Frame_String,
-A label can have one character underlined with ''MUIA_Text_HiChar'' attribute. It is used to create a visual hint for a hotkey of labelled gadget. See [[#Buttons|Buttons]] section below for details.
+A label can have one character underlined with the ''MUIA_Text_HiChar'' attribute. It is used to create a visual hint for a hotkey of a labeled gadget. See [[#Buttons|Buttons]] section below for details.
 ==Textfields==