-
Notifications
You must be signed in to change notification settings - Fork 25
Migrating from UwTerminal
UwTerminalX is a rewrite of UwTerminal using Qt - this means that the vast majority of features available in UwTerminal can also be found in UwTerminalX, however not everything has been ported over and some functions differ slightly:
UwTerminal does not support UTF-8 data or characters and will display UTF-8 characters as it's ASCII representation, UwTerminalX however does support UTF-8 data and will display all supported UTF-8 characters.
UwTerminal has a function called 'File player', this feature has not been ported to UwTerminalX and therefore is not available
UwTerminal has a 'BASIC' tab for testing smartBASIC commands and syntax, this feature has not been ported to UwTerminalX and therefore is not available.
UwTerminal supports acting as a TCP host over the network or connecting to a client over TCP, this functionality is not supported in UwTerminalX
UwTerminal supports XCompiling applications using XCompiler executables on the local system, this is supported in UwTerminalX but due to XCompilers being Windows Executable files, this functionality is not available on the Mac or Linux builds of UwTerminalX.
There is instead a new online XCompilation feature which uses a cloud Laird server to XCompile applications for modules and is supported on Windows, Linux and Mac versions of UwTerminalX.
UwTerminal has command line arguments for selecting a COM port with just a number, e.g. COM=2, this command line argument is supported in UwTerminalX as a migration feature for the Windows release, so it can use either the full device name or just the COM port number (COM=2 or COM=COM2). On Linux and Mac builds, this will need be the full path of the device, e.g. COM=/dev/ttyS0
UwTerminal has an option to poll a USB port if it becomes disconnected and automatically reopen the connection to the device if it becomes available again, this feature has not been ported to UwTerminalX and therefore is not available.
In UwTerminal, when data is received from a module, it will be displayed instantly on the screen, however in UwTerminalX there is a slight delay, this is because UwTerminalX uses a display buffer instead of just directly adding data to the output.
The delay in screen updating is user-configurable from the UwTerminalX.ini file, 'TextUpdateInterval' which is by default 80 (milliseconds), decreasing this will give faster screen updates at the expense of greater CPU usage, increaseing this will give slower screen updates but have lower CPU utilisation.
In UwTerminal, the text is colour coded depending upon what the data is, however in UwTerminalX, the terminal display is monotone and all text is one colour.
Both UwTerminal and UwTerminalX have error code lookup functionality, in UwTerminal an error code in hex can be looked up from the right click menu, in UwTerminalX there are two functions for looking up error codes depending upon the output format of the error code. UwTerminal's error code functionality is equivalent to 'Lookup Selected Error-Code (Hex)' in UwTerminalX.
Sample smartBASIC code to output error code in hex format (required for UwTerminal error-code lookup):
dim rc : rc = 5
PRINT "Error Code: ";INTEGER.H'rc;"\n"
Sample smartBASIC code to output error code in integer format:
dim rc : rc = 5
PRINT "Error Code: ";rc;"\n"