Re: [Development] Should QObject::event() be protected or public?

On 3/15/24 18:09, Marc Mutz via Development wrote: I like simple rules. "Overrides should have the same access level as the initial virtual function." is a simple rule. But it makes no sense in general. The base class is the interface, and overrides should have the least possible visibility

Re: [Development] How to document API only deprecated in future Qt versions

On 9/15/23 09:36, Kai Köhne via Development wrote: The methods are formally marked as deprecated for Qt 6.10. But the methods are already in the '-obsolete' page for Qt 6.6, which leaves the API in a weird in-between state. Radical idea: Treat all deprecated functions as if they didn't

Re: [Development] Do we need VS2019 for Qt 6.6?

On 2/2/23 16:38, Vladimir Minenko wrote: In 2022 and 2023, around 24M builds ran on Windows in around 600K unique installations worldwide which had at least 10 builds in this period of time. Not even a single one used MSVC2022. That's difficult to believe. I'm inclined to think the version

Re: [Development] New Qt example development guideline and revamping examples

On 1/18/23 19:56, A. Pönitz wrote: As a data point, even at it's height of .ui usage, Qt Creator (which is a "namespace aware" code base, see https://wiki.qt.io/Qt_In_Namespace) needed the QT_*_NAMESPACE for about 30 of its >200 .ui classes, and that in the presence of ~680 places where it was

Re: [Development] Qt 5.12.12 branches disappeared from code.qt.io?

On 1/12/23 01:24, Thiago Macieira wrote: On Wednesday, 11 January 2023 15:29:11 PST Jon Trulson wrote: Will these be returning at some point? No. Out of curiosity: Who gains what by removing branches? Christian ___ Development mailing list

Re: [Development] Nominating Marcus Tillmanns as Approver

On 11/22/22 22:27, A. Pönitz wrote: I'd like to nominate Marcus Tillmanns as an approver for the Qt project. +1 Christian ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] Using '#pragma once' instead of include guards?

On 10/10/22 17:13, Thiago Macieira wrote: The biggest problem we used to have was installing builds that had include paths pointing to both the source and installation directory. With preprocessor guards, only one of the two would actually get included; with #pragma once, the files are actually

Re: [Development] Nominating Sona Kurazyan as maintainer of qt5compat

+1 On 1/18/22 15:10, Cristián Maureira-Fredes wrote: Hello, I would like to nominate Sona as maintainer [1] for the qt5compat module, which at the moment doesn't have one. Even if it's a special module we have around only for Qt6, we need a responsible person in charge of it. She has been

Re: [Development] Qbs development

On 9/15/21 1:03 PM, Oswald Buddenhagen wrote: in this case, you personally instructed the maintainer to do only minimal maintenance work (which he does an excellent job at). he has repeatedly made clear that he has exactly *zero* interest in the strategic direction of qbs, and is letting "the

Re: [Development] Windows maintainer change

+1 On 6/15/21 9:27 AM, Oliver Wolff wrote: Hi all, I would like to propose a change in Qt's Windows maintainership. I think that everybody knows, that Friedemann has been doing a great job maintaining the Windows platform specifics in Qt's code base. He wants to focus on Qt for Python now

Re: [Development] Qt6 repo

On 1/13/21 11:46 PM, Thiago Macieira wrote: Like I said above, the latest tip of the branch for every single module. This recipe has worked for me for 10 years. I don't believe you. Christian ___ Development mailing list

Re: [Development] Nominating Max Goldstein as an approver

On 12/14/20 9:13 AM, Ulf Hermann wrote: I would like to nominate Max Goldstein as an approver for the Qt Project. +1 Christian ___ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development

Re: [Development] qsizetype and classes working with QStrings or QList

On Mon, 24 Aug 2020 14:45:19 +0300 Ville Voutilainen wrote: > On Mon, 24 Aug 2020 at 12:17, Mathias Hasselmann > wrote: > > >> C++ also has a solution for that problem: > > >> https://herbsutter.com/2013/08/12/gotw-94-solution-aaa-style-almost-always-auto/ > > > That non-solution is terrible.

Re: [Development] QProperty and library coding guide

