[Development] QScroller behavior with QAbstractItemView subclasses

Hi, In working on https://bugreports.qt.io/browse/QTBUG-64543 I've seen that the QAbstractItemView::autoScroll property interferes with QScroller managing the flick/scroll. The problematic behavior goes away if users of the API manually set this property to false on the instance of QAbstractIt

Re: [Development] CMake && QtCreator cross-compilation for ARM fails

FWIW, Denis: I feel your pain and agree that the Qt Company and Qt Project have a responsibility to make cross compilation with CMake just work out of the box when you have the necessary kits installed in QtCreator. There is absolutley no excuse for us not doing this. We as a company should be

Re: [Development] Build system for Qt 6

See: “deprecated” From: Development on behalf of Uwe Rathmann Sent: Wednesday, October 31, 2018 2:35:50 AM To: development@qt-project.org Subject: Re: [Development] Build system for Qt 6 On Tue, 30 Oct 2018 19:24:26 +, Adam Treat wrote: > Lars gav

Re: [Development] Build system for Qt 6

Lars gave a keynote saying pretty much the same. Simply is not true that we are planning major source compatible breakage for Qt6 so let's stop saying that. On 10/30/2018 03:19 PM, Thiago Macieira wrote: > On Tuesday, 30 October 2018 12:11:38 PDT NIkolai Marchenko wrote: >> > That's not going

Re: [Development] Repository request: HTTP server

What came of this? On 10/06/2017 07:10 AM, Fredrik de Vibe wrote: Hi all, We have recently been working on a research project looking into the possibilities for creating a lightweight server component that can easily enable Qt applications to serve over HTTP. We would like to make this work

Re: [Development] About our CI update notifications

NM, I figured out how to cancel it :P On 03/15/2018 11:57 AM, Adam Treat wrote: Speaking of... https://codereview.qt-project.org/#/c/223224/ That integration is stuck and I don't know how to stop it and restage it. Apparently, the Windows 7 (mingw53-x86) VM crashed and COIN is not awa

Re: [Development] About our CI update notifications

https://bugreports.qt.io/browse/QTQAINFRA-1748 Anyone know how to stop the integration so I can restage? Cheers, Adam On 03/15/2018 09:35 AM, Adam Treat wrote: I would not regard this as excess spam at all. It is important to know when the CI is not available and what the status is. If a resta

Re: [Development] About our CI update notifications

I would not regard this as excess spam at all. It is important to know when the CI is not available and what the status is. If a restart or scheduled update of any kind requires to restage commits for COIN, please include that info. On 03/15/2018 04:26 AM, Tony Sarajärvi wrote: Hi We’re try

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

"If many users spend much time doing a "thing", does that mean that this is most important to them? Or that it is most fun to do?" Personally, I think we can table the discussion of how to interpret non-existent data for a plug-in that does not exist in a thread about whether to open a repo. __

Re: [Development] [Qt-creator] Requesting repository for telemetry plugin in Qt Creator

+1 to playground This is open source... by all means experiment! As long as no laws are being broken and no licenses violated, then if their is an itch... scratch it! The person who codes decides. We can all judge the results by looking at the code. Useless to have stop energy about a plug-in t

Re: [Development] Qt branches & proposal how to continue with those

“stop doing patch releases for minor releases that are not LTS.” +1 _ From: Simon Hausmann Sent: Monday, January 29, 2018 3:16 AM Subject: Re: [Development] Qt branches & proposal how to continue with those To: Jani Heikkinen , Hi, I feel that we are generally g

Re: [Development] Setters: Clarifying the ownership

How about "transfer" On 01/19/2018 11:57 AM, Thiago Macieira wrote: On sexta-feira, 19 de janeiro de 2018 08:26:21 PST Philippe wrote: +20 years ago, the (good) Taligent crossplatform project, in its guideline, proposed: adopt() aka "take ownership" orphan() aka "release ownership" Given tha

Re: [Development] atomic commits across submodules

On 12/18/2017 05:24 AM, Jędrzej Nowacki wrote: On czwartek, 7 grudnia 2017 12:17:16 CET Adam Treat wrote: Hi, I think it is high time that we fix the underlying problem: supporting atomic commits across submodules. As I'm not against the idea, I'm not really fan of it either. T

Re: [Development] COIN failures on dev

pushing other than really mandatory fixes in bypassing the CI. It is very unfortunate that dev has been broken for a while, but work is ongoing to unblock it. Yours,     Tuukka *From: *Development on behalf of Adam Treat *Date: *Tuesday, 12 December 2017 at

Re: [Development] COIN failures on dev

? From: Simon Hausmann Sent: Tuesday, December 12, 2017 3:09:03 AM To: Adam Treat; development@qt-project.org Subject: Re: [Development] COIN failures on dev Hi, I find the easiest way to find the last successful integration for example for qt5.git dev is this

