I beg to differ with Greg's, NC7B, comments on Mac OS X 10.11 (El Capitan).
The OS is only 3 years old, and there is a substantial hardware base that can not upgrade beyond it. I mean this in only the nicest way, but Hams tend to be in the category of users who run older hardware. I think it will remain important to support these users through the ability for them to download older versions of WSJT-X. Where I find myself agreeing with NC7B is that the much larger problem is going to be those who upgrade to Catalina quickly and find that WSJT-X stops working for them. Personally, I plan on taking my usual approach, and let others move fast and break things with the latest Mac OS. Thanks. Robert. AD6I. On Fri, Oct 4, 2019, at 8:01 AM, Greg Vatt wrote: > Bill, > > That’s good news. Hopefully Mac users will understand this. > > I don’t think you will have much of an issue by dropping the macOS 10.10 & > 10.11 support as the vast majority of macOS users have upgraded well beyond > that (based on developer statistics). The near-term issue will be the many > MacOS users who upgrade to *Catalina* today and find WSJT-X could stop > working for them. (When we emailed earlier this year about this same topic > after the release of Catalina beta#1 to Apple developers I explored the Qt > code and noticed Qt was using hooks to depreciated code that hasn’t been > officially supported since macOS 10.10 & 10.11 so the new version of Qt will > help all the way around.) > > *Looking forward to the next release of WSJT-X*, > > 73, Greg > > NC7B > > >> On Oct 4, 2019, at 7:21 AM, Bill Somerville <[email protected]> wrote: >> >> On 04/10/2019 15:04, Greg Vatt wrote: >>> Bill, >>> >>> Here is the crash report of WSJT-X v2.1 using the last developer beta >>> before MacOS Catalina is released today. *Thread 12 Crashed:* which shows >>> it is still a Qt issue. >>> >>> This beta is supposed to be the same as the full release but I am waiting >>> to update later today with the public release of Catalina and see if this >>> is fixed. (Still using MacOS 10.14.6 on my other computer connected for Ham >>> use and WSJT-X v2.1 works fine here.) >>> >>> Greg, NC7B >>> >>> >>> Thread 12 Crashed: >>> 0 org.qt-project.*QtCore* 0x00000001088b4ce9 QLocale::QLocale() + 25 >>> 1 org.qt-project.*QtCore* 0x0000000108909395 >>> QDateTimeParser::parseSection(QDateTime const&, int, QString&, int&, int, >>> QDateTimeParser::State&, int*) const + 1237 >>> 2 org.qt-project.*QtCore* 0x000000010890b340 >>> QDateTimeParser::parse(QString&, int&, QDateTime const&, bool) const + 512 >>> 3 org.qt-project*.QtCore* 0x000000010890de14 >>> QDateTimeParser::fromString(QString const&, QDate*, QTime*) const + 148 >>> 4 org.qt-project.*QtCore* 0x00000001088a10de QDate::fromString(QString >>> const&, QString const&) + 94 >>> 5 org.k1jt.wsjtx 0x00000001039156a6 >>> LotWUsers::impl::load_dictionary(QString const&) + 230 >>> 6 org.k1jt.wsjtx 0x000000010391725c >>> std::__1::__async_assoc_state<QHash<QString, QDate>, >>> std::__1::__async_func<QHash<QString, QDate> (LotWUsers::impl::*)(QString >>> const&), LotWUsers::impl*, QString> >::__execute() + 60 >>> 7 org.k1jt.wsjtx 0x000000010391758e void* >>> std::__1::__thread_proxy<std::__1::tuple<std::__1::unique_ptr<std::__1::__thread_struct, >>> std::__1::default_delete<std::__1::__thread_struct> >, void >>> (std::__1::__async_assoc_state<QHash<QString, QDate>, >>> std::__1::__async_func<QHash<QString, QDate> (LotWUsers::impl::*)(QString >>> const&), LotWUsers::impl*, QString> >::*)(), >>> std::__1::__async_assoc_state<QHash<QString, QDate>, >>> std::__1::__async_func<QHash<QString, QDate> (LotWUsers::impl::*)(QString >>> const&), LotWUsers::impl*, QString> >*> >(void*) + 62 >>> 8 libsystem_pthread.dylib 0x00007fff69e65d76 _pthread_start + 125 >>> 9 libsystem_pthread.dylib 0x00007fff69e625d7 thread_start + 15 >>> >> Hi Greg, >> that crash is a known Qt issue (`QTBUG-71030`) and is not specific to macOS >> Catalina, or even Macs. It is fixed in Qt in a version (v5.13) that we will >> use for the next release of WSJT-X for macOS. Note that using that version >> of Qt will mean that we can no longer support macOS 10.10 and 10.11. >> 73 >> Bill >> G4WJS. > > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel >
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
