The Mosaic class WidgetSet::HorizontalValueBar implements a GUI component intended to serve as a Horizontal Value Bar widget. This widget can be used to compose the appearance of other more complex GUI components, in particular to add to them controls intended to display an integer value (e.g. measured value) by using a needle as pointer that moves horizontally along a track. Accordingly, the track areas on the left and on the right of the needle appear as separate horizontal bars. The user can't interact with the widget.

The exact appearance and behavior of the Horizontal Value Bar is determined by a Horizontal Value Bar Config object. This configuration object provides bitmaps, colors and other configuration parameters needed to construct and display the affected Horizontal Value Bar. Embedded Wizard is delivered with a set of prepared Horizontal Value Bar Config objects you can use instantly as they are. However, if desired, you can create your own configuration objects and so customize the Horizontal Value Bar widgets according to your particular design expectations. The following screenshot demonstrates few examples of how Horizontal Value Bars appear in the canvas area of Composer (and accordingly on the screen in your target device):

The following sections are intended to provide you an introduction and useful tips of how to work with and how to customize the Horizontal Value Bars. For the complete reference please see the documentation of the WidgetSet::HorizontalValueBar and WidgetSet::HorizontalValueBarConfig classes.

To add a new Horizontal Value Bar widget just at the design time of a GUI component do following:

As long as the Horizontal Value Bar widget is selected you can inspect and modify its properties conveniently in the Inspector window as demonstrated with the property Bounds in the screenshot below:

Once added, you can freely move the Horizontal Value Bar, or you simply grab one of its corners and resize it in this way. You can control the position and the size of the widget also by directly modifying its property Bounds. If you want the Horizontal Value Bar to appear behind other views you can reorder it explicitly.

The appearance and partially also the behavior of the Horizontal Value Bar widget can be configured according to your particular design expectation. For demonstration purpose and to help you to quickly create new product prototypes, Embedded Wizard contains six ready to use configurations. The configurations are provided in two different designs we named Mono and Lime. In each design there are three different sizes Small, Medium and Large. The following figure demonstrates all available default configurations at once:

To use the desired appearance configuration you have to select it in the property Appearance of the affected Horizontal Value Bar widget as demonstrated in the screenshot below. You can use the integrated Inspector Assistant window to conveniently select the right configuration. If you like the provided default configurations then you can use them as they are:

If you prefer to adapt the appearance of the Horizontal Value Bar by yourself, then you have to create a new Horizontal Value Bar Config object and specify in it all the bitmaps, colors as well as other parameters to customize your individual Horizontal Value Bar. Once your configuration object is available, you can select it in the property Appearance exactly as you select one of the configurations provided per default with Embedded Wizard.

The Horizontal Value Bar widget is intended to display an integer value by using a needle as pointer that moves along a track. The track areas on the left and on the right of the needle appear as separate horizontal bars. The position of the needle and accordingly the ratio between the width of the left and the right track areas is reflected in the widget's property CurrentValue. By evaluating this property you can simply query the value which is actually displayed in the affected value bar. When you modify the property CurrentValue, the value bar will implicitly update the position of its needle as well as the width of the both tracks (Please note, depending on the selected configuration, the value bar may appear without the needle or without the tracks).

The possible value range for the property CurrentValue is determined by the both properties MinValue and MaxValue, whereby the value specified in the property MinValue corresponds to the leftmost position of the needle and the value of the property MaxValue to the rightmost position. Thus, the value of the property CurrentValue lies always between MinValue and MaxValue. The following figure demonstrates the relations between the three properties:

The value MinValue has not to be necessarily less than MaxValue. If your application case it requires, you can initialize MinValue so that it is greater than MaxValue. For example, you can configure MinValue to be 100 and MaxValue to be 0. Then when the value bar's CurrentValue is getting smaller, the needle moves from left to right. However, you should note, that when initializing MinValue and MaxValue with the same value, the possible value range is empty and the widget will not work.

