These pages are blank:
* https://contribute.qt-project.org/quips/
* https://contribute.qt-project.org/quips/0
In contrast, these pages show the (now-outdated) index:
* http://quips-qt-io.herokuapp.com/
* http://quips-qt-io.herokuapp.com/quip-.html
Regards,
Sze-Howe
--
Development mailing li
+1'ed
Regards,
Sze-Howe
On Mon, Jun 12, 2023, 06:48 Thiago Macieira
wrote:
> This change was last updated on May 12. It's a simple change to a unit
> test,
> but I haven't got a vote yet.
>
> Someone please give any thumbs up or now. I can't maintainer-approve
> without
> net positive votes a
This one has been stuck in "Integrating" state for over a year:
https://codereview.qt-project.org/c/qt/qt5/+/328630
Regards,
Sze-Howe
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
On Mon, 26 Sept 2022 at 15:13, Volker Hilsheimer
wrote:
>
> Hi,
>
>
> I would like to nominate Christian and Andy as co-maintainers for Qt SQL.
>
> Mark Brand, who is currently listed as the maintainer of Qt SQL, hasn’t
> responded to any of my emails, including one from two weeks ago where I
>
On Thu, 5 May 2022 at 16:41, Tor Arne Vestbø wrote:
>
> > On 5 May 2022, at 10:32, Alex Blasche wrote:
> >
> > > -Original Message-
> > > From: Development On Behalf Of Sze
> > > Howe Koh
> > > On Mon, 4 May 2020 at 15:19, Lars Knol
On Mon, 4 May 2020 at 15:19, Lars Knoll wrote:
>
> > On 4 May 2020, at 09:08, Albert Astals Cid via Development
> > wrote:
> >
> > P.S: Someone should really really remove John Layt as printinting mantainer
> > stuff, i don't think he's been around for years.
>
> Agreed. I’ll remove him.
>
> Che
A blog post [1] and the current doc snapshot [2] both say, "Clients that
still rely on missing functionality can include the private header
as a stopgap solution."
However, I just installed Qt 6.2.0 RC for Android and can't find
qtandroidextras_p.h anywhere. Are the blog and snapshot accurate?
On Tue, 31 Aug 2021 at 19:22, Eirik Aavitsland wrote:
>
> On 7/27/21 6:41 PM, Sze Howe Koh wrote:
> > Current Qt behaviours:
> >
> > A) If you create any QPixmap after creating QGuiApplication, the result
> > is probably the pixmap that you asked for. All is well.
&g
Current Qt behaviours:
A) If you create any QPixmap after creating QGuiApplication, the result is
probably the pixmap that you asked for. All is well.
B) If you create any QPixmap after creating QCoreApplication, the result is
a null QPixmap. No warnings are produced.
C) If you create any QPixmap
On Tue, 13 Jul 2021 at 21:38, Michal Klocek wrote:
>
> Hi
>
> Please note qtpdf repository was merged into qtwebengine, authors wanted to
> keep all the history so it was kept and git blame works nicely. However,
> qtwebengine git repo is anyway big in size so adding extra ~100 commits did
> no
== Issue ==
There is a rule that "QCoreApplication should be the first QObject
created and last destroyed" [1]. However, there exists a violation to
this rule in Qt's internals -- QPixmapCache uses an internal global
static QObject (a QPMCache, to be precise) [2].
If initialized, the QPMCache outl
On Thu, 20 May 2021 at 01:40, Kai Köhne wrote:
>
> > -Original Message-
> > From: Development On Behalf Of
Jason H
> > Sent: Wednesday, 19 May 2021 17:26
> > To: giuseppe.dang...@kdab.com
> > Cc: development@qt-project.org
> > Subject: Re: [Development] Changes to Freenode's IRC
> >
> > *
On Thu, 8 Apr 2021 at 04:43, Volker Hilsheimer wrote:
> without compile time warning those methods will still be in use, so we can’t
> remove them.
Is there a way to generate compile-time warnings for _enum values_?
Here are some existing flags that were missed during the Qt 6.0 cull:
* Code co
On Wed, 7 Apr 2021 at 22:14, Volker Hilsheimer wrote:
>
> > On 7 Apr 2021, at 15:55, Allan Sandfeld Jensen wrote:
> >
> > On Mittwoch, 7. April 2021 15:18:10 CEST Giuseppe D'Angelo via Development
> > wrote:
> >> Il 07/04/21 14:56, Sze Howe Koh ha scrit
Some parts of the Qt API have been documented as obsolete for a long
time, but were not removed before Qt 6.0.0 was released.
For example, the following 2 pages contain exactly the same list:
* https://doc.qt.io/qt-5/qmessagebox-obsolete.html
* https://doc.qt.io/qt-6/qmessagebox-obsolete.html
QL
On Fri, 19 Mar 2021 at 02:43, Cristián Maureira-Fredes
wrote:
>
> Dear community,
>
> The Qt Project is a huge effort from many people, and for the same
> reason, it's quite interesting to (1) Learn how to contribute and be
> part of it, and (2) Analyze the interactions of the many
> Qt modules.
>
Thank you, Tuukka and co!
Regards,
Sze-Howe
On Fri, 22 Jan 2021 at 22:33, Tuukka Turunen wrote:
>
> Hi,
>
>
>
> Servers have been restored and open-source downloads are working again.
>
>
>
> Archive of old and historic releases is missing, but will be made available
> next week.
>
>
>
> Blog
t;
>
> From: Development
> Date: Wednesday, 20. January 2021 at 8.06
> To: Sze Howe Koh
> Cc: development@qt-project.org ,
> releas...@qt-project.org , Interests Qt
>
> Subject: Re: [Development] [Releasing] [Interest] download.qt.io is down
>
> Hi,
>
&
On Wed, 20 Jan 2021 at 04:10, Tuukka Turunen wrote:
>
>
> Hi,
>
> There are multiple mirrors, try for example:
>
>
>
> https://qt-mirror.dannhauer.de/
>
> https://www.funet.fi/pub/mirrors/download.qt-project.org/
>
> https://ftp.fau.de/qtproject/
>
>
>
> ...or just use the online installer, which
On Sat, 18 Jul 2020 at 03:58, Ulf Hermann wrote:
>
> > I must be missing something. I tend to think of eventloops with notify
> > signals are an improvement over polling. You statement seems to say
> > that asking for a value is better, and notifications are to be avoided?
>
> I'm not saying tha
On Wed, 10 Jun 2020 at 15:26, Lorn Potter wrote:
>
> Hi *,
> On the road to Qt 6, we must remember our past:
> What better way than to have a short break to listen to this worldwide
> hit - The Qt 4 Dance!
>
> https://www.youtube.com/watch?v=NbTEVbQLC8s
>
> --
> Lorn Potter
> Freelance Qt Develope
On Mon, 9 Mar 2020 at 19:11, wrote:
> Hi,
>
> I provided a patch for CVE-2018-21035, present in Qt5 WebSocket Module.
> However apparently since the patch adds a new API it cannot go into Qt5.
>
> This vulnerability makes the Qt5 WebSocket module totally unusable for
> use in non-trusted environme
On Tue, 18 Feb 2020 at 20:57, Edward Welbourne wrote:
>
> 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/
>
> I note that the code quoted is usi
See
https://forum.qt.io/topic/111473/maintenance-tool-error-cannot-open-file-for-writing-no-error/
In summary, a bad BIOS prevents QTemporaryFile from generating
different filenames each run. The Qt Installer encounters name
conflicts and produces a cryptic error message:
Cannot open file ""
On Mon, 17 Feb 2020 at 14:18, Marc Mutz via Development
wrote:
>
> On 2020-02-16 19:32, Thiago Macieira wrote:
> > On Saturday, 15 February 2020 06:23:52 PST Marc Mutz via Development
> > wrote:
> >> C++20 will contain new classes with emit() member functions
> >> (wg21.link/P0053). While that wil
Another use case: Mass deployment to multiple PCs:
https://forum.qt.io/topic/111587/classroom-deployment-of-qt-for-multiple-pcs-and-for-all-users-windows
Regards,
Sze-Howe
On Sat, 15 Feb 2020 at 07:06, Sze Howe Koh wrote:
>
> On Sat, 15 Feb 2020 at 04:19, Thiago Macieira
> wrot
On Sat, 15 Feb 2020 at 04:19, Thiago Macieira wrote:
> On Tuesday, 28 January 2020 19:31:34 PST Thiago Macieira wrote:
> > On Tuesday, 28 January 2020 03:52:49 PST Tino Pyssysalo wrote:
> > > It is also possible to transfer the qtaccount.ini file to a CI machine,
> > > which removes the need for m
Currently,
* The qApp macro changes type depending on which headers are included,
and in what order. (If you #include but instantiate
a QCoreApplication, qApp returns a QGuiApplication pointer)
* The documentation says that the qApp macro is only valid if a
QApplication was instantiated. [1]
* Th
On Tue, 26 Nov 2019 at 17:07, Samuel Gaist wrote:
>
>
>
> > On 26 Nov 2019, at 09:36, Alex Blasche wrote:
> >
> > Hi,
> >
> > The QCanbus API is part of the QtSerialBus module. Since its first release
> > it has come a long way. In particular, André Hartmann & Denis Shienkov made
> > big contri
On Fri, 18 Oct 2019 at 08:43, Alexander Nassian
wrote:
>
> C++ hasn‘t even proper Unicode handling integrated. std::string is a mess in
> my opinion.
>
> Beste Grüße / Best regards,
> Alexander Nassian
>
> Am 18.10.2019 um 02:30 schrieb Henry Skoglund :
>
> > Hi, while writing lots of QString s
On Tue, 20 Aug 2019 at 22:29, Matthew Woehlke wrote:
>
> On 17/08/2019 00.13, Sze Howe Koh wrote:
> > QLabel returns some CoW types by-pointer as a legacy from Qt 1 times [1]:
> >
> > QPixmap *QLabel::pixmap() const;
> > QPixture *QLabel::pixmap() const;
>
On Tue, 27 Aug 2019 at 18:48, Nils Jeisecke via Development
wrote:
>
> Am 27.08.2019 um 08:34 hat Jani Heikkinen geschrieben:
> >This issue should be fixed now
> Now it says "Your edit was aborted by an ArticleSave hook".
The message could be clearer, but it actually means "Your edit is
pending m
On Sun, 18 Aug 2019 at 07:37, Mutz, Marc wrote:
>
> On 2019-08-17 07:13, Sze Howe Koh wrote:
> [...]
> > Which should we implement? I personally prefer (2) as it it can be
> > added to Qt 5.x and provides backward compatibility while keeping the
> > nice compact func
QLabel returns some CoW types by-pointer as a legacy from Qt 1 times [1]:
QPixmap *QLabel::pixmap() const;
QPixture *QLabel::pixmap() const;
If you know of any other such API, please point them out!
Anyway, a few different ways have been proposed to modernize this API
[2][3][4], summar
Thanks for the initiative, Tuuka and team. Much appreciated.
As part of the meeting, please review the points raised in previous
discussions [1][2]. Three major pain points were:
(A) Downloading metadata is very time-consuming.
(B) The automatic mirror selection algorithm doesn't always p
On Wed, 6 Feb 2019 at 12:43, Giuseppe D'Angelo via Development
wrote:
>
> Il 05/02/19 18:16, Dmitriy Purgin ha scritto:
> > I couldn't figure out the exact combination but as far as I remember, if
> > you have namespaced code, you have to always fully qualify the enum
> > class parameters in signa
On Tue, 15 Jan 2019 at 23:50, Thiago Macieira wrote:
>
> On Tuesday, 15 January 2019 00:21:54 PST Lars Knoll wrote:
> > * We regularly merge dev into it
> > * BC breakages are fine
> > * SC breakages require a maintainer approval and a Changelog entry marking
> > this as a source incompatible chan
On Fri, 11 Jan 2019 at 19:03, Fabrice Mousset | GEOCEPT GmbH
wrote:
>
> Hi Kai,
>
> I've used the development mailing list because I think this is a bug in the
> release.
> When I build my application with Qt 5.4.2, Qt 5.6.x or Qt 5.11.2 all works as
> expected.
> But with Qt 5.12.0, nothing wor
Significant chunks are missing from the Qt 5.12 documentation:
https://bugreports.qt.io/browse/QTBUG-72357
Could we please have a prominent notice on the website informing users of
this issue (and suggest viewing the Qt 5.11 version as a workaround) until
a fix lands?
Regards,
Sze-Howe
_
On Tue, 20 Nov 2018 at 16:40, Samuel Gaist wrote:
>
> Hi,
>
> > On 20 Nov 2018, at 09:38, Richard Gustavsen wrote:
> >
> > Hi,
> >
> > I'd like to nominate Christian Ehrlicher for approver rights.
> >
> > He has done a lot of work in Qt, especially Widgets and Item Views, with
> > more than 150
Hi all,
I can't find a final decision on this topic:
http://lists.qt-project.org/pipermail/development/2016-June/026058.html
The arguments from both sides were numerous (browse through
http://lists.qt-project.org/pipermail/development/2016-June/thread.html ).
I would like to avoid a re-hash of th
Hi Thiago,
On Sat, 18 Aug 2018 at 01:51, Thiago Macieira wrote:
>
> On Friday, 17 August 2018 08:13:21 PDT Tor Arne Vestbø wrote:
> > > Now, looking at the code, I don't think it does work. I thought that
> > > QCborValue::operator[] returned QCborValueRefs, but it doesn't. Adding a
> > > set of
New users cannot install at all and old users can't add new components
because a preview package depends on the not-yet-released Qt 5.11.2:
Cannot find missing dependency "qt.qt5.5112.win64_msvc2015_64" for
"preview.qt.tools.qt3dstudioruntime.win64_msvc2015_64"
Regards,
Sze-Howe
On Sat, 28 Jul 2018 at 16:57, André wrote:
>
> Hello all,
>
> I'd like to propose Samuel as approver. He has been active in the Qt project
> for ages.
>
> He not only provides code changes [0], he is also active reviewing others
> changes [1].
>
> But that's not all: Samuel is *extremly* active
2018 um 07:50 schrieb Alex Blasche:
> > Hi,
> >
> > There are no binaries for open source users. However open source users are
> > free to build their own binaries using GPLv3.
> >
> > --
> > Alex
> >
> > ____
> &
Hello,
According to http://doc.qt.io/QtForAutomation/qtautomation-install.html
Qt for Automation is available under GPLv3. However, the installation
instructions are not valid for open-source users. Furthermore, that
page also says that Qt for Automation is built on Qt for Device
Creation, which i
Thanks for chiming in, Henry. I've started filing bug reports, as
Giuseppe suggested.
On 3 April 2018 at 08:29, Henry Skoglund wrote:
>
> Hi, excellent initiative, a better MaintenanceTool UX would also improve the
> general opinion of Qt I think.
>
> Just one to add 2 things to Sze Howe's list:
On 3 April 2018 at 08:43, Jason H wrote:
> I'm not involved with the installer, but 2 points.
> 1. Number of gets doesn't really matter as long as it's HTTP 1.1. yeah it's
> not as optimal as a single compressed download, but it's not terrible. If
> it's only 1.0, then that's a problem. Or it co
3 broad issues impede new users who want to start using Qt and
frustrate old users who want to update Qt:
(A) Downloading metadata is very time-consuming.
(B) The automatic mirror selection algorithm doesn't always pick
the best mirror.
(C) (New users) It's not clear how to choose what
On 9 February 2018 at 15:54, Lars Knoll wrote:
>> On 9 Feb 2018, at 07:52, Kevin Kofler wrote:
>>
>> André Pönitz wrote:
>>> I think you need to start differentiating between Qt-without-Webengine
>>> and QtWebengine.
>>>
>>> And maybe "we" should do that, too.
>>
>> I would be entirely in favor o
On 7 January 2018 at 13:04, Igor Mironchik wrote:
> Hello,
>
> I see a button "Abandon Change" under the last patch set. Does this button
> abandon all changes set or only the last patch set?
>
> I want to abandon whole changes set.
>
> Thank you.
That button abandons all the patch sets with that
On 30 Dec. 2017 16:12, "Igor Mironchik" wrote:
Hello,
I want to contribute a little to Qt.
I cloned qtbase from git://code.qt.io/qt/qtbase.git
Created branch with
git branch test
git checkout test
made changes
git commit -a
Great but now I have a question: how should I correctly push my c
On 9 October 2017 at 13:53, Alex Blasche wrote:
>
>>We would like to have two new repositories created to share the code publicly.
>>Name of the project: Qt KNX
>>Name of the project: Qt MQTT
>
> +1. Please add the repos to https://wiki.qt.io/Maintainers.
I've added the repos to
https://wiki.qt.i
On 11 October 2017 at 03:49, Thiago Macieira wrote:
>
> On Tuesday, 10 October 2017 20:18:42 CEST Mat Sutcliffe wrote:
> > On 10 October 2017 at 15:28, Thiago Macieira
> >
> > wrote:
> > > On Tuesday, 10 October 2017 15:12:52 CEST Christian Gagneraud wrote:
> > > > (PS: I don't even know if qDebu
On 9 October 2017 at 21:02, Orgad Shaneh wrote:
> Hi,
>
> Recent changes in debian openssh packages cause errors when negotiating
> ciphers with qt-project gerrit.
>
> To enable connection, you need to add the following in ~/.ssh/config
>
> Host codereview.qt-project.org
>Ciphers +aes256-cbc
>
use the `extra` field in `Formatting` which
> you could optionally parse for custom formatting options. The parser
> would be a separate class inheriting `Formatting` and be specified in
> the Formatter using a typedef.
>
> E.g.
> `struct QStringFormatter::Formatter
> {
> typedef DateTimeInfo FormatType;
> QString operator()(const QDateTime &dateTime, const FormatType &format);
> }`
>
> `QStringFormatter` will then instantiate this struct when it receives
> a `QDateTime` object, and create a `FormatType` object to parse the
> data located in the `extra` field of formatting options. The
> `FormatType` object is then expected to store whatever info it needs
> and then the `Formatter` will use it later.
>
> Feedback on the approach, pitfalls etc. is much appreciated!
>
> Thanks,
>
>
> -- Mårten Nordheim
Regards,
Sze-Howe Koh
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On 6 July 2017 at 14:36, André Hartmann wrote:
>
> I'd like to propose the nomination of Denis Shienkov for Approver
> status.
>
> Denis has been the maintainer of QtSerialPort for a long time now.
> He also formed the architecture of QtSerialBus and provided several CAN
> plugins there. He furth
On 15 June 2017 at 01:29, Tuukka Turunen wrote:
> Hi,
>
> Yes, we would like to overall improve the examples. This is related to
having a new repo for examples, but not fully the same thing. Main goal in
example improvement being to make them more useful in what they are:
examples of how to use Qt
On 14 June 2017 at 19:18, Frederik Gladhorn wrote:
>
> Hi all,
>
> We recently had a discussion in the Qt Company about how we can improve the
> first use experience of Qt and one important aspect are the examples and
> demos.
+1
> We have a lot of examples that are limited by the Qt module th
A user from China has reported that the Chinese mirrors are no longer
visible to him [1]. I also don't see any when I visit
http://download.qt.io/online/qtsdkrepository/windows_x86/root/qt/Updates.xml.mirrorlist
(from Australia)
Now, from my experience (which is a few years old and possibly outdat
ry 2017 at 11:03, Ch'Gans wrote:
> > On 7 February 2017 at 23:18, Edward Welbourne
> > wrote:
> > [...]
> >>
> >> Sze Howe Koh (7 February 2017 04:35) replied:
> >>> See http://wiki.qt.io/Branch_Guidelines (Note: Qt module repositories
>
On 7 February 2017 at 08:39, Ch'Gans wrote:
>
> Hi there,
>
> It's been a while that I notice some typos here and there in Qt5
> documentation (mainly qtbase), and i decided that i would start
> correcting them in the source code.
> Most of them are really straight forward, eg. in QGraphicsView::s
On 30 Nov. 2016 04:04, "Thiago Macieira" wrote:
>
> On terça-feira, 29 de novembro de 2016 20:17:23 PST Sergio Ahumada wrote:
> > > Say what? Why not?
> >
> > I think he meant that you can't add new stuff .. say if you have a
> > iOS-only offline installer, then you can't use that maintenance tool
On 21 July 2016 at 19:04, Mitch Curtis wrote:
> Hello.
>
> Stack Overflow Documentation is now in Beta. You can read more about it here:
>
> http://stackoverflow.com/tour/documentation
>
> It is much more accessible than our contribution system, so I see a lot of
> documentation/example contribut
On 27 June 2016 at 17:28, Uwe Rathmann wrote:
>
> On Mon, 27 Jun 2016 08:39:42 +, Shawn Rutledge wrote:
>
> > We have mostly stopped working on QtQuick Controls 1, because the
> > implementation of Controls 2 is much more performant ...
>
> Controls 2 are for "embedded" - what at least means t
On 7 May 2016 at 12:20, Joseph Crowell wrote:
>
> On 4/05/2016 7:39 PM, Lars Knoll wrote:
>>
>> On 02/05/16 14:37, "Development on behalf of Sze Howe Koh"
>> > szehowe@gmail.com> wrote:
>>
>>
>>
>>> Hello,
>>>
>&
Hello,
One month ago, URLs that contain proper class names, e.g.
http://doc.qt.io/qt-5/QObject.html, worked as expected. However, they now
lead to Error 404. It looks like the server currently allows lowercase URLs
only, e.g. http://doc.qt.io/qt-5/qobject.html
This change might break bookmarks or
Hello,
The LICENSE.GPLvX and LICENSE.LGPLvX files from
http://code.qt.io/cgit/qt/qtbase.git/tree/ (and submodules) start with
"The Qt Toolkit is Copyright (C) 2015...", but then they go on to say
"You may use, distribute and copy the Qt GUI Toolkit under the terms
of..."
Is this correct? What abo
Hi all,
With the proliferation of supported platforms and add-on modules, we now
have a situation where some classes are only useable on particular
platforms. There've been cases where a developer sees a class in the Qt
docs and thinks "Ooh, this is just what I need!", only to find out (after
spen
On 9 January 2016 at 01:05, John Layt wrote:
>
> On 8 January 2016 at 07:18, Turunen Tuukka
> wrote:
>>
>>
>>
>> Hi John,
>>
>>
>>
>> This item was discussed at Qt Contributor’s Summit, please see session
>> notes: http://wiki.qt.io/QtCS2015_LTS
>>
>>
>>
>> For compilers this is also documented
On 10 October 2015 at 11:06, Sze Howe Koh wrote:
>
> On 16 September 2015 at 15:46, Jake Petroules
> wrote:
> > > On Sep 15, 2015, at 9:07 PM, Sze Howe Koh wrote:
> > >
> > > Hi all,
> > >
> > > There's a list of platfor
On 16 October 2015 at 05:50, Samuel Gaist wrote:
>
> On 15 oct. 2015, at 19:12, Giuseppe D'Angelo
> wrote:
>
>> Il 15/10/2015 19:06, Volny ha scritto:
>>> Same on Linux.
>>
>> It's https://bugreports.qt.io/browse/QTBUG-48781 , no idea about an ETA. You
>> could try redownloading until you get
On 16 September 2015 at 15:46, Jake Petroules
wrote:
> > On Sep 15, 2015, at 9:07 PM, Sze Howe Koh wrote:
> >
> > Hi all,
> >
> > There's a list of platform-specific functions from Qt 4:
> > http://doc.qt.io/qt-5/exportedfunctions.html
> >
> &g
Hi all,
There's a list of platform-specific functions from Qt 4:
http://doc.qt.io/qt-5/exportedfunctions.html
It looks like most of these functions are now gone. The non-existing
functions should be removed from the documentation, but 3 functions
remain in the code base:
* qt_mac_secure_keyboard
icular book very helpful in this
topic, I'd be happy to add it. Otherwise, I'll proceed as originally
planned. We have 3 votes for removal (including my own) and 2 votes
for replacement.
> Original Message
> From: Sze Howe Koh
> Sent: Sunday, August 30, 2015 09:49
> To: d
t; On Sun, Aug 30, 2015 at 10:48 AM, Sze Howe Koh
> wrote:
>>
>> Hi all,
>>
>> http://doc.qt.io/qt-5/threads.html#recommended-reading points readers
>> to some books about multithreading. These books were published between
>> 1995 and 1997, and have been well
Hi all,
http://doc.qt.io/qt-5/threads.html#recommended-reading points readers
to some books about multithreading. These books were published between
1995 and 1997, and have been well and truly superseded by newer ones.
Rather than update the list, I plan to remove it completely. I don't
think thi
Hi,
On 20 August 2015 at 15:31, Frederik Gladhorn
wrote:
>
> Hello all,
>
> To make dealing with Enginio a bit easier (I get asked for the right version
> number for each release and keep being confused myself since it doesn't see
> much activity), I will change the future branch names and versio
Hi,
In general, I think we should give higher priority to API simplicity
and flexibility, and lower priority to implementation simplicity.
Note that the QML Dialog is different from the C++ QDialog. QDialog
has no standard buttons of its own. Rather, it's up to the user to
manually add buttons, o
On 28 July 2015 at 15:28, Olivier Goffart wrote:
> On Monday 27. July 2015 10:03:25 Thiago Macieira wrote:
>> The whole thinking is that the use of operator<< for QString implies you're
>> trying to figure out why that string is the way it is, as opposed to trying
>> to convey a message.
>
> I thi
On 16 June 2015 at 19:28, Kurt Pattyn wrote:
> Well,
>
> you can also think of “on” + , like in: onWindowClosed,
> onMouseClicked, onBytesReceived, …
> In the same analogy, you could have onErrorOccurred.
>
> Seems very intuitive to me.
>
> It depends if you want to react to a state or to the eve
First, a big thanks to Stephen for bringing these issues to the ML's attention.
The topic of namespacing has been raised a few times before, but
discussions faded without us reaching any solid conclusions:
http://comments.gmane.org/gmane.comp.lib.qt.devel/13176
I think the disagreements we have o
On 11 June 2015 at 00:59, Alan Alpert <4163654...@gmail.com> wrote:
> On Wed, Jun 10, 2015 at 8:14 AM, 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:...
>
> I disagree that it lo
Hello,
This is the cleanest way I can currently think of to concatenate 2
QJsonArrays:
for (const auto& value : array2)
array1 << value;
Most of Qt's array-like containers (QVector, QList, QByteArray,
QString) have concatenation functions, but QJsonArray doesn't. So, I
propose adding
On 9 April 2015 at 17:08, Joerg Bornemann
wrote:
> On 08-Apr-15 17:45, Sze Howe Koh wrote:
>
>> May I suggest adding a bit of documentation on our side to help people
>> discover the features? Currently,
>> http://doc.qt.io/qt-5/qjsengine.html#script-exceptions only reco
On 9 April 2015 at 19:17, Simon Hausmann
wrote:
>
> On Thursday 9. April 2015 11.52.31 Simon Hausmann wrote:
> > On Wednesday 8. April 2015 23.45.29 Sze Howe Koh wrote:
> > [...]
> >
> > > Going off on a slight tangent:
> > > https://doc.qt.io/qt-5/qjsva
On 8 April 2015 at 22:10, Joerg Bornemann
wrote:
> On 08-Apr-15 16:06, Sze Howe Koh wrote:
>
>> I think we should document this somewhere, if it isn't already done (I
>> searched but couldn't find anything). I'm happy to volunteer if
>> necessary. Coul
On 7 April 2015 at 17:31, Joerg Bornemann
wrote:
>
> On 07-Apr-15 09:59, Dominique Fober wrote:
>
> > I'm using the new QJSEngine and I'm trying to get the error line number (in
> > case of error of course).
> > Currently I'm handling errors as documented:
> >
> > if (result.isError()) resu
On 27 February 2015 at 21:04, Kojo Tero wrote:
>> -Original Message-
>> From: Sze Howe Koh [mailto:szehowe@gmail.com]
>> Sent: 27. helmikuuta 2015 14:12
>> To: Kojo Tero
>> Cc: Qt Project; development@qt-project.org
>> Subject: Re: [Development] N
On 26 February 2015 at 23:05, Kojo Tero wrote:
> Hello,
>
>
>
> We just opened the new Qt Wiki at http://wiki.qt.io
>
>
>
> You can find the details in the blog post:
>
> http://blog.qt.io/blog/2015/02/26/new-qt-wiki-now-available/
>
>
>
> In short, it’s a mediawiki instance, you use Qt Account to
On 20 February 2015 at 16:28, Koehne Kai wrote:
>> -Original Message-
>> From: development-bounces+kai.koehne=theqtcompany.com@qt-
>> [...]
>> But this is an implementation convenience only. You can't convince me to
>> drop VS2010 to be able to use them internally inside Qt. Or 2008 for Wi
On 10 February 2015 at 00:55, Sean Harmer wrote:
>
> On Monday 09 Feb 2015 08:44:34 Thiago Macieira wrote:
> > On Monday 09 February 2015 16:15:42 Sean Harmer wrote:
> > > Trying to come up with a generic way to manage all this whilst making good
> > > use of n cores is a good fit for ThreadWeave
On 2 December 2014 at 07:37, Sze Howe Koh wrote:
>
> On 1 December 2014 at 16:00, Thiago Macieira
> wrote:
> > On Monday 01 December 2014 07:40:50 Knoll Lars wrote:
> >> Exactly that. It’s been like that since Qt 1 times, where QPixmap was a
> >> non shared cl
Hi all,
I'm trying to upgrade to Qt 5.4 and Qt Creator 3.3 using the online installer.
However, when I select "Update components" or "Package manager", the
installer gets stuck at "Preparing meta information download..."
Looking at
http://download.qt-project.org/online/qtsdkrepository/windows_x
On 1 December 2014 at 16:00, Thiago Macieira wrote:
> On Monday 01 December 2014 07:40:50 Knoll Lars wrote:
>> Exactly that. It’s been like that since Qt 1 times, where QPixmap was a
>> non shared class you had to instantiate on the heap. We never changed this
>> accessor for source compatibility
Hi all,
I'm curious about the rationale behind this API design. I can't think
of any other Qt function that returns an implicitly-shared object by
pointer, so this seems inconsistent. e.g. QWidget::font() returns a
QFont by const-ref.
Regards,
Sze-Howe
___
On 15 November 2014 03:58, André Pönitz wrote:
>
> On Fri, Nov 14, 2014 at 10:06:32AM +0100, Yann Levreau wrote:
> > Hi everybody!
> >
> > I am starting a new project and I am looking for some advice about what
> > kind of Qt/QML controls I should use. The purpose is to develop an rich
> > text e
On 5 October 2014 07:00, Aleix Pol wrote:
> On Fri, Oct 3, 2014 at 7:33 PM, Thiago Macieira
> wrote:
>>
>> On Friday 03 October 2014 18:11:22 Aleix Pol wrote:
>> > If I do "git submodule update" from a qt5 in 5.4 branch, the HEAD commit
>> > in
>> > qtsystems is 4a324f7. If I "git checkout origin
On 30 September 2014 20:56, Blasche Alexander
wrote:
>> -Original Message-
>> From: development-bounces+alexander.blasche=digia@qt-project.org
>> [mailto:development-bounces+alexander.blasche=digia@qt-project.org]
>> On Behalf Of Sze Howe Koh
>
>>
Hi all,
To bring the WebSocket QML import name in line with other modules
(e.g. "QtWebEngine 1.0", "QtQuick 2.x", "QtWebKit 3.x", "QtSensors
5.x"), I propose changing the import:
- From "import Qt.WebSockets 1.0"
- To "import QtWebSockets 1.1" (no dot between "Qt" and "WebSockets")
Ideally, the
1 - 100 of 226 matches
Mail list logo