****************************************************************************************************
YAT Release Notes
--------------------------------------------------------------------------------------------------
YAT - Yet Another Terminal.
Engineering, testing and debugging of serial communications. Supports RS-232/422/423/485...
...as well as TCP/IP Client/Server/AutoSocket, UDP/IP Client/Server/PairSocket and USB Ser/HID.
--------------------------------------------------------------------------------------------------
Visit YAT at https://sourceforge.net/projects/y-a-terminal/.
Contact YAT by mailto:y-a-terminal@users.sourceforge.net.
--------------------------------------------------------------------------------------------------
Copyright © 2003-2004 HSR Hochschule für Technik Rapperswil.
Copyright © 2003-2026 Matthias Kläy.
All rights reserved.
--------------------------------------------------------------------------------------------------
YAT is licensed under the GNU LGPL-2.1.
See https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html for license terms.
****************************************************************************************************
Contents
========
A. Download
B. Installation
C. Execution
D. History of changes in YAT
E. History of changes in XTerm232
F. Roadmap
G. Source Code Build
H. Package Build
I. Legal
====================================================================================================
A. Download
====================================================================================================
Go to YAT's SourceForge main page at https://sourceforge.net/projects/y-a-terminal/. The target's
default package can be downloaded from the main page. The complete set of packages can be downloaded
from YAT's SourceForge file page at https://sourceforge.net/projects/y-a-terminal/files/:
- Linux Mono x64 .deb package
- Linux Mono x64 .rpm package
- Linux Mono x64 binaries
- Windows x64 installer
- Windows x64 installer that includes the .NET runtime
- Windows x64 binaries
- Windows x86 installer
- Windows x86 installer that includes the .NET runtime
- Windows x86 binaries
How to choose the most appropriate package for Linux:
- For Debian based distributions, use the .deb package.
- For Red Hat and SUSE based distributions, use the .rpm package.
- Alternatively, use binaries.
How to choose the most appropriate package for Windows:
- For up-to-date systems, use the corresponding .msi file.
(Windows Installer and .NET are already installed on up-to-date systems.)
- For outdated systems or offline installation, use a full installer package "..._with_.NET...zip".
(Windows Installer and .NET are included for installation.)
- Alternatively, use binaries; optionally, install the monospaced "DejaVu" font used by YAT, and
assign the .yat/.yaw file extensions to "YAT.exe".
====================================================================================================
B. Installation
====================================================================================================
Linux
----------------------------------------------------------------------------------------------------
YAT packages are not yet upstreamed to any Linux distribution. Instead, download the appropriate
package according to section above and use the package manager to install the downloaded package.
YAT uses .NET 4.8, which on Linux is made available by Mono. YAT requires Mono 6.12 or above.
When installing a package, the package manager ensures that Mono is available on the target system.
1) If missing, the package manager will install "mono-complete" (on Debian, Ubuntu,...) or
"mono-core" and "mono-winforms" (on Red Hat, SUSE, Fedora,...).
2) Application files will be placed into /usr/bin and /usr/lib/yat.
3) Application meta data, documentation, icons and file type assignments will be placed into the
appropriate folders of /usr/share.
You can also install Mono prior to installing YAT.
For use of binaries, refer to the respective instructions.
Windows
----------------------------------------------------------------------------------------------------
It is recommended to unzip the package to a temporary location before starting the installation.
YAT uses .NET 4.8. The installer packages ensure that .NET 4.8 is available on the target system.
The installer packages also ensure that Windows Installer 4.5 is available on the target system.
For installation, run the ".msi" if Windows Installer is installed, otherwise "setup.exe".
1) Installer will check the prerequisites mentioned above and install what is missing.
2) Installer will install YAT. Older versions of YAT are automatically replaced.
3) Installer will install DejaVu monospaced fonts and assign YAT file types.
You can also download .NET and/or Windows Installer from https://www.microsoft.com/download
or by googling for "Download Microsoft .NET Framework 4.8" and/or "Windows Installer 4.5".
Installing .NET and/or Windows Installer requires administrator permission.
For use of binaries, refer to the respective instructions.
x86 (32-bit) -vs- x64 (64-bit)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
YAT can be installed as x86 or x64 application. x86 works on either 32-bit or 64-bit systems, given
64-bit provides 32-bit compatibility. x64 also works on either 32-bit or 64-bit systems, as YAT x64
is built as [Any CPU] for providing compatibility with MSIL projects. By default, x86 is installed
to "\Program Files (x86)" whereas x64 is installed to "\Program Files".
It is not possible to install both types for the same user. When changing from x86 to x64 of the
same version of YAT, or vice versa, the installed application must first be uninstalled before the
other type can be installed. If this limitation is not acceptable, create a new feature request
ticket and describe the impacts/rationale/use case as detailed as possible. Or use binaries, which
can be used in parallel without restrictions.
====================================================================================================
C. Execution
====================================================================================================
In standard mode, infos/warnings/errors are shown on the user interface, whereas in console mode,
notifications are returned via stdout/stderr and there will be no blocking modal dialogs.
Linux
----------------------------------------------------------------------------------------------------
Run `yat` or `mono usr/lib/yat/yat.exe` for standard mode.
Run `yatconsole` or `mono usr/lib/yat/yatconsole.exe` for console mode.
When starting YAT, there may be a GTK related error message, depending on Linux distribution and
installed packages:
* "Failed to load module "canberra-gtk-module""
=> `sudo apt install libcanberra-gtk-module` or `sudo dnf install libcanberra-gtk-module`
* "Gtk not found (missing LD_LIBRARY_PATH to libgtk-x11-2.0.so.0?), using built-in colorscheme"
=> `sudo apt install libgtk2.0-0` or `sudo dnf install gtk2`
Windows
----------------------------------------------------------------------------------------------------
[Start > Programs > YAT > YAT] or
run "C:\Program Files\YAT\YAT.exe" for standard mode.
Run "C:\Program Files\YAT\YATConsole.exe" for console mode.
====================================================================================================
D. History of Changes in YAT
====================================================================================================
YAT 2.8.0 with Mono/Linux :: 2026-06-07
----------------------------------------------------------------------------------------------------
New:
- Support for Mono/Linux (feature requests #381 and #401).
- Support of selected ANSI escape sequences incl. set/reset text color (feature request #294). To
optimally facilitate, additional neutral Tx/Rx format definitions and options on when to activate.
- Log files can now optionally be limited in number of lines and/or time; useful for chunking log
of long running sessions into multiple files (feature requests #423 and #497).
- Optionally, tell YAT to send raw file content, for all file types (feature request #504).
- Size of the raw buffers is configurable now (feature request #412, related to bug #459) and the
terminal's extent (line length and line count) can now optionally be set separately for Tx and Rx.
- Text terminals: Support for Mazovia code page 790 encoding (feature request #498).
- Text terminals: Decoder mismatch behavior also for single-byte encodings (feature request #522).
- Menu item to scroll to bottom and re-enable vertical auto-scrolling added (feature request #523).
Important changes:
- After changing settings, terminal content only gets refreshed as needed; e.g. switching log on/off
or changing I/O settings no longer triggers a refresh (bug #459, feature request #309).
- Duration of refreshing terminal content, reduced from up to several minutes (bug #459) down to
just a few seconds, even for large terminal content (result of the configurability of the raw
buffers, which now by default only hold up to 1 MB of raw data each Tx and Rx, see feat. #412).
- Duration for applying settings during startup, changing settings, and shutdown significantly
reduced; by eliminating unnecessary updates of the view's controls (related to changes above).
- Refreshing terminal content now happens asynchronously (feat. #514; related to changes above).
- Performance on copying formatted monitor content has further improved (follow-up to former bugs
#573, #574, #575; fixes bug #598 and feature request #346; related to changes above).
- Performance of [Send Characters Immediately] massively improved; and no longer quickly showing
characters corresponding to the pressed keys (related to feature requests #381 and #401).
- Display element handling refactored (related to feature request #294 related changes).
- Text terminals: Decoding and processing refactored (related to feature request #294).
- Time baselining added to all tests and basic terminal methods (related to feature request #294).
- Serial port deadlock recovery time-out increased from 5 to 20 seconds, large enough to cover a
known use case with a secure tunnel (bug #613; related to former bug #543 and others).
- Terminology "Serial COM Port" generalized to "Serial Port" for including Mono/Linux "tty" named
ports (related to feature requests #381 and #401).
- Several shortcuts changed/added for better aligning with Windows and Linux standard behavior:
> Open terminal settings changed from [Ctrl+Shift+S] to [Alt+Enter].
> Save workspace changed from [Ctrl+Shift+W] to [Ctrl+Shift+S].
> Close workspace added as [Ctrl+Shift+W].
> Close terminal [Ctrl+F4] accompanied by [Ctrl+W].
- [Terminal > Settings... > Text... > Encoding] can now also be entered by code page or name or
fragment thereof (feature request #330; along with feature request #498).
- In addition to [Enter], the YAT specific dialogs can now also be confirmed by [Ctrl+Enter], same
as e.g. dialogs of Visual Studio. Especially useful for dialogs containing other buttons, where
[Enter] will click the selected button, rather than accept the dialog.
- Various refinements to let the implementation better handle Mono/Linux (related to feature
requests #381 and #401). All workarounds related to Mono issues and limitations documented.
- Default main window size increased to 1366x768 (FWXGA).
- On Windows, system text scaling other that 100% is now reflected in most locations (bug #608,
works around limitation of Windows.Forms with .NET 7 and before). Issue will fully be fixed when
eventually upgrading the code base to .NET 8+ (feature request #369).
- YAT now tells Windows to not enter hibernation while data is being sent/received (feat. #525).
Especially useful with long "\!(Delay)" or "\!(LineDelay)" commands.
- YAT aligned with the Windows recommendation, which now follows the Unicode recommendation and no
longer recommends byte order mark (BOM) for UTF-8, it is now optional only. YAT log file setting
default adapted accordingly, and YAT no longer emits the BOM to settings files. In addition, BOM
removed from all source code files (related to feature requests #381 and #401).
- Settings previously called "Time Span" renamed to "Time Offset", for better distinguishing from
other time span related settings (along with feature requests #381 and #401).
- Logs previously called "Neat" renamed to "Display", reflecting the content rather than the format
(along with feature requests #412 and #497 and preparation for feature request #74).
- Order of command settings refined, <CommandLines> again before <DefaultRadix>.
- Name of 3rd party auxiliary subdirectories no longer include spaces, e.g. "DejaVu.Info" rather
than "DejaVu Info" (preparing upcoming feature #74 [Scripting]).
- Name of "YAT.Windows.Forms.dll" corrected to "YAT.SystemEx.Windows.Forms.dll" (regression of
YAT 2.7.2 assembly naming cleanup).
Fixed bugs:
- Reliability of clearing terminal content (bug #561; related to feature request #514 above).
- Missing terminal content refresh after [Automatic Action > Clear Monitor] (bug #592).
- Log files are no longer split at TCP/IP connection loss (bug #593; regression of YAT 2.7.0
changes related to feature request #487).
- Text terminals: Exotic EOL sequences fixed for multi-byte little-endian encodings; test coverage.
- Potential "IOException" while logging to a no longer available location is handled now (bug #601).
Log error handling improved. Log error test coverage improved. Log settings handling fixed.
- Font check related "InvalidOperationException" fixed (bug #606) and font handling refined.
- "ArgumentException" in "FormatSettings.PresetCustomColors()" fixed (bug #602; regression of
YAT 2.7.0 related to feature request #349).
- System error messages and standard message box buttons are again in English (regression of
YAT 2.7.0 analyzer migration and related to previously fixed bug #66).
- Command line examples fixed (bug #607) and refined.
Limitations and known issues:
- General limitations of .NET Framework:
> Unicode is limited to the basic multilingual plane (U+0000..U+FFFF) (feature request #329).
- General serial port limitations:
> Using high baud rates, e.g. 1 MBaud, without flow control, likely results in occasional loss
of data due to buffer overruns (related to fix of bug #572).
- The "\!(PortSettings())" keyword is yet limited to serial ports (feature request #71).
- Sending immediately does not yet support special formats and commands (feature request #10).
- Automatic actions [Filter] and [Suppress] as well as automatic actions and responses based on a
text trigger are constrained to handle complete lines. Thus, individual characters incl. control
characters like <XOn> as well as incomplete lines will not be displayed until line is complete.
- After having large amount of data transmitted, changing settings including e.g. switching log off
may take several seconds, during which YAT is unresponsive (bug #459). Workaround: Clear monitor
[Ctrl+L] or [Ctrl+E] before changing settings.
Additional limitations and known issues on Windows:
- General limitations of .NET Windows.Forms:
> Main window status bar tooltips may flicker in case window is maximized (bug #488).
> Tool strip combo box slightly flickers when updating item list, e.g. [Find Pattern] (bug #402).
> Combo box cannot restore some corner-case cursor positions (bug #403).
> Combo box text is compared case insensitively against item list, e.g. "aa" is changed to "AA"
if that is contained in the item list, e.g. the recent [Send Text] or [Find] items (bug #347).
> Combo box of [Send File] does not have the same color as a button (related to fix of bug #308).
> When text is selected, drop down of recent [Send Text] immediately closes again (bug #584).
> When filling-in [Alt Gr] modified characters, access key underlining may remain (bug #553).
> When [Send Text] or [Send File] is hidden, resizing the panel doesn't properly work (bug #412).
> Automatic completion for e.g. [Send Text] is not feasible to implement (feature request #227).
> Automatic horizontal scrolling of monitors is not feasible to implement (feature request #163).
> Vertical scrolling of monitors while a lot of data is being transmitted and while items are
selected may lead to a severe drop of the overall performance (related to bug #383).
> Link label text rendering issues after plotting (bug #485).
> 150% or greater primary screen scale doesn't properly work with dialogs only resizable in one
dimension. The [New Terminal], [Terminal Settings], [Predefined Commands], [Log Settings],
[Command Line Help] and [Release Notes] dialogs are no longer fixed in height or width,
i.e. can again be resized in both dimensions (bug #583). Issue reported to Microsoft.
- MDI limitations of .NET Windows.Forms:
> Issues with frame (bugs #29 and #30).
> Issue with window list (bug #31).
> Issues with layouting when closing a terminal (bug #399) or resizing main (bug #513).
- Serial port limitations of .NET Framework:
> Support for ports named other than "COM..." isn't supported by .NET (feature request #101).
> Use of serial ports on disconnect, undock or hibernate without closing the port may result in
port no longer usable. It happens due to bugs in the .NET "SerialPort" for which Microsoft
seems to have no plans fixing. YAT applies several patches to circumvent the issues, some of
them require [Terminal > Settings... > ...monitor the port...] being active. If the issue still
is observed, refrain from disconnecting a device or undocking or hibernating while a port is
open. In case the issue occurs, exiting YAT should be sufficient to force the .NET Runtime to
terminate the buggy pieces of code. If not, reconnecting the device should fix the issue.
- Limitations of Visual Studio Installer Projects 2022:
> While the YAT SVN repository now preserves the time stamps of 3rd party, resources and
documentation files, the installer will reset the time stamps to the build time (bug #515).
> The installer now requires that all file types have a command assigned (bug #582).
Additional limitations and known issues on Linux:
- Availability yet limited to .deb and .rpm binary packages. Linux distribution upstreaming yet
pending (feature request #510); same with flatpak (feature req. #507) and AppImage (feat. #511).
- YAT MIME type icon associations may not work (bug #611).
- System-wide named mutex based synchronization among instances of YAT not working yet (bug #612).
- General limitations of Mono (bug #599):
> App.config tag "DpiAwareness" is not supported.
> [Help > Content...] misses content within ASCII table for mono-develop restrictions.
> [Plot > Interaction Help...] is not available for mono-develop restrictions on .resx resources.
> Serial port break state handling may be limited or even not supported.
- Limitations of Mono Windows.Forms (bug #600):
> "Could not set X locale modifiers" (Mono issue https://github.com/mono/mono/issues/18238).
> Occasional X11 "BadWindow" error (Mono issue https://github.com/mono/mono/issues/20726).
> Mono tends to "forget" painting controls. Hovering the mouse should repaint them.
> The area around menu strip combo boxes is not painted with the theme's background color.
> Some editable text not well aligned. Descenders (e.g. lower part of "g") may be cropped.
> MDI limitations with more than one terminal:
> Tool bar may not get refreshed on switching terminal.
> Menu items may not get refreshed on switching terminal.
> Caption may not get refreshed on e.g. I/O changed events.
> Key shortcuts may be processed by the first rather than the active terminal.
> [Tab] navigation among [Send] controls may be disordered, and even get stuck.
> [Multi-Line Text] dialog occasionally cannot be closed. [Tab] navigation or [Cancel] will work.
> On certain themes, e.g. Ubuntu 24 (GNOME 46), standard message box buttons may show no text
(WineHQ bug https://bugs.winehq.org/show_bug.cgi?id=59570).
> Various other issues and suboptimalities on layouting forms and controls.
Where possible, workarounds are in place.
- Limitations of Wine:
> Only binaries can be used; installer fails with "VSDCA_VsdLaunchConditions".
- Limitations of WSL 2:
> "WSL 2 does not include support for accessing serial ports."
(https://learn.microsoft.com/en-us/windows/wsl/compare-versions#exceptions-for-using-wsl-1-rather-than-wsl-2)
- Limitations of YAT:
> USB Ser/HID is not yet supported; use of "LibUsb"/"LibUsbDotNet" and significant work on
implementation and test environment would be needed (feature request #119).
> Preserving the time stamps of 3rd party, resources and documentation files is not implemented.
> Potential "gio: file://... Error retrieving information for file ..." when starting a process.
YAT 2.7.2 :: 2024-08-09
----------------------------------------------------------------------------------------------------
Important changes:
- Upgrade to NUnit 3.14.0 and the TestCentric 1.6.4 GUI runner (feature request #293).
- Various cleanup: NUnit (FR #145), .NET 4+ (FRs #128, #229), assembly naming, field naming,...
- Major steps towards availability on Mono/Linux (parts of feature requests #381 and #401).
- Assemblies again prefer 64-bit rather then 32-bit execution (regression of YAT 2.5.0).
- Use of \todo, \fixme,... tags again unified in source code.
Fixed bugs:
- Non-100% screen scale issue with [Terminal > Settings... > Text... > Exclusion] fixed (bug #589).
- Serial COM port: Handling RTS/DTR pin presets in [Terminal > Settings...] fixed (bug #590).
- Serial COM port, USB Ser/HID: Potential Tx delay after XOn eliminated (regression of YAT 2.7.0).
Limitations and known issues:
- Same as previous release, see below.
YAT 2.7.1 :: 2024-03-08
----------------------------------------------------------------------------------------------------
New:
- Additional options to format CRC (add-on to feature request #300).
Important changes:
- [Help > Command Line Help...] added (related to fix of bug #587).
Fixed bugs:
- Non-100% primary screen scale issue with [File > New Terminal...] dialog fixed (bug #583).
- 225% or greater screen scale "ArgumentOutOfRangeException" for multiple dialogs fixed (bug #586).
- The /tf command line option now supports file path relative to the current directory (bug #587).
- Serial COM port: Legacy settings like 150/7/E/0 or 150/7/E/1.5 not supported by a serial port
device again result in an error message, rather than trying to reopen the port (bug #585).
Limitations and known issues:
- Same as previous release, see further below. In addition:
- General limitations of .NET Windows.Forms:
> 150% or greater primary screen scale doesn't properly work with dialogs only resizable in one
dimension. The [New Terminal], [Terminal Settings], [Predefined Commands], [Log Settings],
[Command Line Help] and [Release Notes] dialogs are no longer fixed in height or width,
i.e. can again be resized in both dimensions (bug #583). Issue reported to Microsoft.
> When text is selected, drop down of recent [Send Text] immediately closes again (bug #584).
YAT 2.7.0 :: 2024-02-16
----------------------------------------------------------------------------------------------------
New:
- Option to append CRC on sending. Behavior and CRC can be configured, e.g. CRC-16/Modbus, and new
keywords "\!(CRC)" and "\!(NoCRC)" added for sending (feature request #300).
- New [File] menu entries to open folder where workspace or terminal file resides (feat. req. #478).
- [File > Preferences...] now allows selecting how the format is handled on copying monitor content.
Enables copying plain text even if formatting is enabled (bug #574, related to former feat. #346).
- [View > Format...] now indicates "formatting per element type" and allows setting the font color
and style when formatting per element type is disabled (bug #573).
- [View > Format...] now provides a few predefined themes (feature request #349) and the means to
define custom themes. [File > New Terminal...] now applies the most recently used theme and font
to newly created terminals (related to feature request #349).
- New keywords "\!(Stop)", "\!(Close)" and "\!(Exit)" added (feature request #483).
- Serial COM port: Half duplex modem handshake added (feature request #485).
- Log files can now optionally be placed and/or named by terminal name and/or I/O device; useful
when simultaneously logging multiple terminals (feature request #487).
Important changes:
- Performance on numeric radices improved (related to feature request #300).
- Performance on copying formatted monitor content improved (related to bugs #573, #574, #575).
- Serial COM port transmission test coverage significantly improved (feat. #263, rel. to bug #572).
- Serial COM port throughput improved, especially for higher baud rates (related to bug #572).
The two above stated improvements have revealed that it is no longer necessary to limit serial COM
port buffering by the [Terminal > Settings... > Advanced... > Buffer...] settings by default, i.e.
these settings are disabled by default now. Additional settings related to buffers and time-out
provide additional means to work around limitations of the .NET Framework's implementation of
serial COM ports and certain COM port devices.
- Serial COM port: Hardware control signal state can now be preset in terminal setting dialog.
- Serial COM port: RS-485 test coverage increased (related to feature request #485).
- Serial COM port and USB Ser/HID: Software flow control handling further improved (feat. #481).
- TCP/IP and UDP/IP: IPNetwork upgraded to 2.6 (feature request #469).
- Source code analysis (FxCop, StyleCop,...) migrated from classic tool-based approach to latest
build integrated analyzers (feature request #231, incl. feature requests #267 and #268).
Fixed bugs:
- Multi-line [Send Text] now respects a trailing empty line.
- [Send Text] again retains cursor position and selection when moving mouse to main menu, toolbar
or status bar (bug #566; regression of YAT 2.6.0, related to fix of bug #554).
- [Predefined] panel no longer gets cropped when [Hide Undefined Commands] is active (bug #569).
- [Predefined > Hide Undefined Commands] is no longer reset when changing layout (rel. to bug #569).
- Predefined page navigation is now fully visible also with scaling other than 100 % (bug #568).
- [File > Preferences... > ...ask whether to switch to another port] again includes the serial COM
port previously active, again enabling use cases where one or multiple devices alternately use the
same serial COM port number (feature request #473 follow-up related regression of YAT 2.6.1).
- Serial COM port XOff state no longer results in lost data (bug #572; regression of YAT 2.6.0).
- Running for days no longer results in an "OverflowException" of the byte/line counters (bug #576).
- Attempt to fix potential "InvalidOperationException" when running a TCP/IP server heavily
connecting and disconnecting clients for hours (bug #567).
- [Break lines after time-out] no longer results in a "NotSupportedException" (bug #570, regression
of YAT 2.6.0 improvements in handling leading hidden data like e.g. an initial <XOn>).
- On copying monitor content, warning messages at the end of a line no longer appear at the
beginning of a line (bug #575).
- Custom colors in [View > Format...] are instantly stored in user settings (related to feat. #349).
Limitations and known issues:
- General limitations of .NET Framework:
> Unicode is limited to the basic multilingual plane (U+0000..U+FFFF) (feature request #329).
- General limitations of .NET Windows.Forms:
> Main window status bar tooltips may flicker in case window is maximized (bug #488).
> Tool strip combo box slightly flickers when updating item list, e.g. [Find Pattern] (bug #402).
> Combo box cannot restore some corner-case cursor positions (bug #403).
> Combo box text is compared case insensitively against item list, e.g. "aa" is changed to "AA"
if that is contained in the item list, e.g. the recent [Send Text] or [Find] items (bug #347).
> Combo box of [Send File] does not have the same color as a button (related to fix of bug #308).
> When filling-in [Alt Gr] modified characters, access key underlining may remain (bug #553).
> When [Send Text] or [Send File] is hidden, resizing the panel doesn't properly work (bug #412).
> Automatic completion for e.g. [Send Text] is not feasible to implement (feature request #227).
> Automatic horizontal scrolling of monitors is not feasible to implement (feature request #163).
> Vertical scrolling of monitors while a lot of data is being transmitted and while items are
selected may lead to a severe drop of the overall performance (related to bug #383).
> Link label text rendering issues after plotting (bug #485).
- MDI limitations of .NET Windows.Forms:
> Issues with frame (bugs #29 and #30).
> Issue with window list (bug #31).
> Issues with layouting when closing a terminal (bug #399) or resizing main (bug #513).
- Serial COM port limitations of .NET Framework:
> Support for ports named other than "COM..." isn't supported by .NET (feature request #101).
> Use of serial COM ports on disconnect, undock or hibernate without closing the port may result
in port no longer usable. It happens due to bugs in the .NET "SerialPort" for which Microsoft
seems to have no plans fixing. YAT applies several patches to circumvent the issues, some of
them require [Terminal > Settings... > ...monitor the port...] being active. If the issue still
is observed, refrain from disconnecting a device or undocking or hibernating while a port is
open. In case the issue occurs, exiting YAT should be sufficient to force the .NET Runtime to
terminate the buggy pieces of code. If not, reconnecting the device should fix the issue.
- General serial COM port limitations:
> Using high baud rates, e.g. 1 MBaud, without flow control, likely results in occasional loss
of data due to buffer overruns (related to fix of bug #572).
- Limitations of Visual Studio Installer Projects 2022:
> While the YAT SVN repository now preserves the time stamps of 3rd party, resources and
documentation files, the installer will reset the time stamps to the build time (bug #515).
> The installer now requires that all file types have a command assigned (bug #582).
- The "\!(PortSettings())" keyword is yet limited to serial COM ports (feature request #71).
- USB Ser/HID only runs on Windows; use of "LibUsb"/"LibUsbDotNet" and significant migration work of
implementation and test environment would be needed to run it on unixoids (feature request #119).
- Sending immediately does not yet support special formats and commands (feature request #10).
- Automatic actions [Filter] and [Suppress] as well as automatic actions and responses based on a
text trigger are constrained to handle complete lines. Thus, individual characters incl. control
characters like <XOn> as well as incomplete lines will not be displayed until line is complete.
- After having large amount of data transmitted, changing settings including e.g. switching log off
may take several seconds, during which YAT is unresponsive (bug #459). Workaround: Clear monitor
[Ctrl+L] or [Ctrl+E] before changing settings.
YAT 2.6.1 :: 2023-06-25
----------------------------------------------------------------------------------------------------
Important changes:
- [File > Preferences... > ...ask whether to switch to another port] now proposes the next available
COM port, rather than fixed to the first available COM port (follow-up to feature request #473).
Fixed bugs:
- Panel dependent context menu items no longer remain disabled (bug #563; regression of YAT 2.6.0).
- "InvalidOperationException" on [Terminal > Refresh] (bug #579; regression of YAT 2.6.0).
- Layout related minor issues in [View > Format...] dialog fixed (bug #562).
- Explicit default radix selection in [Predefined > File] fixed.
Limitations and known issues:
- Same as previous release, see below.
YAT 2.6.0 :: 2023-06-09
----------------------------------------------------------------------------------------------------
New:
- Possibility to display a changing value on a single line ("steady line" feature) (bug #546).
> Additional automatic action [Overwrite Line on subsequent Rx].
> Text terminals: New option to execute carriage returns when outside EOL, disabled by default.
- Additional keyword "\!(Break)" that breaks sending, same as [Ctrl+B]; useful with e.g. predefined
commands and automatic responses when [concurrent sending] is allowed (feature request #477).
- When a serial COM port gets disconnected, there is a new option to automatically switch to the
next available COM port; and the "\!(Port())" keyword now supports -1 to automatically select the
first available COM port (feature request #473).
- UDP/IP terminals now provide a setting to either optimize for speed or retain datagrams. The
latter is the default setting; each packet requested by the terminal will be sent as an individual
datagram and each datagram received will be shown on an individual line (feature request #472).
Important changes:
- Terminal view improved; frames removed. View may look unfamiliar at first. Improvement allows more
area usable for content; especially noticeable with a workspace containing many terminals.
- [Predefined Commands] panel now shows a vertical scroll bar if required (feature request #474).
- [Predefined Commands] panel no longer shows page navigation if only a single page (rel. to #474).
- Option to hide menu and toolbar (related to feature request #474).
- Improved speed on copying monitor content onto clipboard if formatting is disabled; clipboard will
only contain unformatted text in this case (feature request #346).
- Handling of keyboard input if not keeping [Text] or for sending immediately improved (related to
fix of bugs #548 and #549).
- [Terminal > All Terminals Open/Start] added.
- TCP/IP server option to limit the number of connections.
- TCP/IP AutoSocket servers are now limited to a single connection by default.
- UDP/IP and TCP/IP terminal I/O status now shows more details on connection end-points.
- Hidden bytes, e.g. initial <XOn>, no longer trigger line begin, e.g. time stamp.
- Serial COM port connection monitor now better covers devices which do not properly handle the
connection state, e.g. Teensy with Microsoft CDC ACM driver (related to feat. #473 and bug #543).
- Additional measures to prevent deadlocked serial COM ports (related to feat. #473 and bug #543).
Fixed bugs:
- [Send > Text*] now validates and respects modified [Text] (bug #544).
- Activating the toolbar no longer resets modified [Text] (bug #510).
- Sending a predefined command no longer resets modified [Text] (bug #549).
- Predefined command shortcut [Shift+F3] fixed (bug #548; regression of fix of bug #534).
- Change of terminal status no longer resets modified [Text] (related to fix of bugs #548 and #549).
- Text terminals: When software flow control is active, <XOn>/<XOff> no longer have an impact on
EOL even if EOL is not shown (follow-up of fix of bug #538).
- Serial COM port send rate limitation fixed and improved (bug #557; regression of YAT 2.4.0).
- Double-clicking a file in a dialog no longer triggers the underneath single-click action in the
main menu, toolbar or status bar (bug #554, related to fix of former bug #210).
- Control char related labels in settings dialogs no longer use terminal back color (bug #547).
- "NullReferenceException" on switching from TCP/IP to serial COM port fixed (bugs #550 and #555).
- Mouse wheel scrolling of combo boxes fixed (bug #558).
Limitations and known issues:
- General limitations of .NET Framework:
> Unicode is limited to the basic multilingual plane (U+0000..U+FFFF) (feature request #329).
- General limitations of .NET Windows.Forms:
> Main window status bar tooltips may flicker in case window is maximized (bug #488).
> Tool strip combo box slightly flickers when updating item list, e.g. [Find Pattern] (bug #402).
> Combo box cannot restore some corner-case cursor positions (bug #403).
> Combo box text is compared case insensitively against item list, e.g. "aa" is changed to "AA"
if that is contained in the item list, e.g. the recent [Send Text] or [Find] items (bug #347).
> Combo box of [Send File] does not have the same color as a button (related to fix of bug #308).
> When filling-in [Alt Gr] modified characters, access key underlining may remain (bug #553).
> When [Send Text] or [Send File] is hidden, resizing the panel doesn't properly work (bug #412).
> Automatic completion for e.g. [Send Text] is not feasible to implement (feature request #227).
> Automatic horizontal scrolling of monitors is not feasible to implement (feature request #163).
> Vertical scrolling of monitors while a lot of data is being transmitted and while items are
selected may lead to a severe drop of the overall performance (related to bug #383).
> Link label text rendering issues after plotting (bug #485).
- MDI limitations of .NET Windows.Forms:
> Issues with frame (bugs #29 and #30).
> Issue with window list (bug #31).
> Issues with layouting when closing a terminal (bug #399) or resizing main (bug #513).
- Serial COM port limitations of .NET Framework:
> Support for ports named other than "COM..." isn't supported by .NET (feature request #101).
> Use of serial COM ports on disconnect, undock or hibernate without closing the port may result
in port no longer usable. It happens due to bugs in the .NET "SerialPort" for which Microsoft
seems to have no plans fixing. YAT applies several patches to circumvent the issues, some of
them require [Terminal > Settings... > ...monitor the port...] being active. If the issue still
is observed, refrain from disconnecting a device or undocking or hibernating while a port is
open. In case the issue occurs, exiting YAT should be sufficient to force the .NET Runtime to
terminate the buggy pieces of code. If not, reconnecting the device should fix the issue.
- Limitation of Visual Studio Installer Projects 2022:
> While the YAT SVN repository now preserves the time stamps of 3rd party, resources and
documentation files, the installer will reset the time stamps to the build time (bug #515).
- The "\!(PortSettings())" keyword is yet limited to serial COM ports (feature request #71).
- USB Ser/HID only runs on Windows; use of "LibUsb"/"LibUsbDotNet" and significant migration work of
implementation and test environment would be needed to run it on unixoids (feature request #119).
- Sending immediately does not yet support special formats and commands (feature request #10).
- Automatic actions [Filter] and [Suppress] as well as automatic actions and responses based on a
text trigger are constrained to handle complete lines. Thus, individual characters incl. control
characters like <XOn> as well as incomplete lines will not be displayed until line is complete.
- After having large amount of data transmitted, changing settings including e.g. switching log off
may take several seconds, during which YAT is unresponsive (bug #459). Workaround: Clear monitor
[Ctrl+L] or [Ctrl+E] before changing settings.
YAT 2.5.0 :: 2022-12-12
----------------------------------------------------------------------------------------------------
New:
- Text terminals: Additional options to...
...configure treatment of extended ASCII characters 0x80..FF (feature request #448).
...hide or replace control and/or extended ASCII characters by a placeholder (feature req. #459).
...hide <CR> and/or <LF> outside EOL. Useful with mixed EOL, e.g. devices with <CRLF> and <LFCR>.
In such case, EOL can now be set to <LF> while <CR> can be hidden (feat. req. #449, bug #521).
- Option to show the time delta among selected monitor lines.
- Additional keywords "\!(LogOn|Off|Toggle)" allow to change logging on-the-fly (feat. req. #446).
- Additional option to enclose separated content, e.g. "[58h]" for "58h". (feat. req. #447).
- Additional automatic actions [Filter Content] and [Suppress Content] (related to bug #521),
enabling filtering/suppressing e.g. ANSI escape sequences (predefined regular expression added).
- Binary terminals: Byte send delay added (related to analysis of bug #528).
- IP networking: DNS preference for IPv6 added to [File > Preferences...] (related to bug #529).
- Script to convert Docklight settings files (.ptp) to YAT (.yat) (feature request #429),
available at https://sourceforge.net/p/y-a-terminal/code/HEAD/tree/trunk/YATTools/Settings/.
Important changes:
- ASCII related settings moved from [Terminal > Settings... > Advanced...] to
[Terminal > Settings... > Text...] (related to feature requests #448, #449, #459 and bug #521).
- ASCII control characters now also use the control format in Bin/Oct/Dec/Hex radix. This enables
coloring them differently than non-control characters also in Bin/Oct/Dec/Hex radix.
- ASCII control character replacement setting [Character] migrated to [Symbol Character] resulting
in displaying as Unicode symbols U+2400..241F as well as U+2421 (bug #517, feature request #34).
- ASCII control character treatment (display/execute/replace/hide) test coverage improved.
- Text terminals: Encoding related improvements (ordering, ASCII compatibility).
- Binary terminals: Now by default using .NET's [Encoding.Default] that corresponds to the system's
default ANSI code page, e.g. Windows-1252 in Western Europe, for parsing of [Send Text|File].
- Serial COM ports and USB Ser/HID: XOn/XOff counts are now preserved when changing settings.
- Serial COM ports: Control pin and break counts are now preserved when changing settings.
- Accuracy of time stamps on sending improved for all I/O types (bug #514) and
accuracy of time stamps on receiving improved for UDP/IP sockets (feature request #442).
- UDP/IP server now supports filtering with CIDR or wildcard notation (related to bug #495,
implemented using IPNetwork).
- Tooltips of send buttons no longer show unlimited large data (bug #535).
- Send buttons again show the file path (leftover of bug #308, feature request #458).
- [Send Text|File] buttons now toggle to [Break Sending] while sending of e.g. files or repeating
commands is ongoing (feature request #445).
- Automatic actions [Highlight], [Filter] and [Suppress] renamed to [... Line] for obviousness and
distinction with newly added [Filter Content] and [Suppress Content] (related to bug #521).
- Option to immediately start logging when creating a new terminal (related to bug #539).
- Major settings dialogs now indicate the corresponding main menu icon.
- Terminal specific settings dialogs now indicate the terminal name (related to bug #539).
- System error messages and standard message box buttons in English rather than locale (bug #66).
- Upgrade to Visual Studio 2022 (feature request #441).
- Build details refined (feature request #437):
> The build ID now represents the SVN revision and thus is an incremental value across versions.
> Visual Studio projects switched to deterministic builds, enabling identical compilation output
across multiple builds for identical inputs.
- App.config file time stamps now reflect the build time of the binaries (bug #515).
- 3rd party use of YAT assemblies, e.g. with PowerShell or CS-Script, product name and version now
reflect the YAT name and version rather than the 3rd party executable's. Especially applies to
name and version stated when writing settings files (related to feature request #429).
Fixed bugs:
- [Send Text] shortcuts [F3] and [Ctrl+F3] now reflect modified text (bug #534).
- Scaling problem of [Predefined Commands] panel on non-100 % scaling fixed (bugs #522 and #524).
- Text terminals:
> Wait for response now always resets clearance when terminal is closed/reopened (bug #523).
> Treatment of backspace fixed for UTF-16/32 (related to ASCII control character improvements).
> Handling of adjacent EOL character(s) fixed for UTF-16/32 Big-Endian.
> When software flow control is active, <XOn>/<XOff> no longer have an impact on EOL (bug #538).
- Serial COM port break state handling fixed and improved:
> Output break state count is immediately incremented.
> Input break state immediately gets restored on first chunk received.
> Input break state count should be incremented only once on all ports/hardware.
> Break state is indicated in terminal I/O status.
> Test coverage enhanced.
- IP networking: Use of host name no longer results in "[broadcast] ..." error message (bug #529).
- UDP/IP server filtering now also works on matching address and filter bit masks (bug #495).
- Automatic actions [Filter] and [Suppress] no longer erroneously suppress Tx content (bug #519).
- Double-click on [connect time] or [bytes | lines] again properly resets the counters (bug #533).
- [Terminal > Select All] now happens instantly even with very many lines (bug #461).
- ASCII control character replacement setting [Character] no longer results in a
"TargetInvocationException" (bugs #517 and #521).
- "ArgumentOutOfRangeException" caused by "ComboBoxHelper" fixed.
Limitations and known issues:
- General limitations of .NET Framework:
> Unicode is limited to the basic multilingual plane (U+0000..U+FFFF) (feature request #329).
- General limitations of .NET Windows.Forms:
> Main window status bar tooltips may flicker in case window is maximized (bug #488).
> Tool strip combo box slightly flickers when updating item list, e.g. [Find Pattern] (bug #402).
> Combo box cannot restore some corner-case cursor positions (bug #403).
> Combo box text is compared case insensitively against item list, e.g. "aa" is changed to "AA"
if that is contained in the item list, e.g. the recent [Send Text] or [Find] items (bug #347).
> Combo box of [Send File] does not have the same color as a button (related to fix of bug #308).
> When filling-in [Alt Gr] modified characters, access key underlining may remain (bug #553).
> When [Send Text] or [Send File] is hidden, resizing the panel doesn't properly work (bug #412).
> Automatic completion for e.g. [Send Text] is not feasible to implement (feature request #227).
> Automatic horizontal scrolling of monitors is not feasible to implement (feature request #163).
> Vertical scrolling of monitors while a lot of data is being transmitted and while items are
selected may lead to a severe drop of the overall performance (related to bug #383).
> Link label text rendering issues after plotting (bug #485).
- MDI limitations of .NET Windows.Forms:
> Issues with frame (bugs #29 and #30).
> Issue with window list (bug #31).
> Issues with layouting when closing a terminal (bug #399) or resizing main (bug #513).
- Serial COM port limitations of .NET Framework:
> Support for ports named other than "COM..." isn't supported by .NET (feature request #101).
> Use of serial COM ports on disconnect, undock or hibernate without closing the port may result
in the port no longer being usable. It happens due to a bug in the .NET "SerialPort" class for
which Microsoft seems to have no plans fixing. To prevent the issue, refrain from disconnecting
a device or undocking or hibernating while a port is open. In case the issue occurs, exiting
YAT should be sufficient to force the .NET Runtime to terminate the buggy piece of code.
If not, disconnecting the device or rebooting the computer should fix the issue.
- Limitation of Visual Studio Installer Projects 2022:
> While the YAT SVN repository now preserves the time stamps of 3rd party, resources and
documentation files, the installer will reset the time stamps to the build time (bug #515).
- The "\!(PortSettings())" keyword is yet limited to serial COM ports (feature request #71).
- USB Ser/HID only runs on Windows; use of "LibUsb"/"LibUsbDotNet" and significant migration work of
implementation and test environment would be needed to run it on unixoids (feature request #119).
- Sending immediately does not yet support special formats and commands (feature request #10).
- Automatic actions [Filter] and [Suppress] as well as automatic actions and responses based on a
text trigger are constrained to handle complete lines. Thus, individual characters incl. control
characters like <XOn> as well as incomplete lines will not be displayed until line is complete.
- After having large amount of data transmitted, changing settings including e.g. switching log off
may take several seconds, during which YAT is unresponsive (bug #459). Workaround: Clear monitor
[Ctrl+L] or [Ctrl+E] before changing settings.
YAT 2.4.1 :: 2021-05-15
----------------------------------------------------------------------------------------------------
New:
- Quick reference (PDF) added. Accessible via [Windows > Start > YAT] and [YAT > Help].
- [Find All] added, with shortcut [Alt+Shift+L], incl. live update (feature requests #424 and #434).
Important changes:
- YAT now checks whether the DejaVu monospaced font is available, and whether a monospaced font
is used for the terminals. The user gets warned if either is not given (feature request #341).
- [View > Format... > Font...] now by default only shows monospaced fonts (related to req. #341).
- Parser now supports the non-standard but common C-style "\e".
- Behavior on multi-byte character set decoding mismatch can now be configured in the terminal
settings [Terminal > Settings... > Text...] (feature request #436).
- Separate colors for warnings and errors (related to feature request #436). On existing terminals,
separate colors will have to be explicitly activated by [View > Format... > Defaults...].
- Find text can now automatically be set by either selecting a line in a monitor or by selecting the
whole or parts of a line in [Copy of Active Line] (related to feature requests #424 and #434).
- Log dialog now more clearly states "root directory and file name base" (part of feat. req. #435).
- Help window can again be sized to display more/all content (related to earlier feature req. #237).
- Command line argument errors are better reported now (bug #503).
- Builds reverted from [x64] to [Any CPU] for providing compatibility with MSIL projects that make
direct use of YAT/MKY/OxyPlot/RtfWriter/ALAZ assemblies (bug #507, related to recent upgrade to
.NET Runtime 4 and .NET Framework 4.8 (feature request #229)).
Fixed bugs:
- Handling of missing log file folder fixed.
- Issues when backspace was preceded by space(s) fixed.
- [broadcast] recently selected for UDP/IP remote host is no longer listed for TCP/IP (bug #508).
- Handling of trigger of automatic actions and responses fixed and improved (bugs #504 and #505).
- Plotting no longer takes time stamp and other meta info into account (bug #509). The option will
again become available in a dedicated action/response configuration dialog (future feature #431).
- Plot window related "NullReferenceException" when closing YAT fixed.
Limitations and known issues:
- General limitations of .NET Framework:
> Unicode is limited to the basic multilingual plane (U+0000..U+FFFF) (feature request #329).
- General limitations of .NET Windows.Forms:
> System error messages are output in local language, even though YAT is all-English (bug #66).
> Main window status bar tooltips may flicker in case window is maximized (bug #488).
> Tool strip combo box slightly flickers when updating item list, e.g. [Find Pattern] (bug #402).
> Combo box cannot restore some corner-case cursor positions (bug #403).
> Combo box text is compared case insensitively against item list, e.g. "aa" is changed to "AA"
if that is contained in the item list, e.g. the recent [Send Text] or [Find] items (bug #347).
> When [Send Text] or [Send File] is hidden, resizing the panel doesn't properly work (bug #412).
> Automatic completion for e.g. [Send Text] is not feasible to implement (feature request #227).
> Automatic horizontal scrolling of monitors is not feasible to implement (feature request #163).
> Vertical scrolling of monitors while a lot of data is being transmitted and while items are
selected may lead to a severe drop of the overall performance (related to bug #383).
> Link label text rendering issues after plotting (bug #485).
- MDI limitations of .NET Windows.Forms:
> Issues with frame (bugs #29 and #30).
> Issue with window list (bug #31).
> Issues with layouting when closing a terminal (bug #399) or resizing main (bug #513).
- Serial COM port limitations of .NET Framework:
> Support for ports named other than "COM..." isn't supported by .NET (feature request #101).
> Use of serial COM ports on disconnect, undock or hibernate without closing the port may result
in the port no longer being usable. It happens due to a bug in the .NET "SerialPort" class for
which Microsoft seems to have no plans fixing. To prevent the issue, refrain from disconnecting
a device or undocking or hibernating while a port is open. In case the issue occurs, exiting
YAT should be sufficient to force the .NET Runtime to terminate the buggy piece of code.
If not, disconnecting the device or rebooting the computer should fix the issue.
- The "\!(PortSettings())" keyword is yet limited to serial COM ports (feature request #71).
- USB Ser/HID only runs on Windows; use of "LibUsb"/"LibUsbDotNet" and significant migration work of
implementation and test environment would be needed to run it on unixoids (feature request #119).
- Sending immediately does not yet support special formats and commands (feature request #10).
- Automatic actions [Filter] and [Suppress] as well as automatic actions and responses based on a
text trigger are constrained to handle complete lines. Thus, individual characters incl. control
characters like <XOn> as well as incomplete lines will not be displayed until line is complete.
- After having large amount of data transmitted, changing settings including e.g. switching log off
may take several seconds, during which YAT is unresponsive (bug #459). Workaround: Clear monitor
[Ctrl+L] or [Ctrl+E] before changing settings.
Content of the below historical versions has been removed in order to compact this file such it fits
the SourceForge limitation of 64 KiB for the online readme / release notes.
----------------------------------------------------------------------------------------------------
YAT 2.4.0 :: 2021-01-29
(Versions 2.2 and 2.3 have initially been skipped to emphasize the update to .NET 4.x and keeping
the option for releasing 2.4+ features (except plotting) also on .NET Runtime 2.0 / Framework 3.5.)
YAT 2.2.0 :: 2025-03-27 :: YAT 2.1.0 with selected YAT 2.4.0+ backports for .NET 3.5 SP1
YAT 2.1.0 :: 2019-10-04
YAT 2.0.0 :: 2018-04-13 :: YAT 2.0 Final
YAT 1.99.90 :: 2018-01-12 :: YAT 2.0 Epsilon
YAT 1.99.80 :: 2017-10-15 :: YAT 2.0 Delta
YAT 1.99.70 :: 2017-07-04 :: YAT 2.0 Gamma 3
YAT 1.99.52 :: 2016-09-30 :: YAT 2.0 Gamma 2''
YAT 1.99.51 :: 2016-09-17 :: YAT 2.0 Gamma 2'
YAT 1.99.50 :: 2016-09-16 :: YAT 2.0 Gamma 2
YAT 1.99.34 :: 2015-06-13 :: YAT 2.0 Gamma 1''
YAT 1.99.33 :: 2015-06-07 :: YAT 2.0 Gamma 1'
YAT 1.99.32 :: 2015-06-01 :: YAT 2.0 Gamma 1
YAT 1.99.30 :: 2013-02-02 :: YAT 2.0 Beta 4 Candidate 2
YAT 1.99.28 :: 2011-12-05 :: YAT 2.0 Beta 4 Candidate 1
YAT 1.99.26 :: 2011-04-25 :: YAT 2.0 Beta 3 Candidate 4
YAT 1.99.25 :: 2010-11-28 :: YAT 2.0 Beta 3 Candidate 3
YAT 1.99.24 :: 2010-11-11 :: YAT 2.0 Beta 3 Candidate 2
YAT 1.99.23 :: 2009-09-10 :: YAT 2.0 Beta 3 Candidate 1
YAT 1.99.20 :: 2008-07-18 :: YAT 2.0 Beta 2 Candidate 4
YAT 1.99.19 :: 2008-04-01 :: YAT 2.0 Beta 2 Candidate 3
YAT 1.99.18 :: 2008-03-17 :: YAT 2.0 Beta 2 Candidate 2
YAT 1.99.17 :: 2008-02-11 :: YAT 2.0 Beta 2 Candidate 1
YAT 1.99.13 :: 2007-08-30 :: YAT 2.0 Beta 2 Preliminary
YAT 1.99.12 :: 2007-04-15 :: YAT 2.0 Beta 1
YAT 1.99.8 :: 2007-02-25 :: YAT 2.0 Alpha 3
YAT 1.99.3 :: 2007-02-07 :: YAT 2.0 Alpha 2
YAT 1.99.0 :: 2007-01-23 :: YAT 2.0 Alpha 1
====================================================================================================
F. History of Changes in XTerm232
====================================================================================================
XTerm232 1.0.2 :: 2003-10-31
XTerm232 1.0.1 :: 2003-10-30
XTerm232 1.0.0 :: 2003-10-14
Content of the above historical versions has been removed in order to compact this file such it fits
the SourceForge limitation of 64 KiB for the online release notes.
====================================================================================================
F. Roadmap
====================================================================================================
YAT 2
----------------------------------------------------------------------------------------------------
YAT 2 is in maintenance mode now, i.e. focus on bug fixes and minor changes, while work for YAT 4
is already ongoing.
(Version 3 will be skipped to prevent naming conflict with yat3 of Dieter Fauth that became
public around the same time as YAT. And, 4.0 buzzes more anyway (industry 4.0 and the like ;-))
----------------------------------------------------------------------------------------------------
YAT 4 with scripting (feature requests #74 and #82) :: Expected in 2026..2027
----------------------------------------------------------------------------------------------------
YAT 4.0 will feature the integration of a scripting environment, based on the CSScript engine.
Scripting will allow running scripts in YAT to automate repetitive tasks, for test automation,
implement protocol layers,... whatever one can think of. Examples and templates will be included.
It is also planned to demonstrate how to use YAT from a PowerShell script and along with NUnit.
All these features aim for providing a versatile automatic testing tool for serial communications.
====================================================================================================
G. Source Code Build
====================================================================================================
1. Get the Subversion checkout of the desired "svn://svn.code.sf.net/p/y-a-terminal/code/tags",
or main line "svn://svn.code.sf.net/p/y-a-terminal/code/trunk".
Linux
----------------------------------------------------------------------------------------------------
2. Install "mono-devel" according to https://www.mono-project.com/download/stable/.
3. Navigate to "YAT/".
4. Build e.g. `msbuild YAT.sln -t:Rebuild -p:Configuration='Release Mono' -p:Platform='Any CPU' -noWarn:'AD0001;CS1574;CS1591' -m`.
5. Run e.g. `mono 'YATApp/YAT#Mono/bin/Release Mono/yat.exe'`.
Windows
----------------------------------------------------------------------------------------------------
2. Install "Visual Studio" from https://visualstudio.microsoft.com/, e.g. free "Community" edition.
3. Open "YAT\YAT.sln".
4. Set [YAT] as [Startup Project].
5. Build and run any of the non-Mono [Debug] or [Release] configurations.
====================================================================================================
H. Package Build
====================================================================================================
Linux .deb (Debian, Ubuntu,...)
----------------------------------------------------------------------------------------------------
6. Optionally, install "lintian".
7. Navigate to "YAT/YATPkg/".
8. Run `bash ./MakeLinuxPackage.deb.bash` to create package based on available artifacts.
Run `bash ./MakeLinuxPackage.deb.bash --build --lint` to include building and linting.
Linux .rpm (Red Hat, SUSE, Fedora,...)
----------------------------------------------------------------------------------------------------
6. Optionally, install "rpmdevtools" and "rpmlint".
7. Navigate to "YAT/YATPkg/".
8. Run `bash ./MakeLinuxPackage.rpm.bash` to create package based on available artifacts.
See explanations in `./MakeLinuxPackage.rpm.bash` for workaround to get artifacts.
Windows
----------------------------------------------------------------------------------------------------
6. Install "Visual Studio Installer Projects".
7. Navigate to "YAT\YATPkg\Windows\".
8. Open and build "YAT.Setup.*.vdproj".
====================================================================================================
I. Legal
====================================================================================================
Copyright © 2003-2004 HSR Hochschule für Technik Rapperswil (now OST - Ostschweizer Fachhochschule).
Copyright © 2003-2026 Matthias Kläy.
All rights reserved.
YAT is licensed under the GNU LGPL-2.1.
See https://www.gnu.org/licenses/old-licenses/lgpl-2.1.html for license terms.
****************************************************************************************************
End of YAT Release Notes
****************************************************************************************************
Download Latest Version
YAT-2.8.0_x64_(64-bit).msi (5.5 MB)