To simplify the development of GUI applications, the Horizontal Value Bar implements a technique permitting you to connect the widgets directly to a data provider. Once connected, the value bar will remain in sync with the value stored actually in this provider. This technique corresponds to the model-view-controller (MVC) programming paradigm, where the Horizontal Value Bar has the function of the view and the associated data provider serves as model. If you associate in your application several Horizontal Value Bars to one and the same data provider value, the underlying mechanisms will ensure, that all affected value bars do update their state automatically.

The connection between the Horizontal Value Bar and the data provider is established by assigning to the Horizontal Value Bar's property Outlet a reference to a property existing within the data provider and storing the interesting value. Since Horizontal Value Bar is intended to deal with integer values, the property suitable to be connected via reference to the value bar has to be declared with int32 as its data type. Accordingly, the value of the referenced property corresponds to the value bar's current value.

Summarized, after assigning a reference to an existing int32 property to the Horizontal Value Bar's own property Outlet, the value bars adapts its own state to automatically correspond to the actual value of the associated property. You don't need to write a single line of code to benefit from this mechanisms. The aspects underlying this technique are explained in the sections Outlet properties and Notifications and Observer.

The following example demonstrates the practical application case with several Horizontal Value Bars connected to a common int32 property serving as data provider. When you download and start the example, you see two value bars, an Image view and an additional slider with it the value can be modified. The value bars and the slider are connected to the Image view's property Opacity. When you drag on the slider, the state of the property changes (the image appears more or less transparent) and the both value bars are updated accordingly:

Unlike other widgets like the Toggle Button, the Horizontal Value Bar has no additional label nor icon, which can serve as decoration to give the user an idea of the function behind this widget. If you want such additional decoration, please use the available views. For example, you can add a Text view and arrange it above or below the value bar, as you prefer. This Text view could serve then as a label.

In particular situations, however, you will want the additional decoration views to be automatically arranged at predetermined positions. For example, you can arrange the views to appear always side by side of the needle, so that when the needle position changes, the views are moved accordingly. The WidgetSet::HorizontalValueBar class provides for such application cases various useful methods. The following table gives you a short overview of them:

Method	Description
GetNeedlePosition()	Returns the actual position of the needle center.
GetNeedleMinPosition()	Returns the leftmost possible position of the needle center (left end of the needle movement range).
GetNeedleMaxPosition()	Returns the rightmost possible position of the needle center (right end of the needle movement range)

You can call those methods whenever your GUI component implementation requires the corresponding information. More sophisticated, however, is to join the update mechanism provided natively by the Horizontal Value Bar widget. Precisely, when you assign a slot method to the value bar's property OnUpdate, the slot method will receive postsignals every time the needle's position changes. Accordingly, within the slot method you can react on this notification and e.g. arrange other views at the new position. The following steps describe how to do this:

Assuming, your GUI component contains a Horizontal Value Bar named TemperatureBar and a Text view named TemperatureLabel. Furthermore let's assume you want the Text view to appear arranged automatically just below the needle separated by an additional small margin. In such application case implement the slot method with following Chora code:

With such implementation, every time the needle in the Horizontal Value Bar changes its position, the Text view is updated automatically. The decoration views follow automatically the movements. This is even true if the value bar is configured to display only the bars without any needle. The position where the both bars join together corresponds to the position where the needle would appear:

The following example project demonstrates this application case. When you download and open the example, you will see two Horizontal Value Bars with their associated and automatically arranged Text views:

If desired, you can hide the Horizontal Value Bar so it is not visible to the user. You achieve this by setting the property Visible of the affected value bar to the value false. Please read the section Control the visibility of nested components for further details and more precise explanation.

Newly added Horizontal Value Bars use an appearance configuration provided per default with Embedded Wizard installation. As described above these default configurations are available in two different designs and three sizes you can select easily. If you like them, you can use them as they are. However, should the value bars in your GUI design have another appearance, then you will need to provide your own appearance configuration.

