Activity for Rick Murphy
-
Rick Murphy posted a comment on discussion Help
Yup - ARRL prematurely updated their site. The assumption made by the update check is that they're only publishing final releases. That triggers this loop. This should be fixed now.
-
Reviewed the changes and all look good. Thanks for the updates and corrections.
-
Support for 64-bit Windows builds and up to Visual Studio 2022
-
Fix the GoogleTest suite and issues with wide-strings on Windows
-
Merged. All looks good.
-
This should already have been merged with later requests.
-
Allow CMake to auto-detect the best value for arch on Mac OS.
-
Compilation fixes, build improvements, and support for VS 2012+
-
Initial test suite for libtqsllib
-
Thanks for this - while I do a lot of scripted testing at the UI level, more testing at the APIs is definitely needed.
-
Task Manager implies that you're using Windows, but perhaps not. If TQSL is opening and appearing in the taskbar, but does not appear on your screen, then it's probably showing up off-screen, which usually happens when you run it displaying on a second monitor then remove that monitor - Windows happily allows a window to open where you can't see it. Use one of the results of "windows 10 move window from off screen" (or Windows 7, 11, whatever) to move the TQSL window back into view. Alternatively,...
-
This SHOULD be fixed now - I provided the wrong update files to ARRL so the update kept trying to install the "new" release but still getting the prerelease. Grabbing the kits from my website would also have worked - including the Apple Silicon/x86_64 installer. (https:/www.rickmurphy.net/lotw/tqsl-arm64-2.6.5.pkg )
-
No, as TQSL stores all of the user data in a directory off of your home directory. Uninstalling the program doesn't remove any of your data. (sorry, I missed the question here about where your certificates are stored.)
-
No, as TQSL stores all of the user data in a directory off of your home directory. Uninstalling the program doesn't remove any of your data.
-
The TQSL installer package is going to install TQSL into /Applications/TrustedQSL If you've previously installed TQSL somewhere else, then you're probably still running that older version from somewhere else. Remove that old copy and run it from the "standard" directory.
-
Fix spelling errors
-
The 'nework' errors are in a localized message so that will require updating the message files (both .po and .mo). I'll merge that change in with the fix for the jsonval.cpp change ('obejct'). I found the "unknow escaped character" there as well. Thanks!
-
The 'nework' errors are in a localized message so that will require updating the message files (both .po and .mo). I'll merge that change in with the fix for the jsonval.cpp change ('obejct'). Where are you seeing the "Unknow escaped character"?
-
Clean build: Install from homebrew cmake, openssl, lmdb, and wxWidgets Then: rm CMakeCache.txt export OPENSSL_ROOT_DIR=/opt/homebrew/opt/openssl cmake -DOSX_ARCH=arm64 . make
-
I have not built for Apple Silicon, but that's mostly inertia on my part. I greatly dislike leaving 32-bit Macs behind, and any XCode version that allows targeting M1 only allows x86_64 in a "universal" binary. The build scripts in the package assume the legacy system (i386/ppc) and need to be revamped. As TQSL runs fine on M1 macs, I've not been overly motivated to get it onto Apple Silicon.
-
Just to close this out - the help and localization issues were both due to absolute directory references (root-relative /usr/share/...). Fortunately, this is only defined in one place so it was easy to fix.
-
Apparently the help doesn't work either - which is probably the same problem.
-
Apparently the help doesn't work either - which is probably the same problem.
-
Wow - this was something I was completely unaware of. I've built an AppImage, available from https://www.rickmurphy.net/lotw/TQSL-x86_64.Appimage which seems a pretty straightforward addition to my packaging scripts. Seems to handle command line arguments correctly, and generally works. The only issue I see (which is very likely a packaging problem, not an AppImage problem) is that the language selection dialog doesn't work. I'll investigate. I'm going to test this on a few distributions, but if...
-
Fix empty RunWizard on Cancel in load certificate
-
Thanks, Petr - that thread is long and a bit contentious, but it's clear that getting...
-
Finishing the dangling sentence: "all that would happen is that duplicate and changed...
-
Short term, we'll probably stay with BDB 5 as there's nothing in version 6 that's...
-
The documentation states what was used to build TQSL, not specific requirements....
-
The "Certificate signature failure" seems to indicate that the TQ6 file you're trying...
1