NWare now provides support for the MediaMatrix D1V and D4S hardware devices. There are new devices in the devices tree, under Hardware / D Series Controls.
For more information, see D Series Controls in the NWare Device Reference. Also refer to the D Series Hardware Manual.
You can now select an option in NWare to display the value selected on a fader just above the handle as the fader moves. For more information, see Displaying the value of a fader as a tooltip in the NWare User Guide.
You can now control the appearance of combo boxes in Kiosk2Go by specifying different settings, including the font name and size, background color and border color. For more information, see Customizing the appearance of a combo box in the NWare User Guide.
When you add a knob control to a Kiosk2Go device page, it is now easier to specify images to enhance its appearance. For more information, see Specifying the control graphics in the NWare User Guide.
You can now specify a color to display in the area surrounding the Kiosk2Go device in the browser. For more information, see Adding a background color to the Kiosk2Go device in the NWare User Guide.
Previously, when the image used for the background of a fader was scaled, the image used for the fader handles was also scaled. In this version, you can choose whether to scale the fader handle when the background image is scaled. For more information, see Specifying the control graphics in the NWare User Guide.
When you add a K2G Dialog device to your project, the layout properties will now allow you to specify the dialog type:
You can also add a drop shadow.
For more information, see Using dialogs to interact with the user in the NWare User Guide.
As an alternative to using the standard help and close buttons for dialogs, you can add your own customized buttons to perform these functions.
For more information, see Using custom help and close buttons on dialogs in the NWare User Guide.
You can now store help text for Kiosk2Go controls in a file, instead of adding the text directly to each control. This allows the help text to be produced and managed using an external help tool. The help text is linked to the Kiosk2Go controls using help IDs. For more information, see Adding help text using a topic file in the NWare User Guide.
Previously, if you started Kiosk2Go using a url containing a device name, and the project contained several devices, you were still prompted to select a device from a list. Now, if your user name has access to the device, it will be opened immediately.
When you create a meter using a Generic Controls device, you can now specify the gain labels (shown at the side of the meter) on the Type tab. There is no need to use the Inspector. For more information, see Type in the NWare Device Reference.
When you use the Clean Project feature, it will now remove several types of files from the project to save space. These include: .exe, .xml, .fsl, .json and .dat.
If you have a hardware key that was issued since the release of 1.7.2, you will not need to specify an activation key via the web interface in order to use the device. The presence of the green USB hardware key in the nControl will be sufficient for the product to operate.
Note: Even if you upgrade the firmware to version 1.7.2, nControls with older hardware keys will require an activation key to operate.
If you connect to Kiosk2Go in a browser on the iPad, then repeatedly tap a list control to open and close it, this can cause the browser to crash. This problem has been seen when running Kiosk2Go full screen, via an Add to Home Screen shortcut; it also affects Google Chrome versions prior to 39.0.2171.45.
This issue affects iPads running iOS 8.1, 8.1.1 and 8.1.2, but not previous versions. It does not affect iPhones, iPod Touches or any devices running Android.
As a workaround, we recommend that you use the Kiosk2Go application for iOS or Android, which is not affected by this issue.
If you are using Internet Explorer 10, Kiosk2Go pages that contain many knob controls can take a long time to render in the browser.
Recommended workaround: Upgrade your browser to Internet Explorer 11 or higher.
If you are using Internet Explorer 10, placing an image generic control on top of a string generic control will prevent the string control from working.
Recommended workaround: Upgrade your browser to Internet Explorer 11 or higher.
When you type characters with diacritics, such as š and ý, into a string control, they are corrupted when the project is emulated or deployed.
If you add a Global Preset device to your project, select the System Mute option on the NioNode control surface, and then save the default global preset, when the NioNode is restarted, the system mute is not applied, even though it was saved in the preset.
If you deploy a project containing a Comms Processor device to a Nionode, and then try to use the ports COM3 or COM4, the role will restart.
If a project contains a NION nX/nE device, an nTouch 180 device and a Wave File Player, an error is reported at deploy time. The NION role deploys successfully, but the nTouch 180 role fails to deploy.
When a text value was passed to an LED generic control to specify the color, NWare showed the color correctly, but it was not shown correctly in the browser running Kiosk2Go.
A transparent polygon button configured to open a Kiosk2Go device did not work when placed inside a K2G dialog device.
Kiosk2Go slave control functionality now matches Kiosk. Slave controls cannot be gestured.
Meter-tricolor generic controls showed black bars as values changed, rather than multi-colored bars.
If you arranged a series of buttons in a Kiosk2Go device, then configured them to work as a radio button group, they did not operate correctly. Buttons remained in the down state after being gestured, instead of returning to the up state.
Buttons copied from an nTouch 180 NWare device to a Kiosk2Go device, did not display in the browser.
Loading a project that had been saved when it did not contain any devices caused NWare to display an error: This project was created with an earlier version of NWare..., when actually the project had been created using the same version of NWare.
NION was previously susceptible to the Shellshock or Bashdoor security bug. This vulnerability has now been fixed. For more information on the bug, see Wikipedia - Shellshock.
The Hardware page in the NION web interface has a button at the bottom of the page for running Diagnostics. When you click this button, you must now enter a user name and password in order to proceed. Previously, log on credentials were not required, which meant it was possible for web crawlers indexing the web pages of the NION to start the diagnostics running.