-
Notifications
You must be signed in to change notification settings - Fork 25
Caveats
This page lists some caveats in UwTerminalX:
If using UwTerminalX on the original Raspberry Pi there may be some issues with downloading to modules having errors or where the general response time of UwTerminalX is slow, this is due to the slow speed of the single-core CPU on the original Raspberry Pi board. It is not recommended to use this board for performing speed tests as it is likely that the CPU will become a bottleneck when transferring data.
If a shortcut is made to UwTerminalX, then the 'Start In' directory needs to match up with the directory that UwTerminalX is in for things like local XCompilers to be found in the executable directory.
Whilst dragging the UwTerminalX window, the event loop will not process so any current proceedures such as downloading a file will pause until the window stops being dragged.
Byte count when streaming is bytes sent out to the buffer, not the total number of bytes actually sent out to the device
On Linux, UwTerminalX does not have an icon, this is because icons are not stored as part of programs as they are on Windows/Mac.
This seems to be a problem with Qt, buttons of different sizes are all styled differently for reasons unknown: https://forum.qt.io/topic/51596/in-os-x-qpushbutton-spontaneously-changes-style-when-width-is-less-than-50-pixels/2
When running on Mac, devices will appear as cu.<device> and tty.<device>. The tty.<device> should be selected.
When running on FreeBSD, there is a bug in Qt that will list 3 devices for each serial port in the system, <device>, <device>.lock and <device>.init.
The .lock and .init devices are not valid serial ports and attempting to open them will fail, the valid devices are those without .lock or .init at the end.