To provide a new configuration you create an object of the class WidgetSet::HorizontalValueBarConfig and initialize its properties with all the bitmaps, colors and other parameters particular to your own design. Once this object is available, you can assign it to every Horizontal Value Bar you want to appear with this configuration similarly as you select one of the per default provided configurations. If necessary, you can create several different configuration objects and use them simultaneously within your application. You can even customize every Horizontal Value Bar instance individually.

Before you start to customize your own Horizontal Value Bars you should understand from which views (visual elements) the Horizontal Value Bars are composed of. In the configuration object you can individually specify parameters for every view. Understanding this internal structure is thus essential. The following table provides an overview of the views existing internally within every Horizontal Value Bar:

Visual element	Description
Face	A bitmap frame view filling vertically centered the entire width in the background of the value bar.
TrackLeft	A visual element composed of bitmap frame, filled rectangle and border views filling vertically centered the background of the value bar between its left edge and the actual position of the needle. The bitmap, colors, border width and the height of the track can be configured.
TrackRight	A visual element composed of bitmap frame view, filled rectangle and border views filling vertically centered the background of the value bar between the actual position of the needle and the right edge of the value bar widget. The bitmap, colors, border width and the height of the track can be configured.
Needle	An image view displayed vertically and horizontally centered at the needle position according to value bar's current value.
Cover	A bitmap frame view filling vertically centered the entire width of the value bar and covering so eventually other views belonging to the value bar. As its name indicates, Cover is intended to display decorations in the widget.

The following figure demonstrates once more the above described views existing internally in every Horizontal Value Bar. Please note how the visual elements are arranged one above the other. Per default, the visual element Face resides in the background of the widget:

Please note, the set of views existing within the Horizontal Value Bar is finished implemented in the Horizontal Value Bar component and can't be modified. With the configuration object you can customize the appearance of the affected views only. If you expect the Horizontal Value Bar to appear and behave beyond our default implementation, you will need to implement your own value bar component. Please see the section Widgets versus Component templates.

The following sections are intended to provide you an introduction and useful tips of how to work with the Horizontal Value Bar Config object. For the complete reference please see the documentation of the WidgetSet::HorizontalValueBarConfig class.

Depending on your application case, you have the option to add the configuration object as an embedded object directly to a GUI component or to add it as an autoobject to a unit. The first case is suitable if you want the configuration object to be used only by Horizontal Value Bars existing locally within the GUI component. The second case, in turn, is appropriate if you intend to share the configuration object among multiple GUI components like a kind of common resource.

To add a new Horizontal Value Bar Config object do following:

As long as the Horizontal Value Bar Config object is selected you can inspect and modify its properties conveniently in the Inspector window as demonstrated with the property FaceBitmap in the screenshot below. Please note, for better overview the below screenshot has been made with Inspector window being configured to sort the properties by categories:

As explained in the section above the Face view occupies vertically centered the entire width in the background of every Horizontal Value Bar. With the following properties you specify the bitmap resource as well as other parameters to be used by this view. In other words, you use them to configure the appearance of the Horizontal Value Bar's background:

Property	Description
FaceBitmap	With this property you specify the bitmap resource the Horizontal Value Bar has to display in its background Face view.
FaceFrame	This property is relevant only if the bitmap resource specified in the above described property FaceBitmap contains more than one frame. In such case you use it to determine the desired frame number. Is the bitmap additionally configured as containing an animated sequence you can initialize the FaceFrame property with the value -1 to instruct the Horizontal Value Bar to automatically play the animation.
FaceTint	The effect of this property depends on the type of the bitmap resource specified in the above described property FaceBitmap. In case of an alpha-only bitmap you use this property to determine the color to tint the bitmap. In all other cases you can use the alpha value of FaceTint property to simply modulate the opacity of the bitmap.

