Solution
UI enabled embedded targets run NI Linux Real-Time. When these Linux RT targets have Embedded UI enabled they run the XFCE Desktop Environment to provide the UI. There are fundamental differences between the way that Windows and XFCE draw their Users Interfaces and that causes your VI to render differently on the respective devices.
Designing Your Embedded UI:You may want to design an Embedded UI that has the same look as your Windows Host VI or you may want to make your Embedded UI look like modern devices. To accomplish these goals review the suggestions listed below.
- Fonts
Font styles and sizes render differently on Windows Host VIs and Embedded UIs. When choosing font sizes, stick to the sizes recommended: 9, 12, 14, 18, 24, or 36. These font sizes are supported on embedded targets. If you choose a font size that is in between these sizes, it is possible that the size is unsupported and the embedded target will choose the closest supported size automatically. In general, fonts will appear larger on the embedded target. To mitigate change in text position, you can use center justification. See the images below for reference. Since font style and size can change when deploying to your embedded UI, it is recommended to always test and verify the final appearance before distributing your application.
Windows Host Embedded Target
- Controls
Controls will render differently on Windows Host VIs and Embedded UIs. Control functionality will be the same but the visual appearance of controls will differ. To build a UI that looks similar on both the Embedded display and the Host display, we suggest using the Classic Controls Palette. If you want to build a more simplistic UI or a UI with a modern look we suggest the System or Silver Controls Palette. Below is a comparison of the different Palettes under both the Windows context and the Embedded context.