On Thu, 16 Jul 2020 10:32:08 + Edward Welbourne wrote: > > [...] let me first give an introduction here, and answer some of your > > question. > > I have turned a large chunk of that into > https://wiki.qt.io/QProcess Are you sure about the URL? Christian

[Development] Nominating Ivan Komissarov as approver

Hello, I'd like to nominate Ivan Komissarov as an approver. Ivan has been doing valuable work in the qbs project for a while now, both as a contributor and a reviewer. I trust him to use his approver rights responsibly. His commits can be found here:

Re: [Development] Stepping down as moc maintainer.

On Tue, 5 May 2020 07:43:27 + Lars Knoll wrote: > I’m happy to say that I have a great candidate who’d be willing to take over > the maintainership. Fabian Kosmale would be interested in taking over from > Olivier. He has been working on a couple of features for the moc over the > last

Re: [Development] A modest proposal: disable lower-case keywords (emit, foreach, forever, signals, slots) by default

On Fri, 21 Feb 2020 15:00:53 +0200 Ville Voutilainen wrote: > On Fri, 21 Feb 2020 at 14:58, Sérgio Martins wrote: > > > Why do I need to know that it's a signal being emitted? How is that > > > "vital information"? I could just as well > > > invoke any other callback, but I find myself not

Re: [Development] Qt5.15 deprecating & Qt6 removing QProcess::setupChildProcess

On Tue, 18 Feb 2020 11:17:38 + Edward Welbourne wrote: > > - of the 6 times I can find of QProcess being derived from in Qt & Qt > > Creator, 5 are to override setupChildProcess anyway and the last one > > is in tst_QProcess > > Does anyone have sources from outside Qt project that are

Re: [Development] Broken RNG on AMD Ryzen CPUs affect QTemporaryFile, Qt IFW

On Tue, 18 Feb 2020 19:35:53 +0800 Sze Howe Koh wrote: > See > https://forum.qt.io/topic/111473/maintenance-tool-error-cannot-open-file-for-writing-no-error/ Probably the same as https://bugreports.qt.io/browse/QTBUG-77375. > Is this worth a post on the Qt Blog? I foresee many frustrated and

Re: [Development] Changes to Qt offering

On Mon, 27 Jan 2020 19:09:43 +0100 Giuseppe D'Angelo via Development wrote: > Il 27/01/20 16:57, Benjamin TERRIER ha scritto: > > *We do hope that this eases your concerns, and that we can continue > > with your trust*. > > > >

Re: [Development] Stepping down as Qt for macOS maintainer (but don't worry)

On Mon, 9 Dec 2019 11:33:16 + Morten Sørvig wrote: > I’d like to formally step down as Qt for macOS maintainer, and suggest that > Tor Arne Vestbø takes over in my place. He’s already maintaining Qt for iOS > (and QPA), and has done a lot of good work on macOS over the past couple of >

Re: [Development] Assistant WebKit/WebEngine support

On Thu, 27 Jun 2019 08:47:07 +0300 Alberto Mardegan wrote: > On 27/06/19 04:47, Lars Knoll wrote: > > > > Yes, Webengine uses some memory. But is that really a problem on developer > > machines? > > Yes. The more RAM you use for surfing documentation, the less RAM you > have for building. I

Re: [Development] Assistant WebKit/WebEngine support

On Wed, 26 Jun 2019 11:24:30 + Riitta-Leena Miettinen wrote: > 3. Should the same style be used online and offline? > > For 3), we always answered „yes“, because we felt that the use cases for > reading documentation on the web or using it within Qt Creator next to the > Code editor

Re: [Development] Views

On Thu, 06 Jun 2019 13:46:12 +0200 "Mutz, Marc via Development" wrote: > On 2019-06-06 12:24, Ola Røer Thorsen wrote: > > tor. 6. jun. 2019 kl. 10:21 skrev Vitaly Fanaskov > > : > > > >> Qt is GUI framework. Not only, yes, but this is the main purpose. > >> +/- > >> 10MB is almost nothing for

Re: [Development] Deprecation/removal model going into Qt 6

On Sat, 1 Jun 2019 14:36:12 +0200 André Pönitz wrote: > On Fri, May 31, 2019 at 01:24:13PM +, Volker Hilsheimer wrote: > > The overall goal here is to make sure that we don’t have to carry > > poorly designed architecture or APIs around with us throughout the Qt > > 6 series, and as long as

Re: [Development] unique_ptr and Qt, Take 2

On Sat, 04 May 2019 09:06:39 +0200 Allan Sandfeld Jensen wrote: > On Samstag, 4. Mai 2019 00:43:10 CEST Thiago Macieira wrote: > > On Friday, 3 May 2019 13:00:52 PDT Иван Комиссаров wrote: > > > Which should be considered bad practice and banned on an API level > > > > No way. > > > > Are you

Re: [Development] Supporting helper functions in auto tests by providing throwing Qt Test macros

On Tue, 2 Apr 2019 15:14:38 + Mitch Curtis wrote: > As described in https://bugreports.qt.io/browse/QTBUG-66320, currently Qt > users are on their own if they want to call helper functions that can fail a > test. The reason is documented: > > Note: This macro can only be used in a

Re: [Development] On deprecating functions

On Mon, 4 Mar 2019 22:27:42 +0100 André Pönitz wrote: > (5) Use #if (QT_VERSION / QT_VERSION_CHECK. To "fix" perfectly > valid code *for cosmetical reasons*? DUH! Example: https://codereview.qt-project.org/#/c/252715/1 was necessary because of the immediate deprecation of an existing function

Re: [Development] CMake Workshop Summary

On Mon, 25 Feb 2019 08:13:29 + Jedrzej Nowacki wrote: > On Friday, February 22, 2019 7:18:36 AM CET Thiago Macieira wrote: > > But do note that our parallelism isn't that bad right now. > > It is not bad, but it is not great either :-). For example one needs to > _link_ > QtCore before

Re: [Development] New API design for file system operations

On Thu, 7 Feb 2019 16:03:30 + Volker Hilsheimer wrote: > Thoughts, ideas, and pointers to other frameworks that you believe provide a > good API are welcome here in this email thread before moving to a dedicated > JIRA ticket. My personal pet peeve: Please, let's never again use the term

Re: [Development] New linguist maintainer nomination

On Mon, 7 Jan 2019 12:51:25 + Alex Blasche wrote: > After Ossi stepping down as maintainer for Linguist and related tools > (lupdate/lrelease) I would like to propose Kai Koehne to take over. Kai has a > long history working on Qt and even more specifically with Qt's translation > tools.

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

On Thu, 13 Dec 2018 12:47:08 +0100 Kevin Kofler wrote: > Christian Gagneraud wrote: > > On Thu, 13 Dec 2018 at 12:27, Kevin Kofler wrote: > >> (so, unlike QBS, it does not depend on Qt, which would mean a circular > >> dependency when building Qt), > > > > qmake has this problem, yet it's

Re: [Development] automated bulk change closing old issues in the "Need more info" state

On Mon, 19 Nov 2018 16:01:32 + Kai Koehne wrote: > > -Original Message- > > From: Development > project.org> On Behalf Of Uwe Rathmann > > Sent: Monday, November 19, 2018 4:10 PM > > To: development@qt-project.org > > Subject: [Development] automated bulk change closing old issues

Re: [Development] Build system for Qt 6

On Wed, 31 Oct 2018 10:44:43 +1300 Christian Gagneraud wrote: > On Wed, 31 Oct 2018 at 10:27, Thiago Macieira > wrote: > > On Tuesday, 30 October 2018 13:56:45 PDT NIkolai Marchenko wrote: > > The only thing I'm criticising is that its proper chance involves Qt being > > the > > guinea pig.

Re: [Development] QUIP 12: Code of Conduct

On Thu, 25 Oct 2018 19:39:45 +0200 André Pönitz wrote: > On Thu, Oct 25, 2018 at 09:51:00AM +0200, Volker Krause via Development wrote: > > We do have a Code of Conduct at KDE for about 10 years now, and this hasn't > > led to abuse of power, suppression of free speech, racism against white >

Re: [Development] QtScxml module maintainer change

On Tue, 4 Sep 2018 11:48:24 + Erik Verbruggen wrote: > I'd like to propose Ulf Hermann as the new maintainer of the QtScxml module. +1 Christian ___ Development mailing list Development@qt-project.org

Re: [Development] QAbstractItemModel::setItemData behaviour

On Mon, 3 Sep 2018 09:03:06 + Luca Beldi wrote: > Gentle ping as I got no answers before. > > > Hi everyone, > While trying to submit a patch to fix QStringListModel::setItemData >

Re: [Development] Closing issues automatically with new keyword

On Tue, 7 Aug 2018 11:46:12 +0200 Frederik Gladhorn wrote: > I've spend a bit of time writing a script that monitors gerrit and the git > repositories to update JIRA statuses. It's not quite done yet, but getting > there. > Basically it should be able to set the fixed version and close tasks

Re: [Development] Qt 6 buildsystem support requirements

On Thu, 2 Aug 2018 10:23:12 -0300 Lisandro Damián Nicanor Pérez Meyer wrote: > El jueves, 2 de agosto de 2018 10:03:04 -03 Oswald Buddenhagen escribió: > [snip] > > > > As for java in the loop - this is a a build system, how much does it > > > > matter with what it is written in if the

Re: [Development] Changing maintainer-ship for Qt Assistant, Qt Help and Qt Creator’s help Integration

On Mon, 28 May 2018 10:19:28 + Karsten Heimrich wrote: > officially I'm still  the maintainer of Qt Assistant & Qt Help and Qt > Creator’s help Integration. Since I actually no longer working on this code, > I propose Jaroslaw  Kobus as the new maintainer. Jarek has

Re: [Development] Naming convention for (scoped) enums

On Thu, 17 May 2018 08:14:15 + Alex Blasche wrote: > The naming conventions for enums state that each enum value name must repeat > a part of the enum Type name (for details see > https://wiki.qt.io/API_Design_Principles#Naming_Enum_Types_and_Values) > > In case

Re: [Development] Goodbye

On Fri, 9 Feb 2018 21:14:22 +0100 Jake Petroules wrote: > Steve Jobs once said: > > > “I have looked in the mirror every morning and asked myself: "If today were > > the last day of my life, would I want to do what I am about to do today?" > > And whenever the answer has

Re: [Development] Nominating Kari Oikarinen for Approver Status

On Fri, 9 Feb 2018 14:18:56 +0100 Rainer Keller wrote: > I'd like to nominate Kari Oikarinen for approver status in the Qt Project. +1 Christian ___ Development mailing list Development@qt-project.org

Re: [Development] Getting build flags for platforms without pkg-config

On Mon, 30 Oct 2017 09:00:46 +0100 Jeandet Alexis wrote: > Le dimanche 29 octobre 2017 à 15:57 -0700, Thiago Macieira a écrit : > > On domingo, 29 de outubro de 2017 14:57:44 PDT Jeandet Alexis wrote: > > > Hello, > > > > > > Previously I asked about getting

Re: [Development] Future of QBS

On Wed, 18 Oct 2017 08:46:34 +0200 Jeandet Alexis wrote: > Le mardi 17 octobre 2017 à 17:45 +0200, Giuseppe D'Angelo a écrit : > > (Small story: when I presented Qt Creator at CppCon last year, > > people's > > reactions were always these two: > > > > 1) "Oh,

Re: [Development] Future of QBS

On Tue, 17 Oct 2017 17:23:17 +0200 Ulf Hermann wrote: > >> Exactly. The halting problem can be worked around pragmatically. > > > > ... at the price of getting different build results based on CPU speed ... > > > > Your fast desktop CPU crunches through the JS and you get

Re: [Development] Future of QBS

On Mon, 16 Oct 2017 01:23:51 +0800 Ben Lau wrote: > I am still new to QBS, but I think it is better than CMake too. However, I > think it has missed a critical feature - A simple way to run custom script. > > For example, run a script to call external command (not a product

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

On Fri, 13 Oct 2017 15:13:16 +0200 Viktor Engelmann wrote: > >>  4. I don't think we need to be as paranoid towards contributions > >> from > our own employees as we need to be towards external > >> contributions. > > Anyone with approver rights should be aware of

Re: [Development] QLowEnergyController and obsolete ctor

On Tue, 29 Aug 2017 11:18:02 + Alex Blasche wrote: > Hi Martin, > > > -Original Message- > > From: Development [mailto:development- > > bounces+alexander.blasche=qt...@qt-project.org] On Behalf Of Martin Koller > > > In Qt 5.9 I find that the following

Re: [Development] ChangeLog entries and reverted commits

On Mon, 31 Jul 2017 11:11:41 +0200 Friedemann Kleint wrote: > have a look at https://codereview.qt-project.org/#/c/201164/ for the > Perl script. Are the two scripts competing or do they complement each other in some way? Christian

Re: [Development] Introductions?

On 04/28/2017 04:05 PM, Edward Welbourne wrote: > On 25 April 2017 at 10:09 I wrote (inter alia): >> [...] the same is relevant for any approver or maintainer: perhaps we >> should tweak our process for introducing candidates for those stations >> within the community; ask that each introduce self

Re: [Development] QProcess fork() failure and overcommit

On 03/07/2017 10:05 PM, Thiago Macieira wrote: > Em terça-feira, 7 de março de 2017, às 17:53:41 CET, René J.V. Bertin > escreveu: >> One tends to forget (I do at least) that spawning a little helper process >> can be quite expensive, sometimes prohibitively so. Makes you wonder what >> kind of

Re: [Development] QProcess fork() failure and overcommit

On 03/07/2017 02:54 PM, René J. V. Bertin wrote: >> This kind of stuff seems to happen when the parent process has allocated >> a lot of memory. I haven't debugged into it, but one idea might be that > > What is a lot here? Typical usage for one of the KDevelop sessions that tends > to > be

Re: [Development] QProcess fork() failure and overcommit

On 03/07/2017 02:04 PM, René J.V. Bertin wrote: > I have a bit of an intriguing issue I hope someone here could help me > understand. If not, sorry for the noise. > > I'm seeing occasional QProcess failures where QProcess:waitForStarted() fails > and gives rise to errors like > >

Re: [Development] Naming of path/directory-related environment variables in Qt

On 11/11/2016 04:13 PM, Mitch Curtis wrote: > I'd like to establish some kind of convention for naming > path/directory-related environment variables in Qt, with the hope that it > could be set in stone with e.g. one of these newfangled QUIPs. > > Pelagicore (via Gordan) kindly contributed a

Re: [Development] Removal of some of the blacklisted (non-working) autotests?

On 11/04/2016 09:10 AM, Jędrzej Nowacki wrote: > In your email you wrote that blacklisted is just a burden for CI. In > general it is true, but mark that currently they are compiling and they are > _not_ crashing. So they do contribute to the quality of Qt. On the other hand > they

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

Stephen Kelly wrote: > My previous guess about Qbs being able to generate unknown files in a > particular location and then determine them by an 'ls' equivalent, moc > them and compile everything is not something Qbs would be able to do. I'm having trouble parsing this, but if you mean that

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

Stephen Kelly wrote: >> There is no input file. There is only an input number. The task is from >> Bo, who gave it as a simplified example. > Oops, I'm wrong here. Bo said to read the number from a file. > I don't think that changes anything though regarding dynamic build graph > being an

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

[Sorry about the formatting, using outlook] Stephen Kelly wrote: > Here's the CMake version: [ ... ] > execute_process( > COMMAND python ${CMAKE_CURRENT_SOURCE_DIR}/generator.py --list > ${CMAKE_CURRENT_BINARY_DIR}/genoutput 5 > OUTPUT_VARIABLE fileList > ) How do you know

Re: [Development] Notes on "Qt Build Systems" @ QtCon 2016

On 09/08/2016 02:03 PM, Bo Thorsen wrote: > Ok, go try it. Create a simple python or perl script that reads a file. > The file just has a single number N inside it. And based on N the script > outputs those files: > > server.h > method1.h > method2.h > ... > methodN.h > > Inside method1.h you

Re: [Development] Use of Standard Library containers in Qt source code

On 07/01/2016 08:36 PM, Thiago Macieira wrote: For some time now, we've had a flurry of changes to Qt source code that uses the Standard Library's containers and algorithms, in the name of performance and often code size gains. I'm not disputing that there is a gain. But I am wondering about

Re: [Development] commas in ctor-init-lists

On 06/03/2016 02:52 PM, Thiago Macieira wrote: I've seen a lot of code do: #ifdef FOO if (foo) { // something } else #endif if (bar) { // something else } else { // default } This kind of thing is an

Re: [Development] RFC: lambda or lambda return from lambda?

On 02/01/2016 03:10 PM, Marc Mutz wrote: The point of giving names to things (variable, functions, classes) in programming is so you don't need to look at the implementation all the time to see what it's doing. You only need to look when you want to see _how_ it's doing what it does. So if you

Re: [Development] RFC: lambda or lambda return from lambda?

On 02/01/2016 11:08 AM, Marc Mutz wrote: We're seeing increasing use of lambdas in dev, and I'm a bit unhappy about the result. E.g. (not picking on Anton here, I have done the same before): auto firstEqualsName = [](const QPair ) { return

Re: [Development] Suggestion for change on how blockers are marked in Jira

On 11/27/2015 11:46 AM, Eskil A. Blomfeldt wrote: We've had a few informal discussions locally about the current process of manually adding bugs to a meta-task in order for them to be considered blockers for a particular release. Wouldn't it be more practical if this was baked into the

Re: [Development] Avoid overloading of 'error'

On 06/10/2015 06:42 PM, Thiago Macieira wrote: On Wednesday 10 June 2015 15:14:07 Hausmann Simon wrote: Hi, I think renaming the getter to lastError is nice! I however do like error as signal name and it looks good in qml as onError:... onError screams of Basic to me... ON ERROR GO

Re: [Development] Q_OBJECT and override

On 06/04/2015 04:52 PM, Konstantin Ritt wrote: #define Q_OBJECT \ public: \ Q_OBJECT_CHECK \ QT_WARNING_PUSH \ Q_OBJECT_NO_OVERRIDE_WARNING \ static const QMetaObject staticMetaObject; \ virtual const QMetaObject *metaObject() const; \

[Development] Q_OBJECT and override

Hi, as anyone who uses clang has probably already noticed, this compiler has recently added -Winconsistent-missing-override to the collection of flags enabled via -Wall. As a result, you now get literally thousands of warnings when building any non-trivial Qt project. This is because the

Re: [Development] QTextStream::readLine(0) is an ambiguous overload in 5.5

On 05/17/2015 09:57 PM, Giuseppe D'Angelo wrote: On Sun, May 17, 2015 at 9:55 PM, Smith Martin martin.sm...@theqtcompany.com wrote: How do you get bitten by an out-reference? As usual, because at call site I didn't realize the argument was actually being modified. Compare

Re: [Development] RFC: RAII for property changes

On 04/15/2015 05:12 PM, Matthew Woehlke wrote: [Valid points about the inconsistent state of the object elided.] On 2015-04-15 10:58, André Somers wrote: What if that slot [connected to the instance property changed signal] triggers something that ends up deleting the instance? Then the

Re: [Development] [RFC] more gerrit codereview scores?

On 03/06/2015 05:42 PM, Oswald Buddenhagen wrote: 1) i'd like to propose the introduction of the code review score -3. rationale: it's quite common that a particular patchset is so broken that it must not be merged. this is typically done by giving a -2 score, in particular when it's needed

Re: [Development] QtCore missing check for memory allocation

On 02/25/2015 04:30 PM, Giuseppe D'Angelo wrote: Il 25/02/2015 13:35, Ulf Hermann ha scritto: I noticed that in qglobal.h Q_CHECK_PTR may be a noop in case QT_NO_DEBUG is set. Q_CHECK_PTR is used to check if memory allocations succeeded (e.g. QVector::reallocateData). Until

Re: [Development] Upgrading the sources to C++11 keywords (Q_NULLPTR, etc.)

On 02/10/2015 05:33 PM, Olivier Goffart wrote: Note that some STL implementation (most notably the GNU one) use implicit sharing for std::string I thought that was prohibited in C++11? Christian ___ Development mailing list

Re: [Development] Compiler warnings

On 10/17/2014 08:48 AM, Kurt Pattyn wrote: As we are developing for aerospace, avionics, defence and healthcare, we are confronted on a daily basis with a lot of very stringent rules that we have to comply with (irrespective if some people might find these rules outdated, stupid, ridiculous

Re: [Development] Compiler warnings

On 10/17/2014 01:06 PM, Milian Wolff wrote: I think you are missing something: enum Foo { Bar = 1, Baz = 2 }; Foo foo = static_castFoo(3); If you start to guard against this kind of stuff, where does it end? void f(void *p); f(reinterpret_castvoid *(5)); Is f supposed to catch that?

Re: [Development] Building Creator's qbsprojectmanager and qbsplugin with external qbs

On 10/04/2014 08:36 PM, Lisandro Damián Nicanor Pérez Meyer wrote: Hi! A fellow maintainer in Debian has packaged qbs as a separate source. So we though of building qtcreator's qbsprojectmanager and qbs plugin with it. This seems not supported right now out of the box Hm, what do you mean by

Re: [Development] clang-analyzer and qbs projects

On 09/29/2014 09:29 AM, gorthaue...@yandex.ru wrote: Is there any way to analyze qbs projects with clang-analyzer? A cursory glance at how clang-analyzer works suggests it should be enough to set cpp.compilerPath to the location of the c++-analyzer tool (for C++ projects) and make sure the

Re: [Development] Perceptions/Understandings of the QML language [was: Question about Qt's future]

On 04/28/2014 10:51 PM, André Pönitz wrote: I am tempted to suggest to reload http://www.classnamer.com/ until it contains Q, M, and L. Don't waste your time. I've checked the source code and found that the first word will never start with a 'Q'. Maybe we should fork it? Christian

Re: [Development] Nominating Jake Petroules as approver

On 04/15/2014 07:13 PM, Thiago Macieira wrote: I'd like to nominate Jake Petroules as approver. +1 Christian ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt5 does not build with Python 3.3 anymore

On 01/29/2013 12:34 PM, Дмитрий Волосных wrote: It happens somewhere while building WebKit, when build script starts to use tools from gnuwin32\bin. The failure I saw on my machine was due to some deprecated use of a print format string. I took the easy route and directed the build process to

Re: [Development] QtCreator Generic Linux Device plugin questions

On 01/12/2013 05:11 PM, a.gra...@gmail.com wrote: I'm trying to understand how the Generic Linux Device plugin of QtCreator works and I've some questions to ask, to understand if it already does what I need or if I need to fork it and customize for my needs. Note that this question should

Re: [Development] QtCreator Generic Linux Device plugin questions

On 01/14/2013 01:51 PM, a.gra...@gmail.com wrote: There is a pre-configured upload step in the plugin, which uses SFTP. See the deployment part of your project for the details. This currently works only for qmake-based projects. The files to deploy are specified via the .pro file's INSTALLS

Re: [Development] Is QtConcurrent's code generator still in use?

On 11/14/2012 12:17 PM, Sorvig Morten wrote: QtConcurrent is done. The implementation is not good enough to be used as a base for further development. Can you be a bit more specific? What are the general problems and why can't they be easily solved? Christian

Re: [Development] Issues with qmake and subdirs template

On 10/17/12 17:27, Wehmer, Matthias wrote: I'm currently trying to organize my project with qmake. The compiling itself works pretty smooth so far, but somehow I have problems with make install. To be more concrete: I have organized everything with the subdirs template and in one directory

Re: [Development] Qt Playground - Command Line Parser experiment

On 03/09/2012 12:36 AM, ext Laszlo Papp wrote: I would like to experiment with a command line parser in Qt Playground. The topic and the use case were more or less discussed previously on the qt5-feedback mailing list around last October. It is not a separate module, but class(es). The name