The specified bitmap will fill vertically centered the entire width of the Horizontal Value Bar. This is achieved by so-called 9-slice image scaling technique where the intended destination area is filled with slices copied from the original bitmap. In case of the Horizontal Value Bar, however, the slices are copied horizontally only. In the vertical direction, the bitmap retains its original height and it is just centered within the background area. Therefore, if you want the Horizontal Value Bar to be flexibly resizable, you have to ensure that the used Face bitmap is composed of three equally sized slices arranged in a single row as shown in the following figure. You should consider this aspect when designing the bitmap in a graphic editor:

In turn, if the bitmap in the background of your Horizontal Value Bar is intended to always have the same fixed width, you can ignore the above bitmap design restrictions. Just design your desired bitmap and explicitly define size constraints for the widget itself to ensure, that its width is fixed and it corresponds to the of the used Face bitmap.

As explained in the section above the TrackLeft view occupies vertically centered the background area of the value bar between its left edge and the actual position of the needle. With the following properties you specify the bitmap resource as well as other parameters to be used by this view. In other words, you use them to configure the appearance of the track displayed on the left of the value bar's needle:

Property	Description
TrackLeftBitmap	With this property you specify the bitmap resource the Horizontal Value Bar has to display in its background TrackLeft view.
TrackLeftFrame	This property is relevant only if the bitmap resource specified in the above described property TrackLeftBitmap contains more than one frame. In such case you use it to determine the desired frame number. Is the bitmap additionally configured as containing an animated sequence you can initialize the TrackLeftFrame property with the value -1 to instruct the Horizontal Value Bar to automatically play the animation.
TrackLeftTint	The effect of this property depends on the type of the bitmap resource specified in the above described property TrackLeftBitmap. In case of an alpha-only bitmap you use the property to determine the color to tint the bitmap. In all other cases you can use the alpha value of the TrackLeftTint property to simply modulate the opacity of the bitmap.

The specified bitmap will fill vertically centered the Horizontal Value Bar between its left edge and the actual needle position. This is achieved by so-called 9-slice image scaling technique where the intended destination area is filled with slices copied from the original bitmap. In case of the Horizontal Value Bar, however, the slices are copied horizontally only. In the vertical direction, the bitmap retains its original height and it is just centered within the value bar's area. Therefore, you have to ensure that the used TrackLeft bitmap is composed of three equally sized slices arranged in a single row as shown in the following figure. You should consider this aspect when designing the bitmap in a graphic editor:

As explained in the section above the TrackRight view occupies vertically centered the background area of the value bar between the actual position of the needle and the value bar's right edge. With the following properties you specify the bitmap resource as well as other parameters to be used by this view. In other words, you use them to configure the appearance of the track displayed on the right of the value bar's needle:

Property	Description
TrackRightBitmap	With this property you specify the bitmap resource the Horizontal Value Bar has to display in its background TrackRight view.
TrackRightFrame	This property is relevant only if the bitmap resource specified in the above described property TrackRightBitmap contains more than one frame. In such case you use it to determine the desired frame number. Is the bitmap additionally configured as containing an animated sequence you can initialize the corresponding TrackRightFrame property with the value -1 to instruct the Horizontal Value Bar to automatically play the animation.
TrackRightTint	The effect of this property depends on the type of the bitmap resource specified in the above described property TrackRightBitmap. In case of an alpha-only bitmap you use the property to determine the color to tint the bitmap. In all other cases you can use the alpha value of the TrackRightTint property to simply modulate the opacity of the bitmap.

The specified bitmap will fill vertically centered the Horizontal Value Bar between the actual needle position and the value bar's right edge. This is achieved by so-called 9-slice image scaling technique where the intended destination area is filled with slices copied from the original bitmap. In case of the Horizontal Value Bar, however, the slices are copied horizontally only. In the vertical direction, the bitmap retains its original height and it is just centered within the value bar's area. Therefore, you have to ensure that the used TrackRight bitmap is composed of three equally sized slices arranged in a single row as shown in the following figure. You should consider this aspect when designing the bitmap in a graphic editor:

Starting with version 13, the Horizontal Value Bar enhances its visual element TrackLeft by a rectangle and border views. Those new views display the track using scalable vector graphic so that the Horizontal Value Bar is not restricted anymore to use bitmap resources only. To configure the area and the shape of the new views, following properties are available:

Property	Description
TrackLeftThickness	This property determines the height in pixel of a filled rectangle and border belonging to the left track. That means, the property controls the height of the track.
TrackLeftCornerRadius	This property controls the rounding at corners of the track views. Normally, the track views have the shape of a rectangle with sharp corners. Specifying a value greater than 0 in the property rounds the corners. The larger the value, the bigger the rounding effect.
TrackLeftFlattened	This property controls the appearance of the left track at its edge corresponding to the actual needle position. Per default the corners at the edge are rounded according to the value specified in the above mentioned TrackLeftCornerRadius property. By configuring the property TrackLeftFlattened with the value true, the corner rounding occurs only when the track has assumed its rightmost position. As long as the track is smaller, the edge at the actual needle position is clipped (it appears flattened). The rightmost position for the track is configured by the property TrackLeftMarginRight.

The following figure demonstrates the effect of diverse property combinations. The gray thin borders indicate the areas of the resulting Value Bar. For demonstration purpose the track views are configured to appear with rounded corners:

Starting with version 13, the Horizontal Value Bar enhances its visual element TrackLeft by a rectangle and border views. Those new views display the track using scalable vector graphic so that the Horizontal Value Bar is not restricted anymore to use bitmap resources only. As described in the section above the shape of the new track views can be configured. With following properties you configure the colors to fill the background of the track and to stroke its borders:

Property	Description
TrackLeftColor	This property determines the color to fill the background of the track.
TrackLeftBorderWidth	This property determines the thickness of the border surrounding the track.
TrackLeftBorderColor	This property determines the color to stroke the border surrounding the track. To see the border ensure that the property from the list above configure the border thickness greater than 0.

The following figure demonstrates the effect of diverse property combinations. The gray thin borders indicate the areas of the resulting Horizontal Value Bar. For demonstration purpose the track views are configured to appear with rounded corners:

Starting with version 13, the Horizontal Value Bar enhances its visual element TrackRight by a rectangle and border views. Those new views display the track using scalable vector graphic so that the Horizontal Value Bar is not restricted anymore to use bitmap resources only. To configure the area and the shape of the new views, following properties are available:

Property	Description
TrackRightThickness	This property determines the height in pixel of a filled rectangle and border belonging to the right track. That means, the property controls the height of the track.
TrackRightCornerRadius	This property controls the rounding at corners of the track views. Normally, the track views have the shape of a rectangle with sharp corners. Specifying a value greater than 0 in this property rounds the corners. The larger the value, the bigger the rounding effect.
TrackRightFlattened	This property controls the appearance of the right track at its edge corresponding to the actual needle position. Per default the corners at the edge are rounded according to the value specified in the above mentioned TrackRightCornerRadius property. By configuring the property TrackRightFlattened with the value true, the corner rounding occurs only when the track has assumed its leftmost position. As long as the track is smaller, the edge at the actual needle position is clipped (it appears flattened). The leftmost position for the track is configured by the property TrackRightMarginLeft.

The following figure demonstrates the effect of diverse property combinations. The gray thin borders indicate the areas of the resulting Value Bar. For demonstration purpose the track views are configured to appear with rounded corners:

Starting with version 13, the Horizontal Value Bar enhances its visual element TrackRight by a rectangle and border views. Those new views display the track using scalable vector graphic so that the Horizontal Value Bar is not restricted anymore to use bitmap resources only. As described in the section above the shape of the new track views can be configured. With following properties you configure the colors to fill the background of the track and to stroke its borders:

Property	Description
TrackRightColor	This property determines the color to fill the background of the track.
TrackRightBorderWidth	This property determines the thickness of the border surrounding the track.
TrackRightBorderColor	This property determines the color to stroke the border surrounding the track. To see the border ensure that the property from the list above configure the border thickness greater than 0.

The following figure demonstrates the effect of diverse property combinations. The gray thin borders indicate the areas of the resulting Horizontal Value Bar. For demonstration purpose the track views are configured to appear with rounded corners:

Per default, the left track fills the area between the left edge of the widget and the actual needle position. When the needle moves, the width of the track is adjusted automatically. If this is not desired, configure the property TrackLeftStatic with the value true. Now, the width of the left track is fixed filling horizontally the entire area of the Value Bar regardless of the current needle position. The following figure demonstrates the effect of this property (the gray borders indicate the areas of the respective widget):

Further properties TrackLeftMarginLeft and TrackLeftMarginRight are useful to determine the minimal distances in pixel between the left/right edges of the Value Bar and the corresponding ends of the track. The so configured margins limit the range in which the track's width may change. Once the margin is reached, the track stops growing. This is also true for tracks configured to have fixed width (property TrackLeftStatic). In such case, the static track will fill the area between the margins. The following figure demonstrates the effect of the margins (the gray borders indicate the areas of the respective widget):

Unless it was explicitly configured, the tracks are centered vertically within the Value Bar's area. By using the property TrackLeftOffset an additional vertical displacement for the track can be configured. For example, the Track views may appear slightly shifted:

Per default, the right track fills the area between the actual needle position and the right edge of the widget. When the needle moves, the position and the width of the track are adjusted automatically. If this is not desired, configure the property TrackRightStatic with the value true. Now, the width of the right track is fixed filling horizontally the entire area of the Value Bar regardless of the current needle position. The following figure demonstrates the effect of this property (the gray borders indicate the areas of the respective widget):

Further properties TrackRightMarginLeft and TrackRightMarginRight are useful to determine the minimal distances in pixel between the left/right edges of the Value Bar and the corresponding ends of the track. The so configured margins limit the range in which the track's width may change. Once the margin is reached, the track stops growing. This is also true for tracks configured to have fixed width (property TrackRightStatic). In such case, the static track will fill the area between the margins. The following figure demonstrates the effect of the margins (the gray borders indicate the areas of the respective widget):

Unless it was explicitly configured, the tracks are centered vertically within the Value Bar's area. By using the property TrackRightOffset an additional vertical displacement for the track can be configured. For example, the Track views may appear slightly shifted:

The left and the right track images fill the corresponding areas on the left and on the right of the needle. As described in the chapters above, it is achieved by so-called 9-slice image scaling technique where the respective area is filled with slices copied from the original track bitmap. The both track images join together at the current needle position. To produce an effect of the both tracks being connected seamlessly, the tracks are per default truncated at this position. You can imagine, the right cap of the left track and the left cap of the right track are not displayed. This is demonstrated in the following figure:

This truncation is not always desired. Depending on the design of your individual value bar, it can be necessary to always display the whole track inclusive its both end caps. This can be controlled by modifying the properties TrackLeftWithEdge and TrackRightWithEdge. If you assign the value true to the property TrackLeftWithEdge, the left track is not truncated anymore. It appears with its all edges. Similarly, if you initialize TrackRightWithEdge with true, the right track is not truncated. You can also combine both. The following figure demonstrates the effect of these properties:

As explained in the section above the Needle view is displayed centered at the actual needle position within the value bar's area. With the following properties you specify the bitmap resource as well as other parameters to be used by this view. In other words, you use them to configure the appearance of the needle image in the foreground of the value bar:

