Skip to content

Beta 0.1.0.4

Pre-release
Pre-release
Compare
Choose a tag to compare
@quassbutreally quassbutreally released this 27 Oct 08:59
· 39 commits to master since this release
cpdlc0.1.0.4
895f266
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

General:
A relatively small update featuring some requests and some additional functionality in order to help me find and fix the more niggling bugs.

-BUGFIXES:

  • FIXED: User-sent logoff commands not updating the "Current ATC Unit" field (thanks Flurus!)
  • FIXED: CPDLC Messages occasionally getting duplicated if message contained 2 identical fields.

-NEW FEATURES:

  • BASIC LOGGING: EasyCPDLC now keeps a basic log of what it's doing at any given time to help with bugfixing. Because of this, from v0.1.0.4 onwards the program must be run as administrator. The log file is called EasyCPDLCLog.txt and can be uploaded to an issue or sent directly to me at joshseagrave@googlemail.com. The log file contains no personally identifiable information outside of the callsign that is used to connect to and the contents of CPDLC messages.
  • RESIZE: All windows (except the initial login window) can now be resized by clicking and dragging the bottom-right corner of the screen. They can not be made smaller than their original size for scaling and layout reasons but can, in theory, be made as large as they like.
  • UPDATER: EasyCPDLC now ships with an updater that should check for updates on program start, so you know if you're running an outdated version. I have, of course, not really had opportunity to test this, if it doesn't work I'll come up with something else.

-KNOWN ISSUES:

  • If a window is shrunk rapidly there are occasionally some formatting issues with CPDLC messages and scrollbars. This is something I am aware of but haven't worked out how to optimise yet, expect this to be refined and improved in future updates.
  • Some users have reported that they stop receiving CPDLC messages after a short while of being connected. This doesn't appear to be consistent across anyone and I am yet to discover the root cause. Issue #4 is the place to go if you encounter this.

Thankyou all again for your patience and keep the suggestions and bug reports coming! Development is accelerating now as I continue to clean up the codebase towards release standards and further optimise routines and such, every bugfix helps!

Josh

Assets 3
Loading