Re: [Development] [Interest] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops
On Mon, Dec 19, 2022 at 10:09 AM Tuukka Turunen wrote: > This mailing list thread is actually already part of the discussion. I am > sure the relevant stakeholders will read through the mails. One important > thing: the question is whether or not the _latest_ Qt version supports 3 or 4 > generations of macOS – because we already support the older macOS version > with the earlier Qt releases. We are avoiding to the extent possible dropping > supported platforms from released versions of Qt, so macOS 10.15 continues to > be supported with Qt releases up to Qt 6.4 in any case. This also leads into > Qt supporting such macOS versions that Apple no longer supports – like the > discussed macOS 10.15 that is supported in Qt 6.4, but no longer supported by > Apple. > > Yours, > Tuukka Thank you, Tukka, for clarifying the points for the decision makers. Hope to hear from them soon. Kind regards, Robert Iakobashvili ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Interest] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops
On Sun, Dec 18, 2022 at 3:09 PM Thiago Macieira wrote: > > That's bad. But we all know who's to blame here, in both arguments: Apple. > > > Try to listen to the people that work with the real, live customers > > like Nuno and me. > > We have. The decision is that we need to make a cut and move on, eventually. > There's only so much resource available for handling different generations. We > decided to adopt Apple's own end-of-life as ours. > > > Please, add one more old Mac OS release to the supported list to be > > more realistic, so it will be not a thin three releases but at least four. > > At this point, since my AVX2 changes have been postponed to 6.6, I don't mind > restoring 10.15 support in 6.5, as it doesn't impact me and the improvements I > plan to add. So I won't object. > > But I can't speak for Qt Company's resource commitment, with the need to *add* > 13.x to their test base. I think we all agree that MUST be tested. Given a > finite resource allocation, something will need to give and they will have to > make that choice. > > Moreover, 6.5 is one of their LTS. They have to make a choice whether they > want to keep 10.15 in support for the lifetime of that LTS. That would mean > they'd *end* support 2.5 years after Apple last provided a security update for > the OS. Their own networking requirements may imply they *can't* have that OS > in the CI because of its lack of security fixes. I don't know what it takes > for > them to allow that; I can only tell you that if Intel were hosting such > systems, those would need to be in a special lab with no direct Internet > access, which means they couldn't be part of a CI. > > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Cloud Software Architect - Intel DCAI Cloud Engineering > Thank you, Thiago, for your understanding and the assistance proposed. Thus, we need it to be approved by the Qt Company. Tukka, can we get the people of the Qt Company sitting and at least discussing: 1. The general issue related to the level of Qt support for Mac platforms considering four (4) versions to support instead of the current three (3). 2. The concrete case of Mac Support for Qt 6.5. Even if you come back and say - sorry, we considered, but decided to turn it down, still the effort will be very much appreciated. Thanks in advance for considering the options. Kind regards, Robert Iakobashvili ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Interest] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops
On Sun, Dec 18, 2022 at 3:29 AM Thiago Macieira wrote: > > On Saturday, 17 December 2022 05:40:48 -03 Tuukka Turunen via Interest wrote: > > at least between versions 10.15 and 11 there does not seem to be a > > major drop in what HW is supported. > > There is a drop, but we're talking about CPUs launched in 2013 and older. > Specifically, 11.0 drops support for Sandy Bridge and Ivy Bridge Macbooks and > Mac Minis. Whether you count that as "major" or not, I'll leave it up to you. > > What matters to me is that those were the last AVX-incapable CPUs, which allow > us to assume that AVX2 is present. Dear Thiago and Tuukka, It seems that you are working under an assumption that if the HW allows it, users will upgrade their Mac OS. This is not how it works in reality, sorry. Many, if not most, Mac users are upgrading only once. They upgrade, see how their content-editing, multimedia, etc. software is ruined by their first upgrade; next, they work with software vendors to restore their applications back to some working state, get the lesson and ... do not touch it forever. Try to listen to the people that work with the real, live customers like Nuno and me. Please, add one more old Mac OS release to the supported list to be more realistic, so it will be not a thin three releases but at least four. Please, consider that. Thanks in advance! P.S. Oh, these customers are not security aware? Agree, this is bad. Sorry, but please get it that these people, not computer fricks and sometimes technically challenged, need to run smoothly with their daily jobs rather than work hard on bringing their apps to the working stage after each upgrade. ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt 6.5 Is Irrelevant for More than 95% of Mac Desktops
Hi, Since Qt 6.5 drops Mac OS 10.15 Catalina, it apparently starts to be irrelevant for at least 95% of Mac Desktops. https://gs.statcounter.com/macos-version-market-share/desktop/worldwide Google Analytics data of visitors for some web-site, where I have access, also supports the above observations. To keep Qt-6 being still relevant for Mac Desktop open-source development, please consider keeping Mac OS 10.15 as a target. Thanks. Kind regards, Robert Iakobashvili ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Maintainance Tool
There are KDE repos, aren't there? For example: https://invent.kde.org/qt/qt/qtbase/-/commits/kde/5.15 Kind regards, Robert On Sun, Mar 6, 2022 at 3:25 PM Konstantin Ritt wrote: > > For those who have experienced inconvenience due to these blockings, I > propose to gather at some public site and create binaries repo driven by > community, not by political influences. > > > Regards, > Konstantin > > > пт, 4 мар. 2022 г. в 18:01, Andy Shaw : >> >> Hi, >> >> >> >> It is because your IP is detected to be in a country we do not allow >> downloads. If you are not able to access something you have purchased then >> let me know and I will get someone to get in touch with you directly about >> this. Otherwise, for the time being, this IP block will be in place. >> >> >> >> Regards, >> >> Andy >> >> >> >> From: Development On Behalf Of >> Konstantin Ritt >> Sent: Friday, March 4, 2022 1:43 PM >> To: Konstantin Shegunov >> Cc: Qt development mailing list >> Subject: Re: [Development] Maintainance Tool >> >> >> >> I don't care. I need some explanations here, at public dev ML. >> >> >> Regards, >> Konstantin >> >> >> >> >> >> пт, 4 мар. 2022 г. в 15:27, Konstantin Shegunov : >> >> Hi, >> I imagine you're using a russian IP address, so this[1] should shed some >> light on the matter. >> >> Kind regards, >> Konstantin. >> >> [1]: https://forum.qt.io/topic/134724/unlock-qt-in-russia > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Mac Big Sur - Qt Open-Source Support For
Dear Eike, Thank you for being so helpful. This is exactly what I need. Yes, I used to build from sources and never rely on binaries. Have a great weekend! Kind regards, Robert On Fri, May 7, 2021 at 1:35 PM Eike Ziller wrote: > > > > > On May 7, 2021, at 12:16, coroberti wrote: > > > > Dear Eike, > > Thanks for your comprehensive answer. > > > > I will try to build it from open-source 5.15 branch > > > > Where is the link to the branch? > > Thanks! > > The official git repository is this: > https://code.qt.io/cgit/qt/qtbase.git/?h=5.15 > > I don’t see a simple way to get a source bundle of that from there, if you > don’t want to use git though. > Also, Qt splits parts into different git submodules, i.e. different > repositories, which doesn’t make it trivial to create something like the > qt-everywhere-src-5.15.2.zip that we have for releases. > > I suppose the easiest way is to simply apply the two patches to the 5.15.2 > sources (https://download.qt.io/official_releases/qt/5.15/5.15.2/single/): > > https://codereview.qt-project.org/c/qt/qtbase/+/322102 > https://codereview.qt-project.org/c/qt/qtbase/+/325927 > > Or you can try replacing the whole qtbase subdirectory of the Qt 5.15.2 > sources with the qtbase 5.15 branch source bundle from github: > https://github.com/qt/qtbase/tree/5.15 -> click the green “code” button and > choose “Download ZIP”. > (No idea if or how well that would work though.) > > Br, Eike > > > > > Kind regards, > > Robert Iakobashvili > > > > > > On Fri, May 7, 2021 at 1:12 PM Eike Ziller wrote: > >> > >> > >> > >>> On May 7, 2021, at 11:47, Tor Arne Vestbø wrote: > >>> > >>> Qt 6.0 and above has official support for Big Sur: > >>> > >>> https://doc.qt.io/archives/qt-6.0/macos.html > >>> > >>> 5.15 is not yet officially supported, but should work fine as well, so > >>> please report any issues in JIRA, thanks! > >>> > >> > >> Except for > >> [QTBUG-88495] Text rendering: spaces are rendered incorrectly on macOS Big > >> Sur after commas, dots. - Qt Bug Tracker > >> https://bugreports.qt.io/browse/QTBUG-88495 > >> and > >> [QTBUG-88985] Context QMenu without parent blocked by modal dialog on > >> macOS - Qt Bug Tracker > >> https://bugreports.qt.io/browse/QTBUG-88985 > >> > >> for which the fixes are available in the opensource 5.15 branch, but not > >> in the 5.15.2 release. > >> > >> Qt Creator binaries are released based on Qt 5.15.2, so you can check that > >> for reference. > >> > >> Br, Eike > >> > >>> Cheers, > >>> Tor Arne > >>> > >>>> On 7 May 2021, at 11:00, coroberti wrote: > >>>> > >>>> Dear Tukka and others, > >>>> Since September Big Sur is a reality. > >>>> > >>>> Which Qt-version supports correctly QWidgets for this platform for > >>>> open-source development. > >>>> > >>>> If there's no such version, when the support is planned if ever. > >>>> > >>>> I'd appreciate not to hijack this question for any discussions beyond the > >>>> very narrow scope of this question. > >>>> > >>>> Thanks, > >>>> > >>>> Kind regards, > >>>> Robert > >>>> ___ > >>>> Development mailing list > >>>> Development@qt-project.org > >>>> https://lists.qt-project.org/listinfo/development > >>> > >>> ___ > >>> Development mailing list > >>> Development@qt-project.org > >>> https://lists.qt-project.org/listinfo/development > >> > >> -- > >> Eike Ziller > >> Principal Software Engineer > >> > >> The Qt Company GmbH > >> Erich-Thilo-Straße 10 > >> D-12489 Berlin > >> eike.zil...@qt.io > >> http://qt.io > >> Geschäftsführer: Mika Pälsi, > >> Juha Varelius, Jouni Lintunen > >> Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht > >> Charlottenburg, HRB 144331 B > >> > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Jouni Lintunen > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, > HRB 144331 B > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Interest] Mac Big Sur - Qt Open-Source Support For
Thanks, Tuukka, for the information. Kind regards, Robert Iakobashvili On Fri, May 7, 2021 at 1:18 PM Tuukka Turunen wrote: > > Hi, > > > > Supporting Apple silicon is something we are actively working to have in > place for Qt 6.2 including full CI coverage etc. > > > > To some extent things will work also with Qt 5.15 if you build yourself, but > there are some rough edges (and Qt 5.15 is not tested for M1). > > > > Yours, > > > > Tuukka > > > > From: Interest on behalf of Nuno Santos > > Date: Friday, 7. May 2021 at 13.10 > To: Tor Arne Vestbø > Cc: Qt development mailing list , Qt Interest > > Subject: Re: [Interest] [Development] Mac Big Sur - Qt Open-Source Support For > > Tor, > > > > What about building Qt 5.15.X for M1 Macs? > > > > Is there any kind of wiki resource out there? > > > > Regards, > > > > Nuno > > > > On 7 May 2021, at 10:47, Tor Arne Vestbø wrote: > > > > Qt 6.0 and above has official support for Big Sur: > > > > https://doc.qt.io/archives/qt-6.0/macos.html > > > > 5.15 is not yet officially supported, but should work fine as well, so please > report any issues in JIRA, thanks! > > > > Cheers, > Tor Arne > > > > On 7 May 2021, at 11:00, coroberti wrote: > > > > Dear Tukka and others, > Since September Big Sur is a reality. > > Which Qt-version supports correctly QWidgets for this platform for > open-source development. > > If there's no such version, when the support is planned if ever. > > I'd appreciate not to hijack this question for any discussions beyond the > very narrow scope of this question. > > Thanks, > > Kind regards, > Robert > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > > > > ___ > Interest mailing list > inter...@qt-project.org > https://lists.qt-project.org/listinfo/interest > > > > ___ > Interest mailing list > inter...@qt-project.org > https://lists.qt-project.org/listinfo/interest ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Mac Big Sur - Qt Open-Source Support For
Dear Tor Arne, Thank you for your reply. It's less useful since Qt-6 is a phantom, beta, and it will remain so for a year or more. Kind regards, Robert Iakobashvili On Fri, May 7, 2021 at 12:47 PM Tor Arne Vestbø wrote: > > Qt 6.0 and above has official support for Big Sur: > > https://doc.qt.io/archives/qt-6.0/macos.html > > 5.15 is not yet officially supported, but should work fine as well, so please > report any issues in JIRA, thanks! > > Cheers, > Tor Arne > > On 7 May 2021, at 11:00, coroberti wrote: > > Dear Tukka and others, > Since September Big Sur is a reality. > > Which Qt-version supports correctly QWidgets for this platform for > open-source development. > > If there's no such version, when the support is planned if ever. > > I'd appreciate not to hijack this question for any discussions beyond the > very narrow scope of this question. > > Thanks, > > Kind regards, > Robert > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development > > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Mac Big Sur - Qt Open-Source Support For
Dear Eike, Thanks for your comprehensive answer. I will try to build it from open-source 5.15 branch Where is the link to the branch? Thanks! Kind regards, Robert Iakobashvili On Fri, May 7, 2021 at 1:12 PM Eike Ziller wrote: > > > > > On May 7, 2021, at 11:47, Tor Arne Vestbø wrote: > > > > Qt 6.0 and above has official support for Big Sur: > > > > https://doc.qt.io/archives/qt-6.0/macos.html > > > > 5.15 is not yet officially supported, but should work fine as well, so > > please report any issues in JIRA, thanks! > > > > Except for > [QTBUG-88495] Text rendering: spaces are rendered incorrectly on macOS Big > Sur after commas, dots. - Qt Bug Tracker > https://bugreports.qt.io/browse/QTBUG-88495 > and > [QTBUG-88985] Context QMenu without parent blocked by modal dialog on macOS - > Qt Bug Tracker > https://bugreports.qt.io/browse/QTBUG-88985 > > for which the fixes are available in the opensource 5.15 branch, but not in > the 5.15.2 release. > > Qt Creator binaries are released based on Qt 5.15.2, so you can check that > for reference. > > Br, Eike > > > Cheers, > > Tor Arne > > > >> On 7 May 2021, at 11:00, coroberti wrote: > >> > >> Dear Tukka and others, > >> Since September Big Sur is a reality. > >> > >> Which Qt-version supports correctly QWidgets for this platform for > >> open-source development. > >> > >> If there's no such version, when the support is planned if ever. > >> > >> I'd appreciate not to hijack this question for any discussions beyond the > >> very narrow scope of this question. > >> > >> Thanks, > >> > >> Kind regards, > >> Robert > >> ___ > >> Development mailing list > >> Development@qt-project.org > >> https://lists.qt-project.org/listinfo/development > > > > ___ > > Development mailing list > > Development@qt-project.org > > https://lists.qt-project.org/listinfo/development > > -- > Eike Ziller > Principal Software Engineer > > The Qt Company GmbH > Erich-Thilo-Straße 10 > D-12489 Berlin > eike.zil...@qt.io > http://qt.io > Geschäftsführer: Mika Pälsi, > Juha Varelius, Jouni Lintunen > Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, > HRB 144331 B > ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Mac Big Sur - Qt Open-Source Support For
Dear Tukka and others, Since September Big Sur is a reality. Which Qt-version supports correctly QWidgets for this platform for open-source development. If there's no such version, when the support is planned if ever. I'd appreciate not to hijack this question for any discussions beyond the very narrow scope of this question. Thanks, Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Releasing] [Interest] download.qt.io is down
On Fri, Jan 22, 2021 at 10:38 AM Nils Jeisecke via Development wrote: > > Hi there, > > On Fri, Jan 22, 2021 at 7:59 AM Tuukka Turunen wrote: >> >> Hi, >> >> >> >> Status update of the problem with open-source downloads: Last night we >> finally got a disk big enough for the packages from the service provider. >> Most of the data has been transferred throughout the night with a few last >> things still being uploaded to the new virtual server. After the data >> transfer is complete we start testing and validation of the data and the >> system. Target is to enable first the online installer, then the offline >> packages and finally the achieve of old releases. > > > just a little "Thank You" from my side. > > I try to imagine being of those spending hour after hour to get things > running again and then reading all those nasty comments on the blog post. > > Nils Joining the thanks of Nils. We are really appreciating your support of open-source distribution. Kind regards, Robert Iakobashvili ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Interest] Windows 7 support will be dropped in Qt 6
On Thu, Jun 11, 2020 at 4:48 PM Oliver Wolff wrote: > > Hi Robert, > > On 11.06.2020 15:02, coroberti . wrote: > > On Thu, Jun 11, 2020 at 3:43 PM Oliver Wolff wrote: > >> with Qt 6 approaching it is time to have a look at our set of supported > >> platforms. > > > >> The operating system was initially launched in 2009 and reached its > >> official end of life in January 2020. That means that Microsoft no > >> longer provides security updates and instances running Windows 7 should > >> be replaced as soon as possible. > >> > >> Br, Olli > > > > Dear Oliver, > > > > The fact is that Windows-7 is supported at least till 2023. > > > > Please, correct your fact table. > > > > https://www.microsoft.com/microsoft-365/partners/news/article/announcing-paid-windows-7-extended-security-updates > > > It's true that Microsoft offers extended support for Windows 7. This > support does not come for free though and there is a price tag attached. > > I think the same might apply inside The Qt Company. If you are a > commercial customer and want to buy extended support for Qt beyond > regular support availability periods, please get in touch with your > Sales representative. If you remove Win-7 from Qt-6, your suggested option of support for commercial customers will be void for Qt-6. After removal, it will be a mess to re-introduce it back whatever money you will be paid. Period. Full-Stop. Qt-6 will have less attractiveness for those bodies that need Win-7: governments, corporates, military, health, insurance, finance, banks and their suppliers. At least talk to your Sales prior to doing it since they have a better smell for money. If Microsoft smells the money - think twice if you'd like to lose this market in Qt-6. Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Interest] Windows 7 support will be dropped in Qt 6
On Thu, Jun 11, 2020 at 3:43 PM Oliver Wolff wrote: > with Qt 6 approaching it is time to have a look at our set of supported > platforms. > The operating system was initially launched in 2009 and reached its > official end of life in January 2020. That means that Microsoft no > longer provides security updates and instances running Windows 7 should > be replaced as soon as possible. > > Br, Olli Dear Oliver, The fact is that Windows-7 is supported at least till 2023. Please, correct your fact table. https://www.microsoft.com/microsoft-365/partners/news/article/announcing-paid-windows-7-extended-security-updates Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt-6 Support for 32-bit Windows-10
Hi, Is there any public page to look at the platforms and tools planned for support by Qt-6.0? For example, are there any plans to support 32-bit Windows-10 by Qt-6.0? Thanks, Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] [Interest] Dictation to Qt-Software on Windows-10 Is Broken
Dear Oliver and Andre, Thank you for your reply and plans to fix it. When you have a patch, please let me know. I can help to test the fix by building Qt from sources and applying the patch/patches. Thanks in advance! Kind regards, Robert On Wed, May 13, 2020 at 7:36 AM Oliver Wolff wrote: > > Hi Robert, > > On 12.05.2020 13:14, coroberti . wrote: > > Hi, > > If somebody in charge could consider increasing priority of the below > > major Accessibility issue, it would be really appreciated. > > > > You cannot dictate to Qt text controls on Windows 10, 8 and 7. > > > > https://bugreports.qt.io/browse/QTBUG-83671 > > > > There is no workaround within Qt platform. > > > > Thanks in advance! > > Sorry for the late reply. Andre had a look at the issue yesterday and > commented on the bug report. He is currently busy with something else > but promised to get back to the topic afterwards. > > Kind regards, > Olli > > > > > Kind regards, > > Robert > > > > On Tue, Apr 21, 2020 at 9:54 AM coroberti . wrote: > >> You cannot dictate to Qt-software on Windows-10: > >> https://bugreports.qt.io/browse/QTBUG-83671 > >> > >> Actually, it was always a broken area at least since 2015: > >> > >> https://bugreports.qt.io/browse/QTBUG-45980 > >> > >> If people on the list have a chance to vote, please vote. > >> > >> Thanks, > >> > >> Kind regards, > >> Robert > > ___ > > Interest mailing list > > inter...@qt-project.org > > https://lists.qt-project.org/listinfo/interest > > > ___ > Interest mailing list > inter...@qt-project.org > https://lists.qt-project.org/listinfo/interest ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Dictation to Qt-Software on Windows-10 Is Broken
Hi, If somebody in charge could consider increasing priority of the below major Accessibility issue, it would be really appreciated. You cannot dictate to Qt text controls on Windows 10, 8 and 7. https://bugreports.qt.io/browse/QTBUG-83671 There is no workaround within Qt platform. Thanks in advance! Kind regards, Robert On Tue, Apr 21, 2020 at 9:54 AM coroberti . wrote: > You cannot dictate to Qt-software on Windows-10: > https://bugreports.qt.io/browse/QTBUG-83671 > > Actually, it was always a broken area at least since 2015: > > https://bugreports.qt.io/browse/QTBUG-45980 > > If people on the list have a chance to vote, please vote. > > Thanks, > > Kind regards, > Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Dictation to Qt-Software on Windows-10 Is Broken
Hi, If by chance Qt-Accessibility has a maintainer, this is the new and even more severe issue with dictation on Windows-10. You cannot dictate to Qt-software on Windows-10: https://bugreports.qt.io/browse/QTBUG-83671 Actually, it was always a broken area at least since 2015: https://bugreports.qt.io/browse/QTBUG-45980 If people on the list have a chance to vote, please vote. Thanks, Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt-5.14.2 - iOS - Drag & Drop
On Mon, Apr 20, 2020 at 1:04 PM Tor Arne Vestbø wrote: > > This is a missing feature, please file a feature request, thanks! > > Tor Arne > > > On 20 Apr 2020, at 08:54, coroberti . wrote: > > > > On Sun, Apr 5, 2020 at 1:32 PM coroberti . wrote: > >> Trying to allow Drag to my app on iOS (iPad with spitted view) > >> and working in line with: https://doc.qt.io/qt-5/dnd.html > >> > >> I see that dragEnterEvent () and dragMoveEvent () are never called. > >> > >> This is in contrast to Mac OS X where it works for the same exactly code > >> properly. > >> (and acceptDrops(true) was set). > >> > >> I was using on both platforms QTextEdit widget. > >> > >> Is it correct to say that on iOS widgets lack implementation of drap&drop > >> events? > >> > >> Please, let me know if I'm missing something like configuration missed, > >> etc. > >> > >> Thanks in advance! > >> > >> Kind regards, > >> Robert Iakobashvili > >> > > > > Could somebody from iOS of GUI maintainers guide me whether the > > issue above is a bug or a feature request to open? > > > > Thanks in advance! > > > > Kind regards, > > Robert Thanks, Tor Arne Vestbø. Here it is: https://bugreports.qt.io/browse/QTBUG-83665 Please, vote for it. Thanks! Kind regards, Robert Iakobashvili ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Qt-5.14.2 - iOS - Drag & Drop
On Sun, Apr 5, 2020 at 1:32 PM coroberti . wrote: > Trying to allow Drag to my app on iOS (iPad with spitted view) > and working in line with: https://doc.qt.io/qt-5/dnd.html > > I see that dragEnterEvent () and dragMoveEvent () are never called. > > This is in contrast to Mac OS X where it works for the same exactly code > properly. > (and acceptDrops(true) was set). > > I was using on both platforms QTextEdit widget. > > Is it correct to say that on iOS widgets lack implementation of drap&drop > events? > > Please, let me know if I'm missing something like configuration missed, etc. > > Thanks in advance! > > Kind regards, > Robert Iakobashvili > Could somebody from iOS of GUI maintainers guide me whether the issue above is a bug or a feature request to open? Thanks in advance! Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] Qt-5.14.2 - iOS - Drag & Drop
Hi, Thanks to Qt-team for the latest patch release. Trying to allow Drag to my app on iOS (iPad with spitted view) and working in line with: https://doc.qt.io/qt-5/dnd.html I see that dragEnterEvent () and dragMoveEvent () are never called. This is in contrast to Mac OS X where it works for the same exactly code properly. (and acceptDrops(true) was set). I was using on both platforms QTextEdit widget. Is it correct to say that on iOS widgets lack implementation of drap&drop events? Please, let me know if I'm missing something like configuration missed, etc. Thanks in advance! Kind regards, Robert Iakobashvili ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] How to get winid from qprocess id for QProcess
On Thu, Feb 20, 2020 at 5:36 PM Sujan Dasmahapatra
wrote:
> I am running an external app, which I want to fit onto my QScrollArea, for
> this I am writing code like this.
>
> // launch weasis
> QProcess *process = new QProcess();
> process->start("./viewer-win32.exe");
> if (process->waitForFinished())
> {
> return;
> }
>
> QWindow *window = QWindow::fromWinId(211812356);
> window->setFlags(Qt::FramelessWindowHint);
> _patient_gui->scrollArea_1->setWidget(QWidget::createWindowContainer(window));
>
> But how can I get the wind id? it is hard coded here, is there any way to get
> the id from process id.
>
> any help is highly appreciated.
>
Dear Sujan
The direction is to enumerate currently running windows of a particular process
and to find the right one, i.e. by title.
You can start here:
https://docs.microsoft.com/en-us/windows/win32/psapi/enumerating-all-processes
https://stackoverflow.com/questions/42589496/getting-a-list-of-all-open-windows-in-c-and-storing-them
Take care,
Robert Iakobashvili
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
Re: [Development] Changes to Qt offering
Jason, The main market for QtCompany is embedded, automotive, etc. Mobile is aside with no real sales there. So, unless community develops features required, do not expect to get new mobile features fast. Sorry to say that. Kind regards, Robert On Tue, Jan 28, 2020 at 7:37 PM Jason H wrote: > > So I've had a night to think about and react to this. > > I want Qt to be successful and make lots of money in addition to taking over > the world. I can appreciate this approach as a way to drive sales. After all, > anything that gets Qt for Mobile more complete is very much appreciated. ;-) > > However I think these decisions are moving Qt in the wrong direction. It's > making Qt less accessible, not more. Even something as trivial as the skip > button in the online installer causes a lot of friction. At a time when the > cross platform toolkits are proliferating, (mainly Webkit based technologies > (Electron, ReactNative, etc)) and interest in C++ is waning, adding friction > is not a plus. Or an alternative is true: Qt has crushed it with auto > manufacturers and doesn't care about any other segment anymore. (The behavior > seems to indicate this, maybe not auto exclusively but if you look at all the > recent additions, they've all been targeted to the vehicle space (flagrant > speculation)) > > Also, I absolutely require headless binary install. I would actively rid Qt > from systems (outside of mobile) and move to Python (and not PyQt) if I lost > this ability. > > In short, I am disappointed to hear the changes. But all the news out of Qt > has been disappointing as of late: > - this announcement > - no mobile progress > - the previous license changes Tukka announced (QtPDF, etc: > https://www.qt.io/blog/change-in-open-source-licensing-of-qt-wayland-compositor-qt-application-manager-and-qt-pdf) > > There's been a lot of taking away and not a lot of providing. Is Qt still > useful? Sure, but the vector is pointing in the wrong direction. > > > > Sent: Monday, January 27, 2020 at 9:34 AM > > From: "Lars Knoll" > > To: "Qt development mailing list" > > Subject: [Development] Changes to Qt offering > > > > Hi all, > > > > The Qt Company has done some adjustments to the Qt will be offered in the > > future. Please check out https://www.qt.io/blog/qt-offering-changes-2020 . > > > > The change consists of three parts. > > > > One is a change in policy regarding the LTS releases, where the LTS part of > > a release is in the future going to be restricted to commercial customers. > > All bug fixes will (as agreed on the Qt Contributor Summit) go into dev > > first. Backporting bug fixes is something that the Qt Company will take > > care of for these LTS branches. We’ve seen over the past that LTS support > > is something mainly required by large companies, and should hopefully help > > us get some more commercial support for developing Qt further. > > > > The second change is that a Qt Account will be in the future required for > > binary packages. Source code will continue to be available as currently. > > This will simplify distribution and integration with the Marketplace. In > > addition, we want open source users to contribute to Qt or the Qt > > ecosystem. Doing so is only possible with a valid Qt Account (Jira, code > > review and the forums all require a Qt Account). > > > > The third change is that The Qt Company will in the future also offer a > > lower priced product for small businesses. That small business product is > > btw not limited to mobile like the one Digia had some years ago, but covers > > all of Qt for Device Creation. > > > > None of these changes should affect how Qt is being developed. There won’t > > be any changes to Open Governance or the open development model. > > > > Best regards, > > Lars > > > > ___ > > Development mailing list > > Development@qt-project.org > > https://lists.qt-project.org/listinfo/development > > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Changes to Qt offering
On Tue, Jan 28, 2020 at 1:01 PM ekke wrote: > > Am 28.01.20 um 11:14 schrieb coroberti .: > > On Tue, Jan 28, 2020 at 11:55 AM Konstantin Shegunov > > wrote: > >> > >> > >>> The third change is that The Qt Company will in the future also offer a > >>> lower priced product for small businesses. That small business product is > >>> btw not limited to mobile like the one Digia had some years ago, but > >>> covers all of Qt for Device Creation. > >> > >> I see a couple of issues here. Firstly, 100k/year *turnover* isn't a small > >> business, that's a nano-company (i.e. 1-2 devs max) and if they're > >> providing a device alongside the software that 100k is going to be eaten > >> in no time. Notice we are not talking profit here, but raw revenue. > >> Whoever from sales came up with that number, really did a botched up job > >> with it. On that note, even if we accept that it's applicable, the > >> straightforward math shows you want to bill 0.5% - 2.5% of the total > >> turnover, so while this sounds good initially it really isn't that shiny > >> when you crunch the numbers. That offering is stillborn from my point of > >> view. > > Agree with Konstantin that the definition of a small business isn't > > realistic. > > The realistic one is up to 5 developers and up 500k/year USD sales. > > > > ... > > > > So, hello, Qt-company, and consider to make something really friendly > > for small businesses ... > > +1 Konstantin and coroberti > > I'm only a single mobile app developer and for me it is ok with 100k and > $499/year > > but I know many developers from small businesses (2-5 devs) and it's > really not realistic to think they have less 100k sales total per year ;-) > > coroberti's idea (up 500k sales per year) covers the target (StartUp, > Small Business) much better and is something making it easier to > motivate mobile app devs to use Qt instead of Flutter, Xamarin, React or so. > > please rethink your definition of StartUp / SmallBusiness to make this > license a success for Qt > > ekke Thanks, Ekke, And several more params not to miss for a small license: - think how to be customer friendly and not red tape; - charge once a year or monthly - by user selection; - provide a guarantee of not increasing charges for least for 5 years; - provide guarantee of not changing the model for a while. Perhaps, this is not your major market, but you can really get some income here. At the end of the day, you are not providing support and all your income is a pure profit unless you screw matters and push people out. Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Changes to Qt offering
On Tue, Jan 28, 2020 at 11:55 AM Konstantin Shegunov wrote: > > On Mon, Jan 27, 2020 at 4:36 PM Lars Knoll wrote: >> >> One is a change in policy regarding the LTS releases, where the LTS part of >> a release is in the future going to be restricted to commercial customers. >> All bug fixes will (as agreed on the Qt Contributor Summit) go into dev >> first. Backporting bug fixes is something that the Qt Company will take care >> of for these LTS branches. We’ve seen over the past that LTS support is >> something mainly required by large companies, and should hopefully help us >> get some more commercial support for developing Qt further. > > > This all sounds like a spanking for the LGPL users, and it really is. Leaves > a really bad aftertaste, especially for those that actively try to give > something back (even if it's a small something) as a "compensation" for using > the LGPL license. I don't think anyone would be against bigger businesses > pitching in more into development (moneywise), but as a one-man-show the feel > is that I've been penalized for not paying the rather insane license fee. > >> The third change is that The Qt Company will in the future also offer a >> lower priced product for small businesses. That small business product is >> btw not limited to mobile like the one Digia had some years ago, but covers >> all of Qt for Device Creation. > > > I see a couple of issues here. Firstly, 100k/year *turnover* isn't a small > business, that's a nano-company (i.e. 1-2 devs max) and if they're providing > a device alongside the software that 100k is going to be eaten in no time. > Notice we are not talking profit here, but raw revenue. Whoever from sales > came up with that number, really did a botched up job with it. On that note, > even if we accept that it's applicable, the straightforward math shows you > want to bill 0.5% - 2.5% of the total turnover, so while this sounds good > initially it really isn't that shiny when you crunch the numbers. That > offering is stillborn from my point of view. Agree with Konstantin that the definition of a small business isn't realistic. The realistic one is up to 5 developers and up 500k/year USD sales. Qt-company may wish to look at the past experience with its failed tiny-license and mobile-license. You cannot get from such companies more than 500 greens a year, and 300 is even more realistic. Personally, I've convinced management to pay 25 USD/month for the Mobile license to support Qt-development, but we never used the license and continued open-source. At a certain point the charges have stopped with an insane offer and insane pricing. So, hello, Qt-company, and consider to make something really friendly for small businesses since we are flexible and really not locked to your offering. Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Changes to Qt offering
Dear Lars, What about sources of LTS versions? Could they be still available? Thanks. Kind regards, Robert Iakobashvili On Mon, Jan 27, 2020 at 4:35 PM Lars Knoll wrote: > > Hi all, > > The Qt Company has done some adjustments to the Qt will be offered in the > future. Please check out https://www.qt.io/blog/qt-offering-changes-2020 . > > The change consists of three parts. > > One is a change in policy regarding the LTS releases, where the LTS part of a > release is in the future going to be restricted to commercial customers. All > bug fixes will (as agreed on the Qt Contributor Summit) go into dev first. > Backporting bug fixes is something that the Qt Company will take care of for > these LTS branches. We’ve seen over the past that LTS support is something > mainly required by large companies, and should hopefully help us get some > more commercial support for developing Qt further. > > The second change is that a Qt Account will be in the future required for > binary packages. Source code will continue to be available as currently. This > will simplify distribution and integration with the Marketplace. In addition, > we want open source users to contribute to Qt or the Qt ecosystem. Doing so > is only possible with a valid Qt Account (Jira, code review and the forums > all require a Qt Account). > > The third change is that The Qt Company will in the future also offer a lower > priced product for small businesses. That small business product is btw not > limited to mobile like the one Digia had some years ago, but covers all of Qt > for Device Creation. > > None of these changes should affect how Qt is being developed. There won’t be > any changes to Open Governance or the open development model. > > Best regards, > Lars > > ___ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Stepping down as Qt for macOS maintainer (but don't worry)
On Mon, Dec 9, 2019 at 2:32 PM Tor Arne Vestbø wrote: > > > > On 9 Dec 2019, at 12:57, Timur Pocheptsov wrote: > > Oh, but please, do not fix the grammar-bot to enforce this spelling of macOS! > > > Don’t worry, it will be a pain-free transition: > https://gist.github.com/torarnv/d558710a236711eb274c03bba59704e0 > > > Cheers, > Tor Arne But don't miss to update upstream - they are still using the old name. https://www.apple.com/macos/catalina/ Congrats, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] NTLM Issue with Qt-5.12 LTS
On Mon, Aug 19, 2019 at 1:04 PM Volker Hilsheimer wrote: > > On 19 Aug 2019, at 11:41, coroberti . wrote: > > Hi, > Could be this issue be given a priority since it's a regression > and strikes deployments of Qt-5.12 LTS on Windows? > > https://bugreports.qt.io/browse/QTBUG-44096 > > > > Hey Robert (and others), > > could you help with verifying the proposed fix in > > https://codereview.qt-project.org/c/qt/qtbase/+/265900 > > FWIW, from the report it doesn’t seem to be regression within Qt 5; the > report is originally against Qt 5.4, at least. > > Cheers, > Volker > Hi Volker, It appeared, however, that my server side has been changed by admin, and I cannot reproduce the original issue. I've applied the patch and tried. The good news it that there was no any badness introduced. Sorry, but it seems that somebody else with an appropriate setup is required to make the positive verification. Sorry for the buzz. Kind regards, Robert ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
[Development] NTLM Issue with Qt-5.12 LTS
Hi, Could be this issue be given a priority since it's a regression and strikes deployments of Qt-5.12 LTS on Windows? https://bugreports.qt.io/browse/QTBUG-44096 Thanks in advance! Kind regards, Robert Iakobashvili ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
Re: [Development] Suggestion - Remove Windows 7 as supported development host
Hi, So where to develop? At Win-10 spying everything? Since Win-7 is with paid updates due for 4 more years, please continue to support it. Thanks in advance. Regards, Robert On Tue, Nov 13, 2018 at 3:13 PM Harald Kjølberg wrote: > > > Hi, > > > Referring to: https://bugreports.qt.io/browse/QTBUG-70891 > > The suggestion is to remove Windows 7 as a supported development host, but > keep it as a target. From the numbers I have access to, more than 55% of the > users are on Windows 10. However, I would like to get feedback on this in > case there are other opinions. > > > > Thanks! > > > > Best, > Harald Kjølberg > Product Manager – QtAD > > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] QTextEdit - Line Spacing
> > Il 11/11/18 17:15, coroberti . ha scritto:
> > > Following Allan's advise, here's something that is starting to work
> > > (checks omitted)
> > >
> > > QTextDocument* doc = this->text_edit_->document();
> > > QTextBlock currentBlock = doc->firstBlock();
> > >
> > > while (currentBlock.isValid()) {
> > >
> > > QTextCursor cursor(currentBlock);
> > > QTextBlockFormat blockFormat = currentBlock.blockFormat();
> > > blockFormat.setLineHeight(200,
> > > QTextBlockFormat::ProportionalHeight);
> > > cursor.setBlockFormat(blockFormat);
> > >
> > > currentBlock = currentBlock.next();
> > > }
> > >
> > > Thank you very much!
> >
> > Isn't it simpler to use a selection approach instead?
> >
> > QTextBlockFormat format;
> > format.setLineHeight(...);
> >
> > QTextCursor cursor(textDocument);
> > cursor.select(QTextCursor::Document);
> > cursor.mergeBlockFormat(format);
> > My 2 c,
> > --
> > Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer
Thanks, Guiseppe. It also works properly.
Thanks, Allan.
So, there are two good ways from the API point of view.
When HTML from QTextEdit is retrieved by toHtml(), it generates HTML
with the correct line-height, i.e. 200% as in the example below:
It's properly treated by browsers, etc.
However, when saved to an html file and next loaded to QTextEdit,
line-height attribute inside tag is ignored.
This page doesn't refer to line-height as to the supported attributes:
http://doc.qt.io/qt-5/richtext-html-subset.html#block-attributes
Is it correct to say that this is not a bug but rather an expected behavior,
and bug report is not required for this case?
Thanks.
Kind regards,
Robert Iakobashvili
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QTextEdit - Line Spacing
Kind regards,
Robert Iakobashvili
On Sun, Nov 11, 2018 at 5:29 PM coroberti . wrote:
>
> On Sun, Nov 11, 2018 at 5:21 PM Allan Sandfeld Jensen
> wrote:
> >
> > On Sonntag, 11. November 2018 16:13:12 CET coroberti . wrote:
> > > On Sun, Nov 11, 2018 at 5:06 PM Allan Sandfeld Jensen
> > wrote:
> > > > On Sonntag, 11. November 2018 14:11:52 CET coroberti . wrote:
> > > > > Hi,
> > > > > It seems that arranging line spacing for text in QTextEdit (like 1.5,
> > > > > 2, 3 lines) is not an easy coding.
> > > > >
> > > > > Any code samples, directions, howtos would be very much appreciated.
> > > >
> > > > There is probably a way to get to the default or root QTextBlockFormat
> > > > and
> > > > set lineHeight on it, but I couldn't spot the logical way from QTextEdit
> > > > either; but you can always just do it in CSS and set the CSS as the
> > > > default style- sheet on the document the QTextEdit is showing. Remember
> > > > a
> > > > QTextEdit is basically showing HTML, so you can do it like you would in
> > > > HTML.
> > > >
> > > > 'Allan
> > >
> > > Hi Allan,
> > > Thanks, but It seems that only this HTML/CSS subset is supported:
> > >
> > > http://doc.qt.io/qt-5/richtext-html-subset.html
> > >
> > Right, line-height isn't mentioned there, but considering the C++ side of
> > the
> > CSS implementation (QTextBlockFormat) has it, it might just have left out. I
> > would give it a shot.
> >
> > 'Allan
>
> Right. You mean to work with:
> http://doc.qt.io/qt-5/qtextblockformat.html#setLineHeight
> http://doc.qt.io/qt-5/qtextblockformat.html#LineHeightTypes-enum ->
> QTextBlockFormat::ProportionalHeight1This sets the spacing
> proportional to the line (in percentage). For example, set to 200 for
> double spacing.
> Thank you.
> Kind regards,
> Robert
Following Allan's advise, here's something that is starting to work
(checks omitted)
QTextDocument* doc = this->text_edit_->document();
QTextBlock currentBlock = doc->firstBlock();
while (currentBlock.isValid()) {
QTextCursor cursor(currentBlock);
QTextBlockFormat blockFormat = currentBlock.blockFormat();
blockFormat.setLineHeight(200, QTextBlockFormat::ProportionalHeight);
cursor.setBlockFormat(blockFormat);
currentBlock = currentBlock.next();
}
Thank you very much!
Robert
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] QTextEdit - Line Spacing
On Sun, Nov 11, 2018 at 5:06 PM Allan Sandfeld Jensen wrote: > > On Sonntag, 11. November 2018 14:11:52 CET coroberti . wrote: > > Hi, > > It seems that arranging line spacing for text in QTextEdit (like 1.5, > > 2, 3 lines) is not an easy coding. > > > > Any code samples, directions, howtos would be very much appreciated. > > > There is probably a way to get to the default or root QTextBlockFormat and set > lineHeight on it, but I couldn't spot the logical way from QTextEdit either; > but you can always just do it in CSS and set the CSS as the default style- > sheet on the document the QTextEdit is showing. Remember a QTextEdit is > basically showing HTML, so you can do it like you would in HTML. > > 'Allan Hi Allan, Thanks, but It seems that only this HTML/CSS subset is supported: http://doc.qt.io/qt-5/richtext-html-subset.html Best regards, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QTextEdit - Line Spacing
Hi, It seems that arranging line spacing for text in QTextEdit (like 1.5, 2, 3 lines) is not an easy coding. Any code samples, directions, howtos would be very much appreciated. Thanks in advance! Kind regards, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Windows 7 support future removal
On Tue, Aug 28, 2018 at 12:34 AM, Thiago Macieira wrote: > On Monday, 27 August 2018 01:50:46 PDT André Pönitz wrote: >> On Mon, Aug 27, 2018 at 12:00:17AM -0700, Thiago Macieira wrote: >> > I don't have a problem with that, so long as they never connect those >> > computers to the Internet after January 2020. That would be irresponsible. >> >> Because of what? > > Because it's not receiving security updates. > >> Because Microsoft (or any OS vendor that's on the "newer is better" trip >> for that matter) have scheduled the invention of the magic sauce that makes >> their systems suddenly safe to use in public networks for December 2019? > > No, that sauce is already known. It's called "security updates" and they have > to be applied on a continuous basis. You may not need to apply all fixes, but > you need to have the ability to do so when there's a fix that is relevant to > you. > > Starting in January 2020, the only company that could make those fixes will > stop making them. It is unlikely that the next day will start with a new > vulnerability discovered, but one will be sooner or later. And since no fix > will ever be coming, those devices will be forever vulnerable. > > Sure, there are other ways to mitigate the problem, like having an external > firewall. But all it takes is another device also vulnerable on that network > to allow access in and now those out-of-date Windows are accessible. > >> "Realistically" (a term I colloquially use for "extrapolating from a number >> of incidents in the past") we will see trading semi-working systems with a >> certain number of known and an uncertain number of unknown deficiencies for >> other systems with another uncertain number of the same of other, newer >> unknown deficiencies. > > Right. But worse than that, you have an unknown number of devices with *known* > deficiencies. > >> This might look like an advantage to some, but it isn't in any metrics >> that I am tempted to take seriously - *especially* when there are ways >> to mitigate some of known deficiencies in a way that don't boil down >> to "try to use a newer random version of what we sold you last year as >> the best thing since sliced bread". > > Defence in depth. You should deploy those other mitigations, like the > firewall. But ignoring or not receiving OS fixes is a critical problem. > > Then again, those computers would be vulnerable without Internet connection. > Have you ever seen what happens if you drop a USB stick in a company's parking > lot? This is not the case with many enterprises, finance, medical, military, banking and even local governments etc. where mounting of an external storage, CD/DVD or downloading is not an option or should pass IT people with a detailed examination of each file or package. In such well controlled and managed environments, you can find enough computers which are still using old systems like Win2000 and XP. Due to the mentioned issues with Win-10, which was not the case with Win-7, my bet is that Win-7 will have a lifetime of about 10 years with a good share still remaining but may be obscured from statistics since not seen over open Internet. jm4c to add. Kind regards, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [Interest] Code contributions via bug reports and forum posts
Hi, This is a very positive and long anticipated development. Excellent! Kind regards, Robert On Wed, May 16, 2018 at 12:20 PM, Tuukka Turunen wrote: > > > Hi, > > > > Contribution of source code is now allowed via Qt systems such as bug > reports and forums. Traditionally all source code contributions to the Qt > Project are governed via Contribution License Agreement (CLA), except > possibility given to the commercial license holders to provide bug fixes and > similar small modifications that The Qt Company has pushed into Qt. We have > now updated the Qt Account service terms to more clearly state that source > code can be contributed via the Qt systems. The preferred way to contribute > source code to the Qt Project is still via the CLA, according to the > contribution guidelines. But sometimes a user who has not accepted the CLA > has a patch that would, for example, fix a bug in Qt. Providing such a patch > is now also possible via the Qt systems, for example via the bug reports or > forum posts. > > > > Please check a blog post for more information: > http://blog.qt.io/blog/2018/05/16/code-contributions-via-bug-reports-forum-posts/ > > > > Note that any existing source code in the systems is not covered, only items > pushed from now on. > > > > Yours, > > > > Tuukka > > > > > > > ___ > Interest mailing list > inter...@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Repository request: MaterialWidgets
Dear Iman, This is really a good idea to enhance QtWidgets by a modern style. Best wishes! Kind regards, Robert On Thu, Oct 26, 2017 at 10:42 AM, iman ahmadvand wrote: > Hi everyone. > > As you probably noticed before in mailing list, Qt MaterialWidgets is going > to bring new modern UI to classical QtWidgets > based on material design style with the aim of same look-and-feel on > multiple desktop platforms. You can think of it as MaterialStyle > in QML but in pure C++ implementation for those application which is not > going to migrate to a new area (like QML) for the > UI development or any other reason. So this will give the developers good > options for choosing the UI tool. > > With the purpose of contributing this module to Qt, I would like to have the > new repository created. > > Name of the project: Qt MaterialWidgets > Responsible person: Iman Ahmadvand > Email: iman72...@gmail.com > Desired repository name: qtmaterialwidgets > > NOTE: this is not just about idea, i already implemented a full-functional > and well-behaved ContinuousSlider(more on: > https://material.io/guidelines/components/sliders.html#sliders-continuous-slider) > and a few more widgets. > > Best Regards. > Iman. > > > ___ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development > ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt iOS - Customization of EditMenu
Hi, iOS developers are able to customize EditMenu (the one used to Select, Select All, Copy, Cut, Paste, Speak, etc.) using clear Apple's API. Once I've used the approach recommended by Richard Moe Gustavsen: https://bugreports.qt.io/browse/QTBUG-41275 that uses private API and is not working since Qt 5.5 Since that I cannot get rid from the standard items, for example, or provide my custom actions on selecting them. There is more mess related: https://bugreports.qt.io/browse/QTBUG-49426 Any clues or directions or the maintainer would like this to be filed as a feature request? Thank you in advance! Kind regards, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt for Android - The New Selection Handles Are Breaking Apps
Hi, Qt port for Android was developed by the great and efforts of Bogdan, Eskil and many others where I mem it was Qt-5.2 and 5.3 where it has started to be usable and Qt-apps were developed. It was steadily improving by Qt-5.4, 5.5, 5.6 and 5.7 with many new features, options and native elements added. Unfortunately, my widget apps have been broken by the good intentions feature: Selection Handles - which appeared first in Qt-5.8, and it is still broken in the LTS intended Qt-5.9. Unlike most other features, it comes not on demand, but as a part of any text area, and breaks the existing Qt-apps. Needless to say that expectation of any developer could be an option to exclude such an intrusive feature. However, this is not the case - there's no any API to get rid from it. Android Text Editing Widgets are totally broken: https://bugreports.qt.io/browse/QTBUG-62426 and Selection Handles with QML have many issues opened with many workarounds proposed, like: https://appbus.wordpress.com/2017/03/25/text-selection-handles-qt-5-8/ and issues: https://bugreports.qt.io/browse/QTBUG-58700 and some more. Rock&Roll is dead, but we and QWidgets are not, not yet. Android apps are coming to Chromebook Desktop and look there superior when based on QWidgets. With other people joining me as seen in the tickets above, I'd like to ask the maintainers to consider giving priority to: 1. Option to exclude Selection Handles from the appearance; 2. Fixing the issues with Selection Handles; 3. Optional, making an option to customize their appearance. Thank you in advance! Kind regards, Robert ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
