Skip to content

v0.4.2

Pre-release
Pre-release
Compare
Choose a tag to compare
@rforzachamp821 rforzachamp821 released this 25 Nov 13:40
· 33 commits to main_ZeeTerminal since this release
v0.4.2
36f8b4d
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

ZeeTerminal v0.4.2. Find release notes, source code and binaries in the .zip OR .7z file.

You can also find the release notes below:

ZeeTerminal v0.4.2 Release Notes

New Features

  • The MemoryTestEngine (used by the MemTest command) now supports multithreading! This may accelerate the memory tests up to 2x faster, in the expense of CPU heat. You can choose between single and multi-threaded testing when you open the MemTest command, where there are 8 options instead of 4 now. Multithreading also allows for a better fit to implement a progress meter, which is now included in all linear memory tests.

Changes and Bugfixes

  • Added a new syntax! There is now a new string argument format, which involves a 2-dash identifier (--). This new string syntax addition is for options only. The previous string syntax (that uses only spaces to identify) is now repurposed into a data-storing syntax, which stores option parameters and/or data for commands directly. Each command may use them differently, so check on each command's help page ( -h) to get usage information. All commands have been modified to meet this spec.
  • Fixed a bug where on first ZeeTerminal startup, all the introduction text would flash on Windows 11 and Windows Terminal systems and not just the 'Welcome to ZeeTerminal' text.
  • Changed the wording of the title text of some parts of the MemTest command.
  • Improved input validation across all integer and floating-point types.
  • Improved string-to-integer integrity validation.
  • Fixed a bug where inputting a negative number in any positive-only input area would result in the end number being incredibly high.
  • Fixed a possible bug where in the CPU stress tests (the CPUStress command), a divide-by-zero operation could occur and result in the program crashing.
  • Added messages that the session is about to be shown in the OptionSelect, ScreenNavigate and TableEngine testers in the DevTools command.
  • Added a 2D 'ZeeTerminal' ASCII art logo in the 'About' page in the Help command, because why not.
  • Added option indicators that use random colours for each option when using the OptionSelect engine. They are located behind each option, and look like this: "~|".
  • Fixed ZeeTerminal crashing on exit (or 'exit' command) when ANSI VT Sequences are disables and Win32 colours are being used.
  • Fixed foreground subheading colour not being checked for validation when reading from configuration file when the ColourTypeSwitch() function is called.
  • Fixed colours being reset after changing the console mode from ANSI to Win32 mode and vice-versa.
  • Fixed random colours on startup not working for people without ANSI VT support.
  • The ANSI VT Sequences setting will now be saved in the configuration file. Previously, it wasn't due to possible issues when transferring settings between different terminals that support the setting and those that don't. Now, a new system has been developed to ignore the setting when the terminal doesn't support ANSI VT escape codes, solving the issue.
  • Fixed an issue where creating an RGB preset within a WIN32 environment and loading it within an ANSI-RGB environment would not be prevented and would cause the colours to look completely different than intended. A message will appear when this is done. This has also been fixed for vice-versa.
  • Fixed an issue where the 'Reset Colours to Default' option wouldn't work in non-ANSI VT Sequence supporting terminals.
  • Made the 'Reset Colours to Default' clear the screen to apply default colours to the whole terminal screen, instead of newer text.
  • In the Custom Config File Directory setting, the "^open" input has been renamed to "*open" to fit in with what all the other commands use.
  • The custom config file setting will now validate any custom configuration files before usage. This may cause the configuration file to get overwritten which is expected behaviour. This has been clarified in the front setting page before the filepath is entered.
  • In the Custom Config File Directory setting, the Windows File Dialogue can now be accessed through the use of arguments.
Assets 4
Loading