Property	Description
NeedleBitmap	With this property you specify the bitmap resource the Horizontal Value Bar has to display in its foreground Needle view.
NeedleFrame	This property is relevant only if the bitmap resource specified in the above described property NeedleBitmap contains more than one frame. In such case you use it to determine the desired frame number. Is the bitmap additionally configured as containing an animated sequence you can initialize the NeedleFrame property with the value -1 to instruct the Horizontal Value Bar to automatically play the animation.
NeedleTint	The effect of this property depends on the type of the bitmap resource specified in the above described property NeedleBitmap. In case of an alpha-only bitmap you use the property to determine the color to tint the bitmap. In all other cases you can use the alpha value of the NeedleTint property to simply modulate the opacity of the bitmap.

The specified bitmap will appear centered vertically and horizontally at the position resulting from the value bar's current value. This corresponds to the position where the left and right tracks join together. The needle overlays this position.

Per default, the needle can move freely across the entire width of the Horizontal Value Bar. If this is not desired, you can specify in the properties NeedleMarginLeft and NeedleMarginRight additional gaps in pixel between the needle image and the respective left or right edge of the value bar. The following figure demonstrates the effect of these properties (the gray borders indicate the areas of the respective value bar):

Please note, if your Horizontal Value Bar is configured to appear without any needle, the specified margins are still valid. The properties NeedleMarginLeft and NeedleMarginRight determine in this case the minimal distances between the position where the both tracks join together and the respective left or right edges of the widget. In other words, by using the properties you can specify the minimum width for the corresponding left and right tracks.

Unless it was explicitly configured, the center of the needle and the position where the both tracks join together do match. In other words, the needle appears vertically centered at the tracks join position. By using the property NeedleOffset an additional displacement for the needle can be configured. The displacement is useful, for example, to correctly adjust the needle position:

As explained in the section above the Cover view occupies vertically centered the entire width in the foreground of every Horizontal Value Bar. Thus as its name indicates, it is intended to be used as a kind of cover, mask, etc. overlaying the needle and the tracks. With the following properties you specify the bitmap resource as well as other parameters to be used by this view. In other words, you use them to configure the appearance of the Horizontal Value Bar's foreground:

Property	Description
CoverBitmap	With this property you specify the bitmap resource the Horizontal Value Bar has to display in its foreground Cover view.
CoverFrame	This property is relevant only if the bitmap resource specified in the above described property CoverBitmap contains more than one frame. In such case you use it to determine the desired frame number. Is the bitmap additionally configured as containing an animated sequence you can initialize the CoverFrame property with the value -1 to instruct the Horizontal Value Bar to automatically play the animation.
CoverTint	The effect of this property depends on the type of the bitmap resource specified in the above described property CoverBitmap. In case of an alpha-only bitmap you use the property to determine the color to tint the bitmap. In all other cases you can use the alpha value of the CoverTint property to simply modulate the opacity of the bitmap.

The specified bitmap will fill vertically centered the entire width of the Horizontal Value Bar. This is achieved by so-called 9-slice image scaling technique where the intended destination area is filled with slices copied from the original bitmap. In case of the Horizontal Value Bar, however, the slices are copied horizontally only. In the vertical direction, the bitmap retains its original height and it is just centered within the value bar's area. Therefore, if you want the Horizontal Value Bar to be flexibly resizable, you have to ensure that the used Cover bitmap is composed of three equally sized slices arranged in a single row as shown in the following figure. You should consider this aspect when designing the bitmap in a graphic editor:

In turn, if the bitmap in the foreground of your Horizontal Value Bar is intended to always have the same fixed width, you can ignore the above bitmap design restrictions. Just design your desired bitmap and explicitly define size constraints for the widget itself to ensure, that its width is fixed and it corresponds to the of the used Cover bitmap.

The Horizontal Value Bar widget implements an effect to react to changes of the widget's current value with an animation. Accordingly, the needle does not jump when the value changes. Instead, it slides smoothly between its actual and the new position.

The maximum time how long the animation should take can be configured as a value in milliseconds in the property SwingDuration. However, the real duration is proportional to the actual distance to move the needle. The shorter the distance, the faster the animation. If this animation effect is not desired in your individual Horizontal Value Bar widget, initialize the property SwingDuration with the value 0.