Re: [Development] COIN failures on dev

Thanksgiving. Can this possibly be correct?? Where is the dashboard showing the last successful integration for a given branch? On 12/11/2017 11:24 AM, Adam Treat wrote: Hi, For the past few business days we've all witnessed failures on dev branch like this: https://codereview.qt-projec

[Development] COIN failures on dev

Hi, For the past few business days we've all witnessed failures on dev branch like this: https://codereview.qt-project.org/#/c/213309/ Seems that something broke with provisioning on macOS or something. I see this https://codereview.qt-project.org/#/c/214045/ attempt to fix, but that is also

Re: [Development] Suggestion to add labels when changing API

On 12/08/2017 12:47 PM, Sergio Ahumada wrote: On 08.12.2017 16:50, Oswald Buddenhagen wrote: On Fri, Dec 08, 2017 at 04:15:10PM +0100, Sergio Ahumada wrote: On 08.12.2017 15:42, Adam Treat wrote: Relying upon qt5 submodule pins is the problem. The underlying issue is atomicity of commits

Re: [Development] Suggestion to add labels when changing API

On 12/08/2017 09:20 AM, Konstantin Tokarev wrote: 08.12.2017, 17:14, "Tor Arne Vestbø" : On 08/12/2017 14:54, Sergio Ahumada wrote:  an old concept that used to pin the sha1 of repo/module's dependency, eg   http://code.qt.io/cgit/qt/qtdeclarative.git/commit/sync.profile?id=ab6b6b7c7ab544

Re: [Development] Suggestion to add labels when changing API

Relying upon qt5 submodule pins is the problem. The underlying issue is atomicity of commits. Oswald is right. We need to have a way to provide atomic commits across modules at least the CI should see these as atomic and integrate accordingly. On 12/08/2017 09:20 AM, Konstantin Tokarev wrote:

Re: [Development] Suggestion to add labels when changing API

Hi, I think it is high time that we fix the underlying problem: supporting atomic commits across submodules. Once this is done we should revert our CI to test changes against latest version of all modules. As for how this could be done: * Adopt something like Google's repo tool: https://co

Re: [Development] Nominating Maintainers of qt3dstudio/qt3dstudio

+1 On 11/02/2017 08:11 AM, Lars Knoll wrote: Hi Pasi, I fully support this. Qt 3D Studio is a big piece that TQtC just open sourced earlier and it’s good to get a defined maintainer structure for that project. Cheers, Lars On 2 Nov 2017, at 12:48, Pasi Keränen >

Re: [Development] Future of QBS

A few points: * Unless you are worried about building software with possibly infinite dependencies, infinite build products, then a non-Turing complete language that just lacks general recursion will be sufficiently expressive to meet your needs. In particular, this means those vaguely worryi

Re: [Development] Future of QBS

Prolog is turing-complete and hence can be used to construct programs which do not terminate. On 10/16/2017 09:42 AM, Konstantin Tokarev wrote: 16.10.2017, 16:17, "Adam Treat" : You'll need a strongly normalizing language for that which does not allow general recursion. Som

Re: [Development] Future of QBS

You'll need a strongly normalizing language for that which does not allow general recursion. Something built on the simply typed lambda calculus, but with added syntactic sugar would do. On 10/16/2017 09:08 AM, Ulf Hermann wrote: I have no real experience with Meson, but at least it has follow

Re: [Development] Speeding up the review process (was: PostgreSQL cross compile for Pi)

+1 I also really appreciate when a reviewer is up front about the steps necessary to get the patch over the finish line. And if you are just doing a drive-by review pointing out all the mistakes, but not willing to +2 in the end then please state that up front as well. To be clear, I'm not ag

Re: [Development] Should QFileSystemWatcher be thread-safe? (Qt 5.8.0)

Simon just gave a talk about signals and slots on different threads and the internals of how Qt handles this at CppCon in Seattle yesterday. I would suggest you have a look at the video of his presentation when it comes out. You could also look at the documentation: http://doc.qt.io/qt-5/thread

Re: [Development] Let's please drop MSVC 2013 for 5.10

On 06/23/2017 03:23 PM, Marc Mutz wrote: [forgot to CC list] On 2017-06-23 19:50, Thiago Macieira wrote: On Friday, 23 June 2017 09:17:55 PDT Marc Mutz wrote: The above argument makes no sense to me. What value does quoting download numbers for 5.9, an LTS, have, to argue about dropping the

Re: [Development] syncqt.pl in C++

On 03/07/2017 03:54 PM, Thiago Macieira wrote: Same here, though I have also to concede that breaking the status quo (to quote Jake's tweet) is sometimes a good idea. Teambuilder -- to name another Trolltech project that had nothing to do with qt -- was a couple of orders of magnitude better th