On mandag 11. juli 2016 12.54.58 CEST Simon Hausmann wrote:
> Instead of using copy(), why not call the non-const bits() function (and
> don't use the returned value). That will detach [...]
Instead of using bits(), why not call detach() directly? ;)
- Paul
__
On fredag 13. mai 2016 05.24.03 CEST Shawn Rutledge wrote:
> > On 12 May 2016, at 17:05, Jake Petroules wrote:
> >
> > +1. I touch Windows as little as possible, yet I'm still aware of
> > Maurice's prominence in the WinRT space. :)
> +1 likewise.
+1 from me too :)
- Paul
__
On Friday, November 27, 2015 02:23:01 PM Eskil A. Blomfeldt wrote:
> I think a batched change for all open reports with a "Fix version" !=
> "Some future release" would have to be part of this. A quick check
> reveals that we (for instance) currently have 27 unresolved bugs with
> fix version se
On Friday 6. November 2015 10.10.52 Thiago Macieira wrote:
> But before I go and modify QFactoryLoader... what is that class for? Can
> anyone find out from the old history? It traces its existence back to "Long
> live Qt 4.5".
Added by Matthias in commit 89df363e4a795d67342d04e478af592618e16363 a
On Tuesday 20. October 2015 23.37.27 Thiago Macieira wrote:
> Em qua 21 out 2015, às 06:29:30, Knoll Lars escreveu:
> > As I remember it, the change from QSubString to QStringRef was a simple
> > API
> > naming decision, i.e. independent of the implementation details.
>
> Then it must be a coinci
On Wednesday 9. September 2015 18.13.55 Thomas Senyk wrote:
> How stable/done is this? Is it worth while trying to port an existing
> compositor to the new API?
It's in active API review, and we're still tearing down some of the classes.
Right now, we are removing absolute positions from the API,
On Sunday 23. August 2015 19.53.51 Knoll Lars wrote:
> The changes made it into 5.6. I'm pretty sure documentation will be in place
> for the release :)
http://doc-snapshots.qt.io/qt5-5.6/highdpi.html#qt-support
- Paul
___
Development mailing list
Devel
On Monday 10. August 2015 16.34.49 Oswald Buddenhagen wrote:
> would the repository be imported as-is (git fast-import from bzr),
> filter-branched, or re-created?
I think fast-import is the simplest. There are probably some packaging related
configuration files that are not relevant in the Qt re
On Monday 10. August 2015 16.34.49 Oswald Buddenhagen wrote:
> On Mon, Aug 10, 2015 at 02:36:34PM +0200, Paul Olav Tvete wrote:
> > So what we are talking about here is the platform plugin for Mir servers,
> > together with a Qt Quick plugin for writing a Mir compositor.
&g
On Monday 10. August 2015 14.01.41 Oswald Buddenhagen wrote:
> the description on launchpad:
> > This projects contains code to integrate Qt with the Mir display
> > server as follows:
> > - a QPA plugin to enable Qt applications as Mir clients
> > - a QPA plugin and support module to enable Qt/QML
On Monday 10. August 2015 10.59.17 Richard Moore wrote:
> On 10 August 2015 at 10:01, Paul Olav Tvete
>
> wrote:
> > I would like to propose a new playground repository for upstreaming the
> > QtMir
>
> > project from Canonical:
> Will the canonical devel
Hi,
I would like to propose a new playground repository for upstreaming the QtMir
project from Canonical:
https://code.launchpad.net/~mir-team/qtmir/trunk
I propose the name "qtmirserver", since it is more descriptive than "qtmir".
The name "qtmirextras" should be reserved for platform specifi
On Sunday 14. June 2015 23.18.18 Thiago Macieira wrote:
> The file qtbase-opensource-src-5.4.2/lib/fonts/README
> states:
> 'Copyright statements and the source of the qpf fonts are located in
> ../../src/3rdparty/fonts'
>
> The directory src/3rdparty/fonts does not exist in qtbase-opensource-
> s
On Tuesday 14. April 2015 08.33.06 Mathias Hasselmann wrote:
> So we finally have reached the turning point at which we have no chance
> but to make C++11 mandatory for public Qt headers:
You might think you're trolling, but I think requiring C++11 would be an
excellent goal for Qt 6.
- Paul
___
On Wednesday 1. April 2015 13.28.50 Christian Gagneraud wrote:
> So, my question is: Do you guys plan to remove this feature, and if yes
> (which seems likely to me), how could I then control colors, opacity and
> drawing order on a per view basis?
There is very little new development for graphi
On Thursday 22. January 2015 06.52.56 Blasche Alexander wrote:
>
> I'd like to nominate Timur Pocheptsov for approver status.
+1 from me too :)
- Paul
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo
On Friday 5. December 2014 10.56.48 Thiago Macieira wrote:
> Was there anyone who did not get seconded?
No. You approved all of them. :)
- Paul
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/developm
On Thursday 23. October 2014 19.03.32 Oswald Buddenhagen wrote:
> just to be clear, everybody is expected to use these scripts after they
> leave the beta phase.
> this will be technically enforced at some point.
Sorry Ossi, your calendar is broken. It's not April the first today.
- Paul
On Monday 13. October 2014 11.36.43 Knoll Lars wrote:
> Qt WebView: Christian Strømme
+1
Christian: you need to work on self promotion, obviously :p
- Paul
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/list
On Tuesday 16. September 2014 07.31.01 Reinio Topi wrote:
> I'd like to nominate Venugopal Shivashankar and Nico Vertriest as approvers
> in the Qt Project.
+2
- Paul
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/ma
On Tuesday 03 June 2014 07:05:07 Blasche Alexander wrote:
> Hi Gatis,
>
> Thank you very much for stepping up. I have not seen any further volunteers
> and I think it is safe to assume that there won't be anybody else at the
> moment. I have set you up as the default assignee.
+2
I think I would
On Monday 28 April 2014 08:42:48 Blasche Alexander wrote:
> I renamed it on request. It was such a minor change that I didn't see an
> issue especially since the component doesn't have a default assignee.
> Obviously that is not the case.
No worries :) I may be using the components in a slightly n
On Friday 25 April 2014 17:27:23 Thiago Macieira wrote:
> I've just noticed that the "GUI: Input methods" component in JIRA has got
> an update now saying "(Non-Latin languages)". That is, it seems the
> purpose of that component has changed to mean complex input methods only.
>
> I've been reass
On Tuesday 01 April 2014 11:12:18 Koehne Kai wrote:
> So, here is what we will do:
> - create one branch named 'qt' out of current stable
> - block any other branches in gerrit
> - move on with this branch, and announce the current status of it (open for
> features, feature freeze, hardening...) on
On Thursday 20 March 2014 19:00:54 Cornelius Hald wrote:
> maybe someone
> already could make some assumptions based on the console output below.
[...]
> W/Qt (15487): kernel/qmetaobject.cpp:1458 (static bool
> QMetaObject::invokeMethod(QObject*, const char*, Qt::ConnectionType,
> QGenericRe
On Tuesday 18 March 2014 12:50:26 m...@rpzdesign.com wrote:
> Hello Development:
>
> I am newly arrived on Qt 5.2x scene and wanted to know how to contribute
> code, fixes,
> and testing for Qt 5.3.x of IOS and Android.
>
> Specifically, I want to focus on QT C++ <-> Objective C/Cocoa bridge
> an
On Tuesday 18 March 2014 10:12:35 André Bergner wrote:
> So what is the "official" way to render a QQuickView scene to an offscreen
> target while keeping it "alive"?
>
> I remember talking to somebody at the last Qt dev days in Berlin. He was
> suggesting some solution that should make this possi
On Wednesday 12 March 2014 10:57:19 Thiago Macieira wrote:
> Em qua 12 mar 2014, às 18:46:15, Martin Koller escreveu:
> > For me the code porting looks a bit "unfinished" due to this Q_WS
> > artefacts, so I just fear that problems arise.
>
> It's possible.
Yes, there are still probably some regr
On Monday 10 March 2014 09:20:14 Agocs Laszlo wrote:
> > > Question: when a QWidget now creates a QPainter on it, how does my QPA
> > > plugin know onto which QWindow it is currently acting, when there's only
> > > one paintDevice/one backing store ?
> As for the painting step, QPA has almost noth
On Wednesday 25 December 2013 01:53:14 BogDan wrote:
> Well, from your mail it looks like Ministro is a second class citizen
> deploying method which IMHO is not true at all. Bundling Qt libs into the
> apk is *one* of the official *ways*, meaning that Ministro is also *one* of
> the official *wa
On Tuesday 17 December 2013 08:52:59 Thiago Macieira wrote:
> On terça-feira, 17 de dezembro de 2013 11:42:56, Knoll Lars wrote:
> > Hi,
> >
> > I’d like to nominate Paul Tvete as the formal maintainer of the QPA
> > architecture. He’s the original architect behind it anyway, and I don’t
> > think
On Tuesday 12 November 2013 13:03:30 Guido Seifert wrote:
> > Which version of Qt is this? It works for me with QT += svg only, with the
> > latest dev branch.
>
> qt-linux-opensource-5.2.0-beta1-android-x86-offline_2013-11-07_15-41-07-136.
> run
>
> Maybe it is fixed. But not to the time when I
On Monday 11 November 2013 17:19:43 Guido Seifert wrote:
> > It's a feature. :) To reduce the size of the package, we only deploy the
> > libraries that we know are necessary. Adding "QT += svg" to the .pro file
> > of your application should enable support for svg files.
>
> It does not. But it i
On Friday 08 November 2013 01:00:11 Guido Seifert wrote:
> I cannot display svg files in QML on Android.
>
> Unfortunately I am not experienced enough with Android/Qt to decide, whether
> this is my bug, or a Qt bug.
It's a feature. :) To reduce the size of the package, we only deploy the
librar
On Friday 25 October 2013 11:09:55 qtmail wrote:
> Qt 5.2 Beta, Could I customize thesize of apk?
>
> When create a QT Quick2 "hello world" on android,the apk size up to
> 10.6M, so
> Could I customize the libs? or all libs is /required/for QT Quick2?
As BogDan said, we are aiming to fix it befor
On Thursday 26 September 2013 17:12:09 Mandeep Sandhu wrote:
> I had pushed my changes to the ref- "refs/for/stable" (as shown in the
> Gerrit wiki page). Is that correct or do I need to send it to the 'dev'
> branch?
Stable is correct for bug fixes that target the upcoming release.
> Also, what
On Friday 23 August 2013 08:36:07 Blasche Alexander wrote:
> I looked into the desired workflow changes for Jira (as discussed on this
> list) and am doing some general cleanups [...]
Thank you, thank you. Thank you. Thank you! :)
- Paul
PS,
Thank you very very very much!
_
On Thursday 02 May 2013 16:30:47 Alan Alpert wrote:
> But if you're addressing this
> from a practical standpoint, just ask Robin to skip join/part events
> in what his bot publishes instead of losing the valuable dialogue as
> well.
+2 for not publishing join/part events, including the "*** ChanS
On Friday 15 February 2013 11:43:10 Stephen Kelly wrote:
> On Friday, February 15, 2013 12:28:32 Timo Jyrinki wrote:
> > At least qtpim, qtsystems, qtconnectivity, qtfeedback
> > and qtwayland will follow later, and I'll be filing change proposals
> > for them at that time as part of the process.
>
On Thursday 7 February 2013 09:44:38 Eskil Abrahamsen Blomfeldt wrote:
> On 02/06/2013 10:31 PM, Thiago Macieira wrote:
> > Hello
> >
> > Andreas is a long-time Qt developer. For those of you who haven't yet had
> > the pleasure of meeting him, he's the brains behind the original
> > implementatio
On Wednesday 6 February 2013 09:41:46 Paul Olav Tvete wrote:
> On Wednesday 6 February 2013 09:00:41 Thomas McGuire wrote:
> > A workaround would be to squash all commits of the branch together into a
> > single patch and then upload that to Gerrit for review. Now, actually
> >
On Wednesday 6 February 2013 09:00:41 Thomas McGuire wrote:
> A workaround would be to squash all commits of the branch together into a
> single patch and then upload that to Gerrit for review. Now, actually
> pushing the single patch would lose history, so we'd instead manually do a
> proper mer
One of the major features for Qt 5.1 is Android support. We have been doing
the work in a feature branch, and are now getting ready to integrate to the
dev branch. To beat the rush of integrations before feature freeze, we aim to
start the integration in two weeks time.
Most of the changes are
On Thursday 31 January 2013 13:08:11 Oswald Buddenhagen wrote:
> as i stated before, i'm driving forward a process to decide the
> execution details of a previously made decision.
Since this decision process has been unnoticed by the people I have asked:
Would you mind giving a reference to where
On Wednesday 30 January 2013 07:58:25 Thiago Macieira wrote:
> On quarta-feira, 30 de janeiro de 2013 17.17.46, Mumtaz Ahmad wrote:
> > Hi,
> >
> > I am trying to run rasterwindow example using minimal plugin but i am
> > getting null paint device
> > QPainter::begin: Paint device returned engine
On Thursday 24 January 2013 21:18:30 Hausmann Simon wrote:
> There haven't fortunately been any objections yet to this proposal, also
> unfortunately also no approval yet from a Qt maintainer. Anyone willing to
> approve the inclusion?
How about I propose it and you approve? :)
- Paul
___
On Tuesday 8 January 2013 15:49:32 Laszlo Papp wrote:
> I personally expected that you need this list for something permanent that
> is out of the scope for the existing mailing lists, like development@, qt-
> components@, and so forth. I still did not get any examples what development
> cannot
On Tuesday 8 January 2013 15:13:38 Laszlo Papp wrote:
> We do not have separate lists for Mac, QNX, Windows, Linux, Harmattan,
> Symbian and so forth so far, so I am wondering: what exactly would not fit
> the existing mailing lists?
This is a new project, and we need a convenient way to com
Hi all,
Now that we have merged the newdocs branches to master, it is time to polish
up the documentation for the final release. Lars already put this better than I
could:
On Monday 19 November 2012 20:09:35 Knoll Lars wrote:
> However, there is still significant work still to write many overvi
On Thursday 25 October 2012 12:16:40 Rafael Roquetto wrote:
> Afaik QCoreApplication::watchUnixSignal() seems to be no longer used, at
> least in Qt5. If that is really the case, would anyone object doing away
> with it (and removing the overhead from QEventDispatchUnix::doSelect() and
> co.)? Othe
On Wednesday 24 October 2012 11:51:09 Jørgen Lind wrote:
> I'm stepping down as the maintainer of QtWayland, as I don't have time
> to ensure that QtWayland is in top notch shape.
I'm sad to hear that, but it's not completely unexpected. Thank you very much
for all the brilliant work and enthusi
On Thursday 02 August 2012 10:31:59 ext Olivier Goffart wrote:
> If that's only a documentation problem, we can workaround that with some
> macro magic.
Very good point. For some reason I thought we would have to hack on qdoc
itself,
but creative use of \fn and \internal should be enough.
> Sh
On Thursday 02 August 2012 07:53:25 ext gunnar.sle...@nokia.com wrote:
> On Aug 1, 2012, at 6:37 PM, ext Stephen Kelly wrote:
> > Hi there,
> >
> > Given that https://codereview.qt-project.org/#change,31387 has been
> > merged, can you post any more information that will last until the
> > QColorP
On Tuesday 24 July 2012 17:15:37 Girish Ramakrishnan wrote:
> On Mon, Jul 23, 2012 at 4:31 AM, wrote:
> > How about a third solution, that only exposes the three methods that are
> > being used by QTestLib? We could turn QWSI into a namespace, and forward
> > declare the required methods in qtes
On Friday 22 June 2012 11:09:25 ext Donald Carr wrote:
> The Raspberry Pi is also meant to have a discrete (and apparently
> meaty) OpenVG processor that is currently lying dormant.
This turns out not to be the case after all. In the OpenVG session, we were
informed that the Raspberry Pi does act
On Thursday 19 April 2012 14:45:29 ext Girish Ramakrishnan wrote:
> Paul did say on irc this proposal sounds 'better', but I am not sure
> that means I have his +2. Is this any better? (read: compromise)
At least it means that I am withdrawing my -1 :)
- Paul
_
On Wednesday 18 April 2012 16:18:09 ext casper.vandonde...@nokia.com wrote:
> Just for my mental state of mind: will these classes then be documented as
> normal classes, or \internal, or do we need something special for them
> still?
They should not be documented as normal classes. \internal is f
On Tuesday 17 April 2012 03:57:16 ext Girish Ramakrishnan wrote:
> As per the previous discuss, I renamed all the _qpa.h to _p.h with a
> couple of helper scripts
I just added the following "-1" comment on gerrit:
I do not agree with this change. We have made a difference between public API
an
58 matches
Mail list logo
