- Using Google Charts as an Alternative to the Built-in Chart Controls
/documentation/pages/Guides/Mobile and Web Components/UX/Controls/Data Controls/Chart/Using Google Charts as an Alternative to the Built-in Chart Controls.xml
The UX component contains a powerful built-in chart control (based on the Microsoft .Net visualization library). This is a 'server-side' control (meaning that the chart is rendered on the server and then the resulting image is sent to the browser.
Text box controls can be used to create edit combo boxes.
- Editor Settings
/documentation/pages/Guides/Mobile and Web Components/UX/Controls/Props/other/Form Properties/Form properties/Fields/Editor Settings/index.xml
The Editor Settings inside the FormView builder allow you to define values to
be passed to any editor or editor set containers in the ux component. Whether or not these
values are consumed is determined inside the [Editor Properties] on each editor.
- Set Editor
The Set Editor written in Xbasic makes it substantially faster to open a Set for editing than was the case with previous Set Editors that were written in MFC; especially when editing Sets based on active-link tables.
- Editor Properties
/documentation/pages/Guides/Mobile and Web Components/UX/Controls/Props/container/Editor Properties/index.xml
be used in manipulating values that are defined inside the editor
itself, usually on the controls contained within the editor. This lets
you decide whether or not you want a property to be consumed inside an editor.
/documentation/pages/Guides/Mobile and Web Components/UX/Controls/Defined Controls/Editor-Camera.xml
Inserts an 'Editor' for capturing an image using the Camera. IMPORTANT: This control
MUST be inserted inside an Editor-Set control.
/documentation/pages/Guides/Mobile and Web Components/UX/Controls/Defined Controls/Editor-List.xml
Inserts an Editor for editing a value using a List control. IMPORTANT: This control MUST
be inserted inside an Editor-Set control. NOTE: The properties of the List used in the editor can be configured by a genie
in the FormView builder.
- Ink Editor
/documentation/pages/Guides/Mobile and Web Components/UX/Controls/Props/Data/Ink Properties/Ink properties/Ink Editor/index.xml
The Ink editor is the area where users draw. These properties determine if an editor has an overlay,
a selection of tools such as pens, erasers, and buttons that appears around the editor. There are also some properties
that effect the scaling in the editor and more.
- Creating a Script to Print a Report for a Selected Record
/documentation/pages/Desktop/Tutorial/Design/View/Database/Creating a Script to Print a Report for a Selected Record.xml
In this example, you will create a script that prints out a mailing label for a particular customer. The script will prompt the user for the customer's name. This script will be a Global Script. as you will recall, a Global Script appears in the Control Panel in the Code tab, and can be run by double-clicking the script name, or clicking the Run button.
- Status Bar Editor
/documentation/pages/Guides/Desktop/Design/View/Status Bar Editor.xml
This is what the status bar editor looks like: