Re: [Development] Another integer typedef OR how to prepare for 64-bit in Qt 5

Hi, > On 2 Nov 2018, at 16:02, Thiago Macieira wrote: > >> On Friday, 2 November 2018 06:50:50 PDT Jedrzej Nowacki wrote: >>> On Friday, November 2, 2018 4:42:52 AM CET Thiago Macieira wrote: >>> >>> We have a lot of API that, for Qt 6, we've already decided to extend to >>> 64-bit on 64-bit p

Re: [Development] Opinions on QTBUG-71545

Hi, On 05/11/2018 20:56, Elvis Stansvik wrote: Den mån 5 nov. 2018 kl 20:32 skrev Konstantin Shegunov : Hello, Since we couldn't agree, I'd love to see some more opinions about this one.[1] I may be missing some detail, but I think what Thiago says makes sense. When children are destroyed, yo

[Development] [SPAM] Re: QDialog vs QPushButton and it's autoDefault default

Spam detection software, running on the system "mx.qt-project.org", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. C

Re: [Development] Qt6 qml

Hi, On 02-10-19 09:39, Nicola De Filippo wrote: Hi, is possible think will Qt6/qml c++ binding similar to swiftui? Perhaps it would be helpful to explain a bit more about how such things work in swiftui, for those not familiar with it? André ___

Re: [Development] The age-old T* foo vs. T *foo

On 18/10/2019 02:37, Kevin Kofler wrote: Ville Voutilainen wrote: Since we are about to do a major version upgrade, should be stop being a special snowflake in the C++ world and start attaching pointer-stars and reference-ampersands to the type instead of to the variable? No, because it is syn

Re: [Development] Two-digit dates: what century should we use ?

Hi, On 05-11-19 14:44, Edward Welbourne wrote: Hi all, Prompted by [0], I'm looking at what century to use for years, when the text being read is expected to be in a "short format" that only includes two digits. * [0] https://bugreports.qt.io/browse/QTBUG-74323 tl;dr - how do folk feel about (

Re: [Development] Two-digit dates: what century should we use ?

On 07-11-19 11:47, Edward Welbourne wrote: André Somers (6 November 2019 17:20) wrote I came to the conclusion that the sane behavior for interpreting dates depends on the semantics of what the date means. For instance, a birth date will always be a date in the past, ... except when it'

Re: [Development] Two-digit dates: what century should we use ?

On 08-11-19 11:15, Edward Welbourne wrote: André Somers (6 November 2019 17:20) wrote I came to the conclusion that the sane behavior for interpreting dates depends on the semantics of what the date means. For instance, a birth date will always be a date in the past, On 07-11-19 11:47, Edward

Re: [Development] qHash / QHash changes

Op 19-3-2012 10:42, Thiago Macieira schreef: > They shouldn't rely on that at all. The documentation of QHash says > that it produces an arbitrary but stable[1] order. > [1] note that the order is stable. Two hashing tables with the same > elements must produce the same order. If I understood

Re: [Development] Towards a Qt 5 beta: Documentation

Op 12-4-2012 15:12, casper.vandonde...@nokia.com schreef: > Modularizing the documentation is a process that will move a lot of files > around and make some things impossible. > The biggest consequence will be that we will have the same dependency > chain as when compiling the modules. > E.g. not a

Re: [Development] The place of QML

Op 19-4-2012 8:18, Robin Burchell schreef: > On Thu, Apr 19, 2012 at 8:11 AM, Girish Ramakrishnan > wrote: >> As for a blog, why is there no qt-project blog? It would be great to >> have people blogging about Qt development related stuff. > presumably because it's a bit hard to define who gets ac

Re: [Development] #qt-labs IRC channel on irc.freenode.net

Op 14-5-2012 17:26, Carl Schumann schreef: > Qt developers, > > I am struggling to access the #qt-labs IRC channel on > irc.freenode.net. I am on a Windows Machine. Any recommendations for > a Windows IRC client please? Thanks for any help. > > Sincerely, > Carl Schumann > I use Quassel IRC,

Re: [Development] The place of QML

Op 16-5-2012 1:31, André Pönitz schreef: > On Tue, May 15, 2012 at 07:13:19AM -0700, BRM wrote: >>> From: Donald Carr >>> [...] This is out of a sample set of 110 people, which is >>> infinitesimally small in comparison to the Qt user base. It would >>> be a stretch to call this a statistically si

Re: [Development] looking for chart examples

Op 21-5-2012 22:56, Purdy, Edgar schreef: Are there any examples on line for implementing the qt chart widget?I need to implement 15 charts on a single panel. I think you should ask your question in the inter...@qt-project.org mailinglist instead. This ML is about developing Qt *itself*

Re: [Development] Proposal: Change Qt Slogan

Op 22-5-2012 10:53, d3fault schreef: > I think we need a slogan change so as not to lie to our users. Could you please stop trolling now? This is not constructive anymore. Your comments have been heard, judging by the amount of people who responded in your many topics in this list, the forum and

Re: [Development] Approver status

Hi, Op 25-5-2012 8:27, lars.kn...@nokia.com schreef: > I agree with Andre. Currently we do not have any guiding criteria in > place, so it's probably difficult to judge when someone is ready to be > nominated as an approver. We've now had one or two cases where people > where being nominated a bi

Re: [Development] Approver status

Op 25-5-2012 9:34, André Somers schreef: > Hi, > > Op 25-5-2012 8:27, lars.kn...@nokia.com schreef: >> I agree with Andre. Currently we do not have any guiding criteria in >> place, so it's probably difficult to judge when someone is ready to be >> nominated as a

Re: [Development] Approver status

Op 25-5-2012 11:53, Sylvain Pointeau schreef: On Fri, May 25, 2012 at 10:55 AM, Laszlo Papp > wrote: > I think that defining fixed number of LOC or hours spend on > the project is not going to work. Please don't go there. I fully agree. I can understand th

Re: [Development] Becoming a Tier 1 platform and the CI System

Op 7-6-2012 13:28, Peter Kümmel schreef: > On 07.06.2012 08:35, Rohan McGovern wrote: >> Molkentin Daniel (Nokia-MP/Berlin) said: It means that the current CI infrastructure is operated by Nokia and can't have build nodes plugged in from outside of Nokia premises. So, if you need to

Re: [Development] Move QAction from QtWidgets to QtGui

Op 3-7-2012 15:07, Shawn Rutledge schreef: > On Tuesday wk27 2012 July 03 09:36:26 AM ext Anselmo L. S. Melo wrote: >> Hi, >> >> On 07/03/2012 05:06 AM, Davide Bettio wrote: >>> Hello, >>> >>> I've noticed that QAction hasn't been moved from QtWidgets module to >>> QtGui module, it would be really

Re: [Development] Move QAction from QtWidgets to QtGui

Op 3-7-2012 18:45, simon.hausm...@nokia.com schreef: > I'm not a fan of moving QAction back to QtGui, because there it would be a > class that cannot be used by itself. Out of the box it is only useful with > the containers in QtWidgets. Why could it not be used by itself? I would totally use it

Re: [Development] Move QAction from QtWidgets to QtGui

Op 3-7-2012 18:31, Tomasz Siekierda schreef: > Hi, > > just a quick note regarding this: > >> Would it not be possible to split QAction in two classes, just like > QApplication was split? We could perhaps create a QCoreAction > > I think a better name would be QSimpleAction. Runs off the tongue a >

Re: [Development] Proposal: Remove QML from Qt's code base (OR: Should it be a requirement that Qt Modules are interoperable?)

Op 4-7-2012 11:00, d3fault schreef: On Jul 4, 2012 1:18 AM, "Attila Csipa" > wrote: > >>replacement. There is no C++ equivalent of much of the functionality > > in QML, whereas everything you can do in a .ui file, you can do in C++. > > > > This is a bit of a red herr

Re: [Development] Abandoning the container changes

Op 5-7-2012 12:28, Thiago Macieira schreef: > We can add them, but I don't see a value in doing that if no one is using > them. They'll just increase build time. How could we use it, if it is not included? André ___ Development mailing list Development@

Re: [Development] Why don't we have notify signal for all of the properties?

Op 6-7-2012 12:45, Tr3wory schreef: > Hi all! > > I found the QML's property binding system really powerful, but as far > as I understand on the C++ side it relies on the property's NOTIFY > signal. > I know the notify signal is added around Qt 4.6, and as far as I > understand we couldn't add more

Re: [Development] Why don't we have notify signal for all of the properties?

Op 6-7-2012 13:30, Olivier Goffart schreef: > On Friday 06 July 2012 13:02:16 André Somers wrote: >> Op 6-7-2012 12:45, Tr3wory schreef: >>> Hi all! >>> >>> I found the QML's property binding system really powerful, but as far >>> as I understand

Re: [Development] State of the Qt Solutions Archive

Op 13-7-2012 15:29, Thiago Macieira schreef: > On sexta-feira, 13 de julho de 2012 14.33.18, Lukas Geyer wrote: >> I've fixed QtSingleApplication for Qt5 and created a merge request, just >> to find out that it's quite quiet there, with merge request beeing not >> seen (?) or at least discussed and

Re: [Development] state of Qt's Australia office

Op 1-8-2012 5:00, lorn.pot...@nokia.com schreef: > Hi all, > > We have received word that the Brisbane Australia office, consisting of the > teams working on Qt3D, QtDeclarative, QtMultimedia, QtSensors, and QtSystems > modules, as well as the CI/QA team for Qt, will be shut down. Our last day is

Re: [Development] Two bugs in the QIcon which broke my life.

Op 8-8-2012 10:30, Stephen Kelly schreef: On Wednesday, August 08, 2012 12:03:34 ? ??? wrote: > In the QIcon/QIconLoader there are 2 old bugs with patches. > > - https://bugreports.qt-project.org/browse/QTBUG-17953 > - https://bugreports.qt-project.org/browse/QTBUG-12874 > > >

Re: [Development] Two bugs in the QIcon which broke my life.

Op 8-8-2012 10:49, Stephen Kelly schreef: On Wednesday, August 08, 2012 10:35:15 André Somers wrote: > Op 8-8-2012 10:30, Stephen Kelly schreef: > > On Wednesday, August 08, 2012 12:03:34 ? ??? wrote: > > > In the QIcon/QIconLoader there are 2 old

Re: [Development] Idea: a qt-project subdomain for QML snippets

I don't quite see what this adds to the wiki that already has a snippets section. André Op 11 aug. 2012 om 00:27 heeft Mark het volgende geschreven: > Hi, > > Every once in a while you encounter some nice QML snippet which helps > you out, but will perhaps help others out as well if they jus

Re: [Development] Removing Wacom support in Qt5

Op 6-9-2012 9:41, Boudewijn Rempt schreef: > For me as an application developer, I wonder what the alternative > would be. I guess to write two platform specific event handlers myself > (win and X11, I cannot afford a Mac) and synthesize the > QTabletEvents... Do a fund raiser to get me some dif

Re: [Development] Removing Wacom support in Qt5

Op 10-9-2012 15:45, Boudewijn Rempt schreef: > I mean, there clearly are more important users of Wacom support in Qt than me > with Krita. Don't underestimate yourself ;-) André ___ Development mailing list Development@qt-project.org http://lists.qt-pro

Re: [Development] Qt wiki MinGW for 64 bit

Op 14-9-2012 11:55, niXman schreef: > Hello, > > Today, reading this(qt-project.org/wiki/MinGW-64-bit) note, I paid > attention to the fact that it refers to the need to edit qmake.conf > Qt5 for building 64-bit. > But yesterday, I have built Qt5 for 64-bit successfully without > changing qmake.con

Re: [Development] Fwd: Re: Proposing QSqlQuery syntax sugar

Op 19-9-2012 11:32, Andras Mantia schreef: > Thiago A. Corrêa wrote: > >> Hi, >> >>I'd like to propose a templated QSqlQuery::value in the same way >> QVariant::value works. This syntax suggar allows one to write: >> >>QSqlQuery query; >>... >>int myvalue = query.val

Re: [Development] bool QProcess::waitForFinished() Race Condition?

Op 26-9-2012 9:32, d3fault schreef: > I don't have a git clone and gerrit set up atm otherwise I'd submit > it. Can someone else do it for me? Well, this sounds like a fine time to get such a setup then? > And another semi-OT question relating to documentation: how are we > synchronizing wiki edits

Re: [Development] QThread usage/guidance

Op 7 okt. 2012 om 02:20 heeft Sze Howe Koh het volgende geschreven: > On Sun, Oct 7, 2012 at 4:13 AM, Giuseppe D'Angelo wrote: > On 6 October 2012 16:46, Kevin Krammer wrote: > > > > Because it clearly states that QTcpSocket instances returned by that method > > cannot be used from another t

Re: [Development] highlight/background colour of active tabs

Op 18-10-2012 19:36, Randolph D. schreef: > Hello > > in the tab widget several tabs have a background colour of dark-grey > and the active forground tab has the background colour of light-grey. > > This is misleading, as all apps with a mainframe have the colour of > light grey, so the active ta

Re: [Development] RFC: Qt Security Policy

Op 19-10-2012 3:50, slfj sfjie schreef: Also, the guy didn't even disagree with me. He pretty much reiterated the first post and said absolutely nothing. You disagreed with me for a little bit (CVE/Mitre), but getting around those problems is trivial by setting up a security-priv...@qt-proje

Re: [Development] Proposal: Time to decide what security policy the Qt Project will use (not Trolltech/Nokia/Digia)

Op 25-10-2012 9:18, d3fault schreef: < a big re-itteration of yet the same arguments> Indeed, time for a conclusion. Oh wait: Lars already gave that conclusion: http://lists.qt-project.org/pipermail/development/2012-October/007511.html Sorry that the conclusion doesn't match your ideas of the ide

Re: [Development] Common base class for all socket types

Op 6-11-2012 10:26, d3fault schreef: > "a common base class is an interesting idea. But it’s a moot point > since we have to maintain binary compatibility until Qt 5. So > QAbstractSocket cannot change. We’ll revisit the issue when Qt 5 > development starts, but that’s a long way in the future". (

Re: [Development] Proposing new mailing list: qt-l...@qt-project.org

Op 20-11-2012 16:04, Tanilkan Sinan schreef: > Hi, > > I would like to propose that we establish the mailing list: > qt-l...@qt-project.org, to take over for the previous qt-l10n list. > > We believe there are people who are interested in localization, that do not > follow the developer mailing l

Re: [Development] New mailing list: web_AT_qt-project.org created

Hi, Op 26-11-2012 12:12, Verma Gurudutt schreef: Hi I am really happy to inform you all that new mailing list web_AT_qt-project.org is created now. We will be discussing open governance model of web development related stuffs for qt-project.org here and proposal for this was made few days

Re: [Development] QAction-like API for QML

Op 11-12-2012 4:39, Alan Alpert schreef: > QAction served widgets well as an abstraction for an "Action" which is > exposed to the UI in a platform specific manner. This was shared > between menus and toolbars and some other things. I think we'll need > something similar for QML, so that the QtQuic

Re: [Development] Settings API for QML

Op 11-12-2012 16:37, Bache-Wiig Jens schreef: >> To get the discussion going, here's my suggestion for that API: >> PersistentSettings >> { >> property bool loadOnStartup: true >> property bool saveOnExit: true >> function load() >> function save() >> } > I would also consider an ev

Re: [Development] QAction-like API for QML

Op 11-12-2012 21:59, Alan Alpert schreef: > On Tue, Dec 11, 2012 at 10:49 AM, Shawn Rutledge > wrote: >> On Tue, Dec 11, 2012 at 09:48:22AM -0800, Alan Alpert wrote: >>> Why can't this be QML-only? For the set of controls exposed in >>> C++-only we have a C++-only Action API. When we add a set of

Re: [Development] [Qt-creator] gerrit-speak

Op 14-12-2012 9:30, Koehne Kai schreef: >> -Original Message- >> From: development-bounces+kai.koehne=digia@qt-project.org >> [mailto:development-bounces+kai.koehne=digia@qt-project.org] On >> Behalf Of Donald Carr >> Sent: Thursday, December 13, 2012 10:16 PM >> To: Jenssen Tim >>

Re: [Development] If you're waiting for reviews from me...

Op 19-12-2012 0:18, Marc Mutz schreef: > ... please cut me some slack while I handle the attached non-maskable > interrupt :) > Oh dear, you're in for a long-term project indeed! Congrats! André ___ Development mailing list Development@qt-project.org ht

Re: [Development] Integrating QAction and the upcoming QML Action (was QAction-like API for QML)

Op 18-12-2012 20:34, Shawn Rutledge schreef: > On 18 December 2012 20:05, Mark wrote: >> On Tue, Dec 18, 2012 at 6:46 PM, Alan Alpert <4163654...@gmail.com> wrote: >>> D) QCoreAction is added to Core or Gui and has even less >>> functionality, QQuickAction and QAction/QGuiAction build on top of >>

Re: [Development] Read binary file

Op 19-12-2012 8:54, Yuriy Rusinov schreef: > Dear colleagues ! > > I have to read binary file via Qt. In console application I make > > I think you'd be better of asking this in inter...@qt-project.org. This list is about the development *of* Qt itself, not the development *with* Qt. André _

Re: [Development] QAction-like API for QML

Op 14-12-2012 8:45, Bache-Wiig Jens schreef: > I have been lurking in the discussion a bit but I guess it is time for me to > pitch in. It is hard to keep up with 10 different threads at once. :) > > I find the idea of adding a new QCoreAction base class that is shared between > QML Action and QA

Re: [Development] QAction-like API for QML

Op 19-12-2012 11:52, Rutledge Shawn schreef: > On 19 Dec 2012, at 9:13 AM, André Somers wrote: > >> Op 14-12-2012 8:45, Bache-Wiig Jens schreef: >>> What I would propose is that we keep the QAction exactly as it is and make >>> it possible to use it from QML as we

Re: [Development] Integrating QAction and the upcoming QML Action (was QAction-like API for QML)

Op 19-12-2012 12:46, Stephen Kelly schreef: > On Wednesday, December 19, 2012 08:57:31 André Somers wrote: > >> My preference is D, obviously. I think it makes a lot of sense to be >> able to use actions in core, non-GUI layers of the application. > Qt is primarily for creati

Re: [Development] QAction-like API for QML

Op 20-12-2012 11:10, Bache-Wiig Jens schreef: >>> I find the idea of adding a new QCoreAction base class that is shared >>> between QML Action and QAction and only carries a small subset of >>> properties an unnecessary layer of abstraction. The idea of QAction is to >>> have the convenience of

Re: [Development] QAction-like API for QML

Op 20-12-2012 11:40, Shawn Rutledge schreef: > On 19 December 2012 09:13, André Somers wrote: >> Well, I disagree with that view of what an action represents. To me, the >> core of an action really is bundling a bit of state with a trigger for >> something to happen (I

Re: [Development] QAction-like API for QML

Op 20-12-2012 12:11, Shawn Rutledge schreef: > So ultimately at that company all the abstract actions you would have > wanted to create would still have to be converted into gui-oriented > actions anyway, right? How would you avoid writing code to bridge or > augment them into actions which can

Re: [Development] QtQuick1 (Qt4 and Qt5)

Op 26-12-2012 23:33, Alan Alpert schreef: > On Wed, Dec 26, 2012 at 11:58 AM, Thiago Macieira > wrote: >> On quarta-feira, 26 de dezembro de 2012 20.38.58, Alberto Mardegan wrote: >>> Hi all! >>> I've a few API additions to propose to the QML FolderListModel class, >>> which is present in thre

Re: [Development] Non-movable Qt build

Op 2-1-2013 13:42, Thiago Macieira schreef: > On quarta-feira, 2 de janeiro de 2013 10.53.03, Yves Bailly wrote: >> Does anyone knows where I could find the source code of the "official" >> installer, or at least some information about what it does? Because the >> installer does relocate the binari

Re: [Development] QML and QAbstractListModel

Op 10-1-2013 17:46, Alberto Mardegan schreef: > Hi all! > I'd like to make C++ models more usable from QML; in the net there > are several blog posts illustrating how to achieve that, but IMHO it > would be better if at least some of these handy features were in > QAbstractListModel itself: > >

Re: [Development] QML and QAbstractListModel

Op 14-1-2013 11:07, Alberto Mardegan schreef: > On 01/14/2013 09:29 AM, André Somers wrote: >> I am not fan of this change. I think the API of QAIM is already very >> complex. Adding more methods that basically only sort-of mirror existing >> methods but for a more confined

Re: [Development] Qt 5.1 feature set and freeze date

Op 13-2-2013 18:24, Jake Petroules schreef: QtWindowsExtras is something I plan to contribute to heavily. What things would folks like to see in there besides the image conversion functions? I suggested Windows 7 task bar features a little while back, and I believe that there is a Windows count

Re: [Development] Evolving Qt's multithreading API

Op 20-2-2013 15:45, Sze Howe Koh schreef: > Hi all, > > Some time ago there was some talk about improving Qt's multithreading > API. I'm summarizing them here to stop them from fading into > obscurity, and to see if there's any interest in following them up. There is also a proposal posted here: ht

Re: [Development] Evolving Qt's multithreading API

Op 22-2-2013 11:57, Sze Howe Koh schreef: > On Feb 22, 2013 12:33 AM, "Olivier Goffart" wrote: >> Some more common use case would be (pseudo-code) >> >> auto watcher = new QFutureWatcher; >> QObject::connect(watcher, SIGNAL(finished()), myObject, SLOT(doStuff())); >> watcher->setFuture(QThrerad::r

Re: [Development] Evolving Qt's multithreading API

Op 22-2-2013 14:31, Corentin Jabot schreef: >> On second thought, I'm not sure if this would be commonly needed. We >> can make it start immediately instead, BUT this requires a guarantee >> that the first thread can always connect the finished() signal, before >> the new thread runs and finishes.

Re: [Development] QtDriveInfo module in Playground

Op 1-3-2013 8:38, Иван Комиссаров schreef: > Hello, i would like to request a repository in a playground for my QDriveInfo > module. > > This class allows to retrieve information about a system volumes - like > available size, filesystem, filesystem flags and so on. > > Right now, repo is located

Re: [Development] QtDriveInfo module in Playground

Op 1-3-2013 10:22, ?? schreef: I don't think it's a good idea to try to fix QStorageInfo. The main argument is that QStorageInfo is a monitor+info provider, but monitor should depend on a DBus in Linux; however info provider doesn't require that. Also, monitor requires internal th

Re: [Development] QtDriveInfo module in Playground

Op 1-3-2013 11:52, Konstantin Ritt schreef: > 2013/3/1 André Somers : >> Op 1-3-2013 10:22, Иван Комиссаров schreef: >> >> I don't think it's a good idea to try to fix QStorageInfo. >> >> The main argument is that QStorageInfo is a monitor+info provider

Re: [Development] Evolving Qt's multithreading API

Op 4-3-2013 16:17, Sze Howe Koh schreef: > On 2 March 2013 18:17, Andre Somers wrote: >> Actually, how do you feel about adding an optional _then_ argument to >> the list of arguments of the functions in QtConcurrent and whatever is >> decided to replace the QtConcurrent::run feature? Such a _then

Re: [Development] Evolving Qt's multithreading API

Op 4-3-2013 23:56, Thiago Macieira schreef: > On segunda-feira, 4 de março de 2013 14.49.15, Thiago Macieira wrote: >>> I think the proposed API addition is actually quite natural. It is not >>> without precedent (QTimer::singleShot()), and would result in quite >>> simple, readable code. >> I disa

Re: [Development] Evolving Qt's multithreading API

Op 5-3-2013 8:41, Thiago Macieira schreef: > On terça-feira, 5 de março de 2013 08.38.17, André Somers wrote: >> I'd appreciate a reply on the point that when using a QFutureWatcher, >> you don't know if the future is already done or not at the moment you >&g

Re: [Development] [Qt-interest] QMultiHash

Op 7-3-2013 10:24, pengliang(??) schreef: Hi All QMultiHashhh; I need to find some key and change their values. I found If I use QmutableHashIteratorit , its bool *findNext *( const T &/value/) Its parameter is a value, not a key. So I need to : While(it.hasNext()) { It.next(

Re: [Development] Qt for iOS - iOSStyle

Op 13-3-2013 18:43, Bache-Wiig Jens schreef: Exactly. Being able to do pixel perfect layouts within the Qt Quick designer is one of the arguments against an IOS QStyle implementation. I would like to be able to see and run my apps _exactly_ as they would look on the device, without having to

Re: [Development] Making QScopedPointer scoped (again)

Op 3-9-2013 11:31, Oswald Buddenhagen schreef: > On Tue, Sep 03, 2013 at 10:02:52AM +0200, Stephen Kelly wrote: >> Again, this is what std::unique_ptr is for. We should not try to turn >> QScopedPointer into an attempt at a NIH std::unique_ptr. Where people have a >> need for a std::unique_ptr, the

Re: [Development] Making QScopedPointer scoped (again)

Op 5-9-2013 7:55, Olivier Goffart schreef: > On Wednesday 04 September 2013 18:45:45 Alexandr Akulich wrote: >> Hi all. >> >> Im totally agree with Stephen, because such change definitely complicate >> source reading. >> When one read "ScopedPointer", then one naturally expect that stored object >>

Re: [Development] A QtCore class for event-driven jobs

Op 11-9-2013 17:19, David Faure schreef: >> Couldn't such a class be part of the hopefully coming QtConcurrent >> replacement? > Can we forget about threads for a second? No, I'd rather not forget that huge pink elephant in the room... In this age of multi-core systems being the norm rather than e

Re: [Development] Heads up: QtAlgorithms to be deprecated in 5.2

Op 13-9-2013 22:16, Giuseppe D'Angelo schreef: > Hello, > > https://codereview.qt-project.org/#change,43441 (currently waiting for > a review) is going to mark most of the QtAlgorithms functions as > deprecated. > > The decision about this has already happened some time ago: > http://www.mail-arc

Re: [Development] [RFC] What to do about overloaded signals/slots?

> Op 5 okt. 2013 om 18:24 heeft Olivier Goffart het > volgende geschreven: > > I would also like to remind that adding overloads to functions is not source > compatible, as it may break a connection using the function poitner syntax. > Overloaded signals and slots should be avoided. > Well,

Re: [Development] [RFC] What to do about overloaded signals/slots?

Hi, > Op 5 okt. 2013 om 20:47 heeft Olivier Goffart het > volgende geschreven: > > > There is the same problem if one use pointer to member function in > QtConcurrent[1] or in other third party API (boost::bind) > Which means adding an overload can be a source incompatible change regardless

Re: [Development] QtTest for everybody

Op 7-10-2013 21:27, Thiago Macieira schreef: > On segunda-feira, 7 de outubro de 2013 22:50:49, Dmitry Ashkadov wrote: >> The topic about exceptions for slots and signals has inspirited me to >> pay your attention to QtTest. QtTest is a good unit-test framework, but >> it is focused to Qt. I think

Re: [Development] Disabling exception support in QtCore?

Op 10-10-2013 14:53, Olivier Goffart schreef: > On Thursday 03 October 2013 10:38:59 Thiago Macieira wrote: >> On quinta-feira, 3 de outubro de 2013 10:36:44, Olivier Goffart wrote: I dislike allowing this via the signal-slot mechanism because I see throwing from a slot as incompatible wi

Re: [Development] async operation error guidance

Frank Osterfeld schreef op 5-11-2013 17:41: > On Nov 5, 2013, at 5:12 PM, Tony Van Eerd wrote: > >> Most of BlackBerry's APIs are async. >> We are looking at moving some of these APIs into Qt. >> Just as one example, WiFi Direct. >> >> I have been attempting to come up with some solid guidelines o

Re: [Development] Weird offseting in QDataStream

Christian Ehrlicher schreef op 8-11-2013 10:29: Am 08.11.2013 10:15, schrieb Yves Bailly: Le 08/11/2013 10:05, Giuseppe D'Angelo a écrit : On 8 November 2013 10:01, Yves Bailly wrote: As a float is 4 bytes, I would expect the second f.pos() to display "4"... but it displays "8", as if QDataSt

Re: [Development] Weird offseting in QDataStream

Yves Bailly schreef op 8-11-2013 10:42: > Le 08/11/2013 10:29, Christian Ehrlicher a écrit : >> Am 08.11.2013 10:15, schrieb Yves Bailly: >>> Le 08/11/2013 10:05, Giuseppe D'Angelo a écrit : On 8 November 2013 10:01, Yves Bailly wrote: > As a float is 4 bytes, I would expect the second f.

Re: [Development] Weird offseting in QDataStream

Olivier Goffart schreef op 8-11-2013 10:57: > On Friday 08 November 2013 10:42:16 Yves Bailly wrote: > >> I can understand this for high-level Qt objects, but what about lower-level >> data? Does this mean I can't use QDataStream to read a file written by >> some other program, and/or can't use it

Re: [Development] Weird offseting in QDataStream

Eskil Abrahamsen Blomfeldt schreef op 8-11-2013 11:20: > > QDataStream supports reading and writing floats and doubles, but it > might use more bytes than necessary to represent them in the stream. > > The main use case of QDataStream is to serialize Qt data in a portable, > binary form with the co

Re: [Development] Weird offseting in QDataStream

Andreas Aardal Hanssen schreef op 8-11-2013 13:28: On 08 Nov 2013, at 12:41, Yves Bailly > wrote: ]I would recommend against using QDataStream for anything else than reading back what was written using QDataStream. This is what I called a step backward. It's jus

Re: [Development] Coding style proposal

Poenitz Andre schreef op 2-1-2014 23:49: > Jiergir Ogoerg wrote: >> Ironically, not even the IDE (QtCreator) sorts them out, in my example >> parse...() is the 1st in the list, and locale() is the last one (16th). > There's a "Sort alphabetically" check box in the context menu of > whatever-that-co

Re: [Development] Coding style proposal

Poenitz Andre schreef op 3-1-2014 12:33: > André Somers wrote: >> Poenitz Andre schreef op 2-1-2014 23:49: >>> Jiergir Ogoerg wrote: >>>> Ironically, not even the IDE (QtCreator) sorts them out, in my example >>>> parse...() is the 1st in the list, and lo

Re: [Development] QTCS2019 Notes from QtQml session

On 25-11-19 12:31, Ulf Hermann wrote: I think one of the biggest problems is that ID resolution crosses file boundaries. This essentially means that the ids chosen can very easily become part of the "API" of a component unless you are very vigilant to not allow that to happen. Well, yes, and th

Re: [Development] QTCS2019 Notes from QtQml session

On 25-11-19 15:53, Ulf Hermann wrote: Yeah, that's going to make using QML in actual applications a whole lot harder. For instance, sometimes access to some root node is needed even from deep leaf files. Removing that capability is quite a drastic measure. Yes, but the problems with this constr

Re: [Development] QTCS2019 Notes from QtQml session

On 26/11/2019 09:34, Chris Adams wrote: On Mon, Nov 25, 2019 at 9:34 PM Ulf Hermann wrote: I think one of the biggest problems is that ID resolution crosses file boundaries. This essentially means that the ids chosen can very easily become part of the "API" of a component unless you are very v

Re: [Development] QTCS2019 Notes from QtQml session

On 26/11/2019 08:56, Ulf Hermann wrote: We have some code that evaluates JS in custom QQmlContexts with certain "magic" context properties set (sort of like the "index" or "modelData" context properties in delegates like Repeater.delegate). Will something similar still be possible? You should r

Re: [Development] QtCS2019 Notes from "Fuzzing Qt" BoF session

On 22/11/2019 18:17, Giuseppe D'Angelo via Development wrote: Il 21/11/19 13:13, Robert Loehning ha scritto: ** [https://doc.qt.io/qt-5/qregularexpression.html QRegularExpression] This should mostly be fuzzing libpcre itself... Note that users should NEVER use / accept untrusted regular exp

Re: [Development] Qt 5.15 schedule proposal

On 27-11-19 07:03, Jani Heikkinen wrote: Hi! Qt 5.14.0 is in its final steps and it is time to start thinking Qt 5.15 release schedule. I don't see any reason/evidence how we could cut the time so my proposal is based on previous releases: Qt 5.15 initial schedule proposal: - All new modul

Re: [Development] Removing overloaded signals in Qt6

Hi, On 29-11-19 09:15, Ville Voutilainen wrote: On Wed, 27 Nov 2019 at 17:52, Sérgio Martins via Development wrote: Hi, The Qt5 PMF connect syntax is wonderful and very elegant compared to Qt 4. Unless, ofc, you have overloaded signals, which makes it painful to write and read. Not even qOve

Re: [Development] QHash for Qt 6

On 24-12-19 11:28, Martin Smith wrote: However, instead of adding template bool qIsEmpty(const T &t) { return t.empty(); } we keep discussing how ugly std is=) But that's kind of ugly too. I read it as qlsEmpty(), not qIsEmpty(). See what I mean? On of those is a lower case L. How about a new

Re: [Development] Changes to Qt offering

On 27/01/2020 22:07, Ville Voutilainen wrote: On Mon, 27 Jan 2020 at 21:56, Dmitriy Purgin wrote: By the way, gathering emails by requiring an account to download the software without any technical reason might be indeed an example of a GDPR violation. I am not a lawyer, but I am unaware of

[Development] Qt installer capabilities (was: Re: Changes to Qt offering)

Hi, On 28/01/2020 12:52, Tino Pyssysalo wrote: On 27.1.2020, 23.53, "Development on behalf of Thiago Macieira" wrote: > On segunda-feira, 27 de janeiro de 2020 10:39:44 PST Elvis Stansvik wrote: > > So? I have an account because I want to contribute. Does not mean I > > want

Re: [Development] Changes to Qt offering

On 28/01/2020 10:52, Christian Kandeler wrote: 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*. https://www.qt.io/blog/2015/05/06/

Re: [Development] Changes to Qt offering

Hi, On 29/01/2020 04:23, Thiago Macieira wrote: On Tuesday, 28 January 2020 10:01:43 PST Tim Murison wrote: 2. Don’t scare people off before they even start. Much lower initial pricing, no historical licensing, more distant ramps for price increases. Historical licensing cannot go away so long

  1   2   3   4   >