With the further property SwingElastic you can configure the timing (the easing) for the animation effect. If this property is false, the animation will be performed with the ordinary FastIn_EaseOut timing. In turn, if you initialize the property SwingElastic with the value true, the animation will be performed with the more sophisticated BackOut timing resulting in the animation having characteristic similar to a physical object with its mass and inertia.

Up to version 12 inclusive the Z-order of visual elements belonging to the Horizontal Value Bar (the order in which the views are displayed one above the other) was fixed predetermined. The Face visual element, for example, was displayed always in the background of the widget while the Needle and Cover views in the foreground. Starting with the version 13, the Z-order can be modified. For this purpose you specify for each visual element its stacking priority value as integer number. As consequence, visual elements with higher stacking priority will overlap visual elements with lower stacking priority. To configure the stacking priority use following properties:

Property	Affected visual element	Default value
FaceStackingPriority	The Face view.	1
TrackRightStackingPriority	Views belonging to the TrackRight visual element.	2
TrackLeftStackingPriority	Views belonging to the TrackLeft visual element.	3
NeedleStackingPriority	Views belonging to the Needle visual element.	4
CoverStackingPriority	The Cover view.	5

With the both properties WidgetMinSize and WidgetMaxSize you can configure size constraints for all Horizontal Value Bars using your configuration object. For example, if your Horizontal Value Bars can not become smaller than 100x50 pixel, initialize the property WidgetMinSize with the value <100,50>. Similarly, by initializing the property WidgetMaxSize you determine the maximum size the value bars may assume at the runtime. Trying to resize the value bars beyond the specified size constraints will be automatically suppressed.

Per default, the properties are initialized with the values <0,0> which means, that no constraints have to be taken in account. If desired, you can also specify constraints only for the width or the height of the value bar. For example, if your value bars are flexibly resizable in the horizontal direction but they should have fixed height of 100 pixel, you initialize the both properties with the value <0,100>.

The appearance of the Value Bar is limited to the visual elements that compose it. To overcome this limitation you can enrich the Value Bar by additional decoration views. The section Combine the Value Bar with decoration views explains how to do this in context of a GUI component containing the Value Bar. That means, the Value Bar and the additional decoration views are siblings in context of the superior GUI component. The code necessary to update the appearance of the decoration views is implemented directly within the GUI component.

This approach is practicable when there are only few Value Bars you want to combine with decoration views or the Value Bars should have different appearance. If you require multiple Value Bars to be enhanced by the same set of decoration views, the necessary implementation may become less convenient resulting in the same code being repeated for each Value Bar instance.

To avoid the code repetition you can associate the necessary update implementation directly to the Value Bar Config object. The update implementation will then affect all Value Bars which are using this configuration object. The Value Bar Config object provides for this purpose a property OnUpdate. When you assign a slot method to this property, the slot method will receive postsignals every time the state of any of the associated widgets has changed.

Similarly to how the section Combine the Value Bar with decoration views explains, you implement within the slot method the code to update the position, size and appearance of the decoration views. The approach using the common implementation has however following peculiarities:

The following code demonstrates a typical implementation of the slot method associated to the OnUpdate property of the Horizontal Value Bar Config object. In this example, we enhance the Horizontal Value Bar by a simple Filled Rectangle view. This decoration view is visible only when Value Bar's value is greater than 50:

The above sections explained how you create and configure your own Horizontal Value Bar Config objects practically from scratch. This is usual when you have your own GUI design. However, if you prefer to use the configurations provided per default with Embedded Wizard and you want only few settings to be changed, it is more convenient to create a copy of the existing configuration object and adapt the affected property only. Let's assume you want to use the WidgetSet::HorizontalValueBar_Lime_Large configuration but with different margins on the left and right of the needle. In such case do following: