Hi all,
some time ago I started using QScroller, and filed a couple of merge
requests, which so far haven't been looked at by the maintainer:
http://codereview.qt-project.org/11397
http://codereview.qt-project.org/11398
In addition to that, when I started adding support for the
QPinchGesture,
Hi all,
sorry for the intricated subject, I couldn't find a concise and
understandable way to express what I mean. :-)
Often it happens to me that I want to run some code when two or more
properties change on a QML object. A real life example is the contentX
and contentY properties from
On 04/01/2012 06:04 PM, joao.abeca...@nokia.com wrote:
The first one introduces a Q namespace, which replaces the Q prefix in
Qt5. The second patch drops the prefix in class names. This brings the
C++ API more in line with the QML/JavaScript one and will hopefully help
move all remaining C++
On 04/26/2012 01:19 PM, Thiago Macieira wrote:
However, unless I'm missing something, this only explains why we cannot
marshal for aggregate types (structures); we should still be able to
marshal array and dictionary types.
Not exactly... there are two reasons why this can't be done.
[...]
Hi all!
I really miss a QML version of QFileDialog. There currently isn't a Qt
Component for choosing a file or a directory from the filesystem, and I
think we should fill this gap ASAP. There's a bug I created to keep
track of this:
https://bugreports.qt-project.org/browse/QTCOMPONENTS-1242
Hi all,
I've got a question about the QML Desktop components at:
https://qt.gitorious.org/qtplayground/qtdesktopcomponents
Some components, such as TextField, are implemented as a derivative of
another (homonymous) component defined in the custom/ subdirectory.
Why is this separation needed?
Hi,
a small update. I started working on a FileDialog component for the
desktop, and it's seems that by using QFileDialog things are very easy. :-)
However, one question: should I map the x, y, width, height,
visible, etc. properties of the QDeclarativeItem to those of the QDialog?
This is what
Hi,
what is the license for Qt Desktop Components [0]?
The headers files don't seem to agree between each other: some are BSD,
some LGPL and carry this notice:
** No Commercial Usage
** This file contains pre-release code and may not be distributed.
** You may use this file in
On 05/22/2012 12:39 PM, Uwe Rathmann wrote:
While Qt4 widgets were a full replacement of Qt3 widgets it is not clear
when - or if ever - Qt components will be able to supersede widgets on
all platforms.
I'm probably being quite naïve here, but I don't think that it's
impossible to have a
Hi Rene,
I don't have real answers for your questions, but just a piece of
advice: KISS.
On 05/23/2012 01:25 PM, Rene Jensen wrote:
Question: How can we expose objects governed by QSharedPointer to QML
safely? I *can* guarantee the lifecycle beyond the life of my
QDeclarativeEngine.
As
On 05/23/2012 02:43 PM, Thiago Macieira wrote:
My original solution was to have a parent only deref its children's shared
pointer counter, deleting it only if it became zero. That means that if you
had a QSharedPointer to an object in the middle of the hierarchy, that object
would be
On 05/30/2012 09:28 PM, Quim Gil wrote:
Question: do you believe there is a value in promoting an effort to port
those components here and now?
Yes! While not perfect, these components are working generally well and
having them in Qt 5 would make it easier for Harmattan developers to
port
On 06/19/2012 11:58 AM, Thiago Macieira wrote:
On terça-feira, 19 de junho de 2012 09.54.15, Peter Kümmel wrote:
So even no Apache licensed code could be used within Qt?
Irrelevant. The CLA says that I can only submit code I authored myself. That
excludes everything that has a copyright,
On 06/29/2012 01:54 PM, Olivier Goffart wrote:
On Friday 29 June 2012 13:14:41 Alberto Mardegan wrote:
snip
So, it seems that q-geometryChanged() invokes just
QDeclarativeItem::geometryChanged(), ignoring the fact that it's a
virtual method. That is because the q_func() invoked with the Q_Q
On 06/29/2012 02:17 PM, Thiago Macieira wrote:
On sexta-feira, 29 de junho de 2012 13.14.41, Alberto Mardegan wrote:
Hi all,
I just run into an issue in Qt 4.8 QDeclarativeItem (but please read
on, the topic regards qt5 too): the geometryChanged() virtual method is
not invoked when
On 07/24/2012 09:01 PM, Rick Stockton wrote:
Hi. This is WRT fix
https://codereview.qt-project.org/#change,30222,patchset=2 for 4.8
declarative.
The changeset allows drag actions to occur with more 2D freedom, but it
steals the mouse (and prevents stealing by the parent flickable) in
On 08/02/2012 03:02 PM, lars.kn...@nokia.com wrote:
Talking for me, it's really sad to see this happen. There are a lot
of bright engineers working in that office and I have been working
with many of them for quite some time now. I really hope that
everybody will find a new job soon, and that
On 08/06/2012 12:52 PM, lars.kn...@nokia.com wrote:
We already have QT_BEGIN/END_NAMESPACE macros used throughout, as well as a
module specific qmoduleglobale.h. So I would think it should be possible to
do the change in a rather straightforward way.
I can't see how this could destabilise
On 09/13/2012 11:27 AM, marco.bu...@nokia.com wrote:
[...]
Q*F and Q*D like QRectF and QRectD? But the first step would be in my
opinion the removal of qreal. It should be really KISS!
OTOH, having a typedef which you can change to be either float or double
according to your precision needs
On 09/13/2012 01:27 PM, Denis Shienkov wrote:
For a start here can add only the basic types of devices (already
implemented),
and then on future can add new supported device types (step-by-step).
This is just pseudocode, I know that it contains errors. I just proposed the
idea,
so
On 09/28/2012 07:37 AM, Loaden wrote:
I prefer:
dev - next
stable - master
release - release
+1
Ciao,
Alberto
--
http://blog.mardy.it - geek in un lingua international!
___
Development mailing list
Development@qt-project.org
On 10/20/2012 02:16 AM, Thiago Macieira wrote:
[...]
3) In addition, we'll create a *new* tool also called qmake that will be
installed to $bindir. This tool shall have the following behaviours:
a) under most circumstances, it will simply find another qmake and pass
through all arguments.
On 10/20/2012 11:28 AM, Stephen Kelly wrote:
And from that time on one doesn't need to remember what qt version or
toolchain one has to use for a project, and just always type qmake
from the project base directory.
This is the right goal imo, but the wrong implementation.
I'm not sure that
On 10/31/2012 01:06 AM, Thiago Macieira wrote:
In any case, what's the problem with making a subjective decision? Clearly the
applications need to be split in two groups, so why shouldn't the Qt Project
make its recommendation to the downstreams?
I would like that all binaries are installed in
Hi all!
At some point I might need to use XEmbed, so I'm interested in helping
out the implementation of QX11EmbedWidget in Qt5, as time permits.
Now I'm just studying the code to evaluate how much of an effort it
would be.
I've seen the merge request about QX11Info, which is somehow related:
On 11/08/2012 11:58 AM, Samuel Rødal wrote:
It needs to be part of a separate library, as we don't want libQtGui or
libQtWidgets to link to X11-specific libraries (the choice between the
wayland, xcb, directfb, kms, etc platform plugins is made at run-time).
Sure, but it could still be
On 12/11/2012 12:47 PM, Sorvig Morten wrote:
I've been planning this a bit from he perspective if the Cocoa port, here's
what I think I need:
- A Qt::WindowFlags flag (Qt::NativeWindow)
OK. Though I'd prefer to call it Qt::ForeignWindow, to make it obvious
that it's not owned by this
On 12/12/2012 01:16 AM, Thiago Macieira wrote:
On terça-feira, 11 de dezembro de 2012 15.55.52, Alan Alpert wrote:
Would you care to sketch out what your PersistentSettings element
would look like in practice?
In a non QML approximant syntax:
Rectangle {
PersistentSettings {
I got a WIP branch up for preliminary review:
https://codereview.qt-project.org/#change,42633
Any hints (especially on how to write automated tests for the feature)
are very welcome :-)
I tested it with a simple client and a Gtk socket, and it mostly works
(still some focusing issues...).
On 12/12/2012 05:30 PM, Thiago Macieira wrote:
But that change should have targeted the dev branch. It's new API and a new
feature.
Indeed! Though I was just interested in sharing the code with people for
early feedback, so I didn't pay much care to the target branch.
I'll move the next
On 12/12/2012 05:24 PM, Alberto Mardegan wrote:
I got a WIP branch up for preliminary review:
https://codereview.qt-project.org/#change,42633
Any hints (especially on how to write automated tests for the feature)
are very welcome :-)
I tested it with a simple client and a Gtk socket
On 12/18/2012 06:46 PM, Alan Alpert wrote:
[...]
C) QGuiAction is added to Gui and is used to create the QML API and
the bridge with QActions.
[...]
My favorite of those is C), but there is the unresolved question of
how to make an effective bridge given that we can no longer make
QAction
Hi all!
I've a few API additions to propose to the QML FolderListModel class,
which is present in three modules:
- Qt4/QtDeclarative
- Qt5/QtDeclarative
- Qt5/QtQuick1
Of course, all changes should go to Qt5/QtDeclarative; but what about
the others? Is there going to be one more release of
On 01/08/2013 02:03 AM, Alan Alpert wrote:
Feedback?
It's really Qt that's cross-platform focused now, not me. I just want
this so that SameGame runs beautifully on BB10 :) . So while I'd
welcome feedback from any source, I *need* to hear it from people
interested in other platforms (or even
On 01/08/2013 06:54 PM, Alan Alpert wrote:
Do you have an example of how this could be done? Specifically,
something that could select a different settings.js file for SameGame
without having to go through the C++ executable?
If by without having to go through the C++ executable you mean that
On 01/09/2013 09:12 PM, Laszlo Papp wrote:
To be honest I am reluctant to this mentality of not caring about others
like me who do not wish to subscribe to many mailing lists.
I don't see any big issues: if you don't want to see the posts
separately, just make a filter so that they appear in
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:
- count property
- get(index) invocable method,
On 01/11/2013 04:47 PM, Simon Hausmann wrote:
So I got in touch with them and they're willing to contribute the code to the
Qt
project. I'm therefore seeking approval from the Qt project to importing
Snowshoe
into Gerrit, with
[...]
I like the idea, but I'm a bit concerned about the future
On 01/10/2013 05:46 PM, Alberto Mardegan wrote:
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:
- count
On 01/12/2013 11:59 PM, Nils Jeisecke wrote:
Hi,
what about adding a new Quick item for enhanced QAbstractItemModel access.
ListModelAdapter {
id: myModelAdapter
sourceModel: myModel
}
ListView {
model: myModelAdapter.sourceModel
delegate: Text {
MouseArea {
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 use-cases only makes that situation
worse. For instance, you now get a
On 01/14/2013 11:37 AM, André Somers wrote:
[...]
top of them. Note that you can also use a proxy to map a table model to
a list by mapping the data in columns to different roles. The base class
would not be a QListModel, but the data would be available from the
first column anyway. When using
On 02/03/2013 04:45 AM, Martin Jones wrote:
Alan is for all intents and purposes acting as maintainer now, so I think
we should make it official.
+1!
Ciao,
Alberto
___
Development mailing list
Development@qt-project.org
On 02/13/2013 12:49 PM, Knoll Lars wrote:
* Friday 22. February: If you have a larger feature/feature branch (not
yet merged) that you want to have in the release you must have told the
release team (by mail to releases@) by then.
I'd like to have the X11 Embedding in 5.1:
Hi all!
The CI bot reported a failure in tst_qwidget when merging
https://codereview.qt-project.org/#change,42990,patchset=8
(see the last comment from Qt Continuous Integration System).
I can reproduce the same failure under ubuntu 13.04 running XFCE.
Then I removed my patch (by checking out
On 03/02/2013 01:06 PM, Olivier Goffart wrote:
If i understand the test properly, it waits two seconds for a window to
receive some events. But it may very well happen that the seconds are not
enough, because the tests are run on some busy virtual machine or because the
window manager is
On 03/15/2013 02:51 PM, Oswald Buddenhagen wrote:
On Fri, Mar 15, 2013 at 12:49:55PM +0100, Axel Waggershauser wrote:
On Fri, Mar 15, 2013 at 8:11 AM, Thiago Macieira thiago.macie...@intel.com
wrote:
4) What about consistent placement of the ',' in class member
initialization lists? I've
Hi all!
One of the issues that has most bothered me when developing in QML is
dealing with the same variable name in item properties and context
properties. For example:
// model is a context property
Loader {
property variant model: model
sourceComponent: someComponent
}
The code
On 12/09/2013 12:54 AM, Alan Alpert wrote:
On Sun, Dec 8, 2013 at 5:38 AM, Alberto Mardegan
ma...@users.sourceforge.net wrote:
[...]
What do you mean current context? The problem you seem to be hitting
is that there is another symbol in the current context that you want
to avoid, so
On 12/09/2013 10:00 AM, Alan Alpert wrote:
Question does seem a bit clearer. But I think the answer is the same -
ListView shouldn't be using context properties anymore. Well, it's
worthwhile for the convenience here but maybe add an attached property
reference as well for those cases needing
Hi all!
For one of my projects, I found the need to merge several models into
a single model. I wrote a class for it, and I think it's generic enough
to be useful for other people, and I wonder if it could be put into Qt
itself:
On 01/15/2014 10:48 PM, Alan Alpert wrote:
This approach could also apply to the original suggestion by Alberto,
in the absence of a separate add on module (which Sean couldn't use
because of the QtQuick.Controls dependency). Just requires a higher
bar for code review/quality, but I'm
On 03/30/2014 03:56 PM, Gladhorn Frederik wrote:
A fix for this would certainly be appreciated.
http://qt-project.org/wiki/Gerrit-Introduction
On Saturday 29. March 2014 14.56.16 Rex Dieter wrote:
Ruslan Nigmatullin wrote:
If the changes will be done and accepted is there any hope to have
On 04/24/2014 03:11 PM, Joshua Kolden wrote:
[...]
We have a solution that works very well for us using QVariantMaps and an
MVC pattern / strong separation between data objects and view. It
appears to me that most people are having this issue because it’s not
common to use MVC with QtWidgets.
Hi Frederik,
On 04/09/2015 04:04 PM, Frederik Gladhorn wrote:
We want to give you the code, here it is :)
https://codereview.qt-project.org/#/admin/projects/qt-labs/qtquickcontrols2
[...]
Feedback welcome!
If I understand correctly, these controls are intended to be a
cross-platform set of
On 04/17/2015 11:48 AM, Allan Sandfeld Jensen wrote:
If we go with the QImageReader level, it could be an QImageIOHandler::Option,
and possibly be set different between JPEG and TIFF by default. The real
problem is what we decide the default for JPEG should be now.
IMHO, QImageReader default
On 04/22/2015 09:54 PM, André Pönitz wrote:
However, we do have context here, namely existing behaviour in Qt 5.x,
as well as certain general promises given for changes between Qt 5.x and
Qt 5.(x+1).
I see it as a long standing bug which finally got fixed.
But the problem is that the
On 04/23/2015 04:53 AM, Konstantin Ritt wrote:
We already have a complete solution -
https://codereview.qt-project.org/110685
That looks good.
All we need now is to fix the behavioral regression introduced in 5.4.
But if I understand the code correctly, the fix above gives developers
an
On 04/23/2015 01:36 PM, Gunnar Sletta wrote:
I think we should strive to not introduce regressions on purpose. Hence:
- Revert the behavioral change in 5.4 which adds rotation to JPEGs
- Have opt-in rotation in QImageReader.
- Keep TIFF rotation as it is (and change it to the Qt-wide
On 04/23/2015 02:34 PM, André Somers wrote:
What is the problem with using
Image {
source: someImage.jpg
autorotate: true
}
Again: note that QImage != QML Image
I don't like globals if they can be avoided. In this case, I think they can.
I could certainly live with that, but
On 04/22/2015 09:39 AM, André Somers wrote:
I'm with Konstatin on this one: it seems like a regression to me. It
would be a useful feature to add, but then add it in such a way that it
is actually clear what it does, the user can control it, and it does not
break applications. I think it _is_
Hi Massimo,
On 04/28/2015 07:46 AM, Massimo Callegari wrote:
I just wanted to share my specific(?) case so if someone stumbles on it, they
can find the solution out of the box :)
I also stumbled on this problem once. Luckily, the documentation is
quite clear on this -- the problem is that
On 18.06.2015 15:59, Smith Martin wrote:
Why not leave current Qt modules as they are, without namespaces and with the
Q prefix on classes, and just introduce the option of adding a new module to
Qt by putting it in a namespace named QtFoo without the Q prefix on class
names, or adding it
On 01/06/2016 18:12, Mathias Hasselmann wrote:
> Yes, when it comes to initializer lists the trailing comma looks ugly to
> me. Because of the inconsistent two-space indent for the first
> initializer. Because line starts of are not aligned.
In my projects I use this style:
MyObject::MyObject():
On 23/02/2016 01:31, deDietrich Gabriel wrote:
> The story behind having QModelIndex and QItemSelectionModel exposed
> to the QML engine was to solve the selection problem in the Qt Quick
> Controls 1 TreeView. TableView could use a simple selection model
> because of the trivial mapping between
On 25/02/2016 13:20, Welbourne Edward wrote:
> André Somers used m* for minutes and metres, footnoting:
>> )* Note the first clash already...
>
> I think it is fairly sane to just insist that SI units take precedence,
> especially given that we support multi-letter unit names (e.g. pt, px,
> mm,
Hi all!
Since Qt 5.5, the QItemSelectionModel class is exposed to QML as
ItemSelectionModel (in the QtQml.Models module):
http://doc.qt.io/qt-5/qml-qtqml-models-itemselectionmodel.html
Apart from having almost no documentation, this component seems to be
rather hard to use in QML: its methods
Hi all!
I wanted to try fixing this bug:
https://bugreports.qt.io/browse/QTBUG-49876
(in QML, the dragged item disappears during the drag and drop operation,
if the dragType is Drag.Automatic -- external drag)
First of all, after some investigation I wonder whether this is actually
a bug, or
On 07/26/2016 05:12 PM, Andrea Bernabei wrote:
> I'd like to propose changing the default value of QML Flickable's
> flickableDirection in Qt 5.8.
I vote against it :-)
While I agree that your proposal makes sense, I would advise against
implementing it before Qt 6. There are lots of programs
Hi there!
I'm working on a project of a desktop application using the
QtQuickControls module. I occasionally run into small issue, but I'm
generally satisfied with the state of the controls (I'm working on
Linux, I hope that other platforms are working equally well).
What makes me worry a bit
On 10/11/2016 11:55, Frederik Gladhorn wrote:
> The last gap are Linux styles. The situation with KDE is actually quite
> interesting, since the platform is QStyle based. We do not believe in QStyle
> based styles for QQC2 as it stands. They will never have the same performance
> level of the
On 11/25/2016 03:40 PM, Oswald Buddenhagen wrote:
i'm expecting a flurry of retargeting requests of changes from 5.6 and
5.7 to 5.8 now.
I have a few changes targeting 5.6 which are waiting for review:
On 16/04/2017 21:13, Olivier Goffart wrote:
>
> Q_GADGET's overhead is basically the cost of the QMetaObject. So it's there,
> but it's quite small.
> If there is an use for a class to be a Q_GADGET, I think it should be added.
For the record:
https://codereview.qt-project.org/#/c/191777/
Hi all,
I'm about to use QMimeType in my application, and I'd found it useful
if it were a Q_GADGET. Can I just go on and submit a patch to add that,
or are there some cons (a small increase on the library size, I assume)?
In general: is it a good idea to add Q_GADGET to non QObject classes
Hi all,
in addition to making QMimeType usable from QML [1], jpnurmi also
suggested of exposing QMimeDatabase as a singleton.
The open question is where this element should be added: I suggested
QtQtml.Models, given that it's a database, but maybe creating a separate
module QtQml.Utils might be
On 25/04/2017 09:29, Martin Smith wrote:
>> What would be incorrect as those APIs are only internal for C++, but
>> public for QML or v.v.
>
> Then we need \cpponly and \qmlonly, or something like that.
This is calling for future headaches, when you start adding python or
other languages.
It's
Hi all,
my understanding looking at the implementation of the
XMLHttpRequest.send() method in QtDeclarative [1] is that the
said method only accepts UTF-8 data as parameter.
Now, I would like to be able to send arbitrary data (in order to, for
example, upload a JPEG image to flickr) and I
On 06/23/2017 10:08 AM, Simon Hausmann wrote:
I think send() should be fixed to support more than just strings as
parameters. For example in browsers
you can use send() with array buffers and blob objects. We don't support
the latter, but the former we do
and they are also our mapping for
On 29/10/2017 22:45, Thiago Macieira wrote:
> I wish I could help in the reviews, but those are not things I understand at
> all. But I can give this advice: the three changes targetting pre-5.9 need to
> be updated. All three should be retargetted at 5.9.
Good to know! I'll resubmit them,
Hi there!
I've got a few merge proposals which were recently closed by the Qt
cleanup bot due to lack of activity; I've reopened them and ping a few
people, but to no avail.
All but one are tiny, and I would appreciate if someone could spend a
couple of minutes to give the final +2 or to advise
Hi all!
I've developed a desktop application which uses the WebView QML
module, with the hope of publishing it in the Apple store. However,
unless I am seriously mistaken, this is just not possible (or maybe the
documentation needs some serious love).
No matter what I try, it seems that
On 22/01/2018 18:49, Konstantin Tokarev wrote:
> From [1] it seems like QT_MAC_USE_NATIVE_WEBVIEW environment variable
> is required to use native backend.
>
> [1] https://codereview.qt-project.org/#/c/162337/
Yes, but still QtWebEngine is required, as QtWebView is linking to it.
I've now
Hi all!
Speaking of coding style again, I haven't found any indication in the
coding guidelines about brace vs parentheses in initializations.
There are a few cases where they can be used (and I might even be
forgetting some):
1) Constructors:
MyClass(): var(0) {}
vs
On 25/02/19 15:57, Mitch Curtis wrote:
> My only issue with it is that I don't know if it will see much use
> outside of your use case. Usually if all items in a layout have the
> same margins, you would just apply those margins to the layout
> managing them instead. While I appreciate that that
Hi there!
I'm working on a desktop style for QtQuick.Controls 2 [1], and I'm
currently investigating the issue of layouts. My current approach is to
define my own ColumnLayout element like this:
==
import QtQuick.Layouts 1.2
import it.mardy.Desktop.private 1.0
ColumnLayout {
On 25/02/19 11:23, Mitch Curtis wrote:
> So would it look something like this?
>
> // implicit size is 118 x 64
> ColumnLayout {
> defaultLeftMargin: 12
> defaultRightMargin: 12
> defaultBottomMargin: 12
> defaultTopMargin: 12
>
> // implicit size
Hi there!
When developing a QML module for the greater public one wants to
provide a source package that can be built on multiple Qt versions.
However, QML's lack of a preprocessor makes this rather cumbersome.
Suppose that my module needs to provide an element like this:
import QtQuick
On 18/03/19 12:11, Pierre-Yves Siret wrote:
> This can be done with QQmlFileSelector :
>
> QQmlApplicationEngine engine;
> QQmlFileSelector* qmlFileSelector = QQmlFileSelector::get();
>
> #if QT_VERSION >= QT_VERSION_CHECK(5, 12, 0)
> qmlFileSelector->setExtraSelectors({"5.12"});
>
On 30/05/19 18:34, Giuseppe D'Angelo via Development wrote:
> Hi,
>
> On 30/05/2019 10:23, Alberto Mardegan wrote:
>> I bet it's unused because everyone is using QList. But once we deprecate
>> QList, people will start asking for a CoW version of std::list.
>
> QList
On 29/05/19 13:53, Mutz, Marc via Development wrote:
> == QSharedDataPointer / QExplicitlySharedDataPointer ==
>
> These are basically Qt-internals, and should never have been public in
> the first place. It's _because_ they are public that we have two of
> them, and soon a third one (properly
On 30/05/19 11:40, Mutz, Marc wrote:
> On 2019-05-30 10:23, Alberto Mardegan wrote:
>> It's not clear to me why splice() cannot be implemented: it would just
>> mean that the list data would detach as in all other non-const methods.
>> Or am I missing something?
>
> Y
On 5/31/19 4:24 PM, Volker Hilsheimer wrote:
> Nobody is forced to move to Qt 6 right away; Qt 5.15 is an LTS with
> three years maintenance. We are not expecting lots of people to jump
> on Qt 6.0 anyway (because .0, and not an LTS release anyway), so when
> an API was marked as deprecated makes
On 18/06/19 10:43, Mutz, Marc via Development wrote:
> On 2019-06-18 08:18, Alberto Mardegan wrote:
>>
>> Adding a const bool operator to QSharedDataPointer would solve the
>> problem, wouldn't it?
>
> And (silently) break code that relies on the current behavio
On 05/06/19 01:39, Kevin Kofler wrote:
> Mutz, Marc via Development wrote:
>
>> and produces surprises such as
>> https://codereview.qt-project.org/gitweb?p=qt%2Fqtbase.git;a=commit;h=96dc9a19ae11ca140d681f0e2605b5f4b953e581
>
> My existing QSharedDataPointer code always checks truth with
> if
On 27/06/19 14:14, Bastiaan Veelo wrote:
>
> However, it seems that most web browsers that implemented their own
> browser tech have ditched those in favour of a third party framework
> (see Opera, Edge, e.g.) -- how much of the reason for that is due to
> rendering or networking I don't know.
I
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 have 16 GB of RAM, and sometimes I have to close
Chromium away (yes, I know,
On 12/02/20 15:20, Vitaly Fanaskov wrote:
>> AFAIK, we don't have a procedure to make project-level decisions by majority
>> vote.
> True. We're discussing now. The goal here is to take people opinions and
> arguments into account before making a decision.
The problem I see, is that in your
On 29/01/20 13:02, Edward Welbourne wrote:
> Clarification: we'll be moving to "all commits land first on dev and are
> cherry-picked out to other branches that need them" in place of our
> present merge-based module. Where Cristián says "all those patches will
> be on Gerrit", they'll be on dev
On 29/01/20 19:02, Volker Hilsheimer wrote:
> You obviously don’t trust that TQtC will treat the data the online-installer
> either demands or requires with the appropriate confidence. So, shouldn't you
> build Qt from sources? Your IP address is PII, after all. Why did you trust
> that The Qt
On 04/02/20 16:55, Vitaly Fanaskov wrote:
> But if you see API like this:
>
> std::unique_ptr someAPI();
>
> You have much more information about managed object just by reading the
> code. This is also much easier to understand what can or cannot be done
> with the returned value in the
1 - 100 of 136 matches
Mail list logo
