Oh, thanks for sharing it. For the first time we have something that really
points to fscache, or at least has it in the logs. I suggest to replace NFS +
fscache, with a distributed files system with _good_ local caching (could be
cephfs?). The current setup requires only that used part of image
On czwartek, 7 grudnia 2017 12:17:16 CET Adam Treat wrote:
> Hi,
>
> I think it is high time that we fix the underlying problem: supporting
> atomic commits across submodules.
As I'm not against the idea, I'm not really fan of it either. The problem with
atomic commits across submodules is that t
On piątek, 1 września 2017 08:38:19 CEST Thiago Macieira wrote:
> I'm also wondering if we shouldn't have a bigger repo for IoT-related
> things, instead of creating a small one for each thing.
Currently, from CI and releasing perspective heaving dozen of small repos is
easier and faster. All th
On tirsdag 1. august 2017 15.11.38 CEST Thiago Macieira wrote:
> No, another problem has now appeared:
>
> Module "qt/qtbase" (34adca0607ff9231b4c79949353827c1c8319c52) Failed
> repeatedly to launch build/test agent:
> Failed 7 times to acquire the hardware
> buildKey: qt/qtbase/eab0f32
On mandag 31. juli 2017 13.24.57 CEST Laszlo Agocs wrote:
> Hi,
>
> Are we sure that the week before the 5.10 feature freeze date is really the
> best time to do this?
>
> Cheers,
> Laszlo
>
Hi,
Well, it is not the worst either. Currently, the integration count is quite
low, but the most im
On mandag 24. april 2017 14.05.17 CEST Sean Harmer wrote:
> Hi,
>
> are there any plans to reduce/remove the redundancy when writing
> documentation for both C++ and QML? Seems a waste of time to have to
> copy/paste or update the docs twice for both languages when really the
> only things differi
On tirsdag 10. januar 2017 11.37.56 CET Simon Hausmann wrote:
> (2) I really wish the placement of the configuration files for the
> platforms being moved to qt5.git had a high priority, because it prevents
> situations like these where the R&D organization, the project, contributors
> and part
On torsdag 10. november 2016 12.29.12 CET Oswald Buddenhagen wrote:
> the easiest would be going with the normal approval rights, but limit
> the submit button to a "QUIP owners" group which would consist of lars
> (and possibly a _few_ deputies).
Considering expected traffic there it could be onl
On torsdag 10. november 2016 11.39.14 CET Arnaud Vrac wrote:
> Hi,
>
> I'm trying to run MaintenanceTool on my Qt commercial install and it fails,
> apparently because the SSL certificate to cdn.qt.digia.com has expired.
> This also prevents using the online installer.
>
> Can this please be fixe
On torsdag 3. november 2016 09.17.57 CET Milla Pohjanheimo wrote:
> I would like to challenge you a bit about removal of (some of) the
> blacklisted autotests.
> (...)
Hi,
In your email you wrote that blacklisted is just a burden for CI. In
general it is true, but mark that currently they
On onsdag 26. oktober 2016 11.28.28 CEST Oswald Buddenhagen wrote:
> that's indeed better in the optimal case:
> 1. prepare downstream module and update upstream module
> 2. have them integrated into qt5. make sure that the upstream update
>does not go in before the downstream adjustment (you c
On tirsdag 13. september 2016 08.25.10 CEST Jędrzej Nowacki wrote:
> On fredag 19. august 2016 08.52.59 CEST Jędrzej Nowacki wrote:
> > On torsdag 18. august 2016 17.46.41 CEST Dominik Holland wrote:
> > > How are the dependencies managed for projects/modules which are not par
On mandag 19. september 2016 09.20.48 CEST Thiago Macieira wrote:
> This code was there in Qt 5.0, so I kept it when I refactored the numeric
> comparisons. Now, dealing with QTBUG-56073, I'm wondering if it should be
> there in the first place.
>
> Should we do fuzzy comparisns in QVariant?
>
>
On fredag 23. september 2016 11.22.08 CEST Olivier Goffart wrote:
> template
> auto registerEqualityOperator()
> -> decltype(std::declval() == std::declval())
I have tried it already. Sadly it breaks terribly in case of private/protected
operators. It doesn't solve the problem,
On mandag 19. september 2016 11.14.51 CEST Chris Adams wrote:
> Hi,
>
> Recently, a few unit test failures[1] in the (unreleased) QtPIM module
> showed that the recent change[2] which changes the semantics of null
> assignment (from JS) to a QVariant Q_PROPERTY can affect existing client
> code.
>
On lørdag 24. september 2016 20.58.38 CEST Thiago Macieira wrote:
> A thread[1] on the interest mailing list started when someone asked for the
> docs for the current format of the QDataStream wire protocol, to which I
> replied that it doesn't exist as we don't maintain such docs.
>
> Long story
On mandag 12. september 2016 14.39.57 CEST Orgad Shaneh wrote:
> On Tue, Sep 6, 2016 at 12:56 PM, J-P Nurmi wrote:
> > On 06 Sep 2016, at 11:46, Konstantin Tokarev wrote:
> > > 06.09.2016, 12:44, "Oswald Buddenhagen" :
> > >>> On Mon, Sep 05, 2016 at 09:17:59PM +, J-P Nurmi wrote:
> > >>> On
On fredag 19. august 2016 08.52.59 CEST Jędrzej Nowacki wrote:
> On torsdag 18. august 2016 17.46.41 CEST Dominik Holland wrote:
> > How are the dependencies managed for projects/modules which are not part
> > of the qt5.git but are part of coin ?
> >
> > Dominik
On torsdag 1. september 2016 15.22.29 CEST Marc Mutz wrote:
> Hi,
>
> Twice in succession.
>
> Any idea what's happening?
>
> Thanks,
> Marc
Yes, more or less. vSphere is overloaded and it shows that it doesn't like
it... Anyway write a bug report for it. Especially if you see it again. As for
On onsdag 24. august 2016 15.23.01 CEST Marc Mutz wrote:
> Hi,
>
> Currently, it's not, which doesn't make much sense, does it?
>
> So,
>
> template
> int qMetyTypeId() {
> return qMetaTypeIdHelper::type>();
> }
>
> ?
>
> (There's of course a lot more involved in this, registration
On torsdag 18. august 2016 17.46.41 CEST Dominik Holland wrote:
> How are the dependencies managed for projects/modules which are not part
> of the qt5.git but are part of coin ?
>
> Dominik
That is the reason of migrating "slowly". We need to define/find a product
repository for them. Such super
Hi,
Short version:
We plan to migrate from using sync.profile to qt5/.gitmodules in Coin, so
please make sure that the files are in sync and that they contain sensible
informations in every actively maintained branch.
Long version:
Currently, for every integration Coin is reading module dep
On fredag 12. august 2016 10.52.52 CEST Marc Mutz wrote:
> Hi,
>
> I'd like to know what the rules are supposed to for submitting to 5.6 (LTS).
>
> Should we enforce the strict rules of other minor releases (only regressions
> and P2+)?
I strongly believe that autotests improvements should go to
On Tuesday 02 of August 2016 17:17:59 Thiago Macieira wrote:
> On quarta-feira, 3 de agosto de 2016 01:05:00 PDT Giuseppe D'Angelo wrote:
> > On Thu, Jul 28, 2016 at 10:06 AM, Michal Klocek
wrote:
> > > It seems to happen in different modules (here qttools and qtlocation)
> > > and in different b
On Wednesday 27 of July 2016 13:58:44 Dominik Holland wrote:
> Hi,
>
> Am 07/27/2016 um 01:47 PM schrieb Jędrzej Nowacki:
> > Hi,
> >
> > Good news everyone! Last month we managed to deploy a new automatic
> >
> > provisioning system to Coin. What
Hi,
Good news everyone! Last month we managed to deploy a new automatic
provisioning system to Coin. What does it mean to you? Now you can modify
existing VM templates used by Coin. Installing additional packages should be
trivial and more or less safe from now.
I. The goal:
- Coin shoul
On Wednesday 27 of July 2016 08:28:08 Friedemann Kleint wrote:
> Hi,
>
> to summarize for Windows:
>
> - Crashes have been observed over time in various tests, mostly in
> QtCore (QDir,QFile, QProcess see fex
> https://bugreports.qt.io/browse/QTBUG-47370
>
> - It only affects 64bit (!) (correct
On Tuesday 26 of July 2016 15:30:48 Thiago Macieira wrote:
> Em terça-feira, 26 de julho de 2016, às 23:24:21 PDT, Giuseppe D'Angelo
>
> escreveu:
> > On Mon, Jul 25, 2016 at 5:51 PM, Thiago Macieira
> >
> > wrote:
> > > Let's pay attention of what crashes and where. But we'll need to
> > > repr
On Monday 25 of July 2016 10:27:30 Thiago Macieira wrote:
> On segunda-feira, 25 de julho de 2016 08:51:36 PDT Thiago Macieira wrote:
> > On segunda-feira, 25 de julho de 2016 14:07:04 PDT Jędrzej Nowacki wrote:
> > > Ugh I haven't seen link.exe crashing, but in case of moc
On Friday 22 of July 2016 13:25:19 Thiago Macieira wrote:
> For the past month or so, I've noted an increase in the number of crashes in
> applications that shouldn't be otherwise crashing. I first saw it with moc
> (Segmentation fault) and I thought my change was at fault. But it's been
> happenin
On Wednesday 20 of July 2016 13:50:49 Olivier Goffart wrote:
> On Montag, 18. Juli 2016 23:15:22 CEST Konrad Rosenbaum wrote:
> > Hi,
> >
> > On Monday 18 July 2016 07:59:21 Jędrzej Nowacki wrote:
> > > On Saturday 16 of July 2016 13:56:00 Konrad Rosenbaum
On Saturday 16 of July 2016 13:56:00 Konrad Rosenbaum wrote:
> Hi,
>
> I am currently interfacing two libraries that only have QVariant in common,
> most of the (value) types getting exchanged are either Qt containers or
> Q_GADGETs.
>
> I was relatively quick to realize that I needed the QMetaTy
On Wednesday 13 of July 2016 10:44:13 Alexander Blasche wrote:
> Hi,
>
> Yesterday, I stumbled over a break in QtSerialBus due to the addition of new
> QTimer::setInterval(..) overloads in qtbase/dev. This was introduced by
>
> https://codereview.qt-project.org/#/c/160889/
>
> Unfortunately this
On Tuesday 21 of June 2016 10:47:29 Jędrzej Nowacki wrote:
> On Thursday 16 of June 2016 16:22:15 Jędrzej Nowacki wrote:
> > There is datacenter hardware maintenance break on Tuesday 21st of June
> > (6am-8am UTC+3), Coin will be shutdown a bit earlier and hopefully restart
> &
On Thursday 16 of June 2016 16:22:15 Jędrzej Nowacki wrote:
> There is datacenter hardware maintenance break on Tuesday 21st of June
> (6am-8am UTC+3), Coin will be shutdown a bit earlier and hopefully restart
> after.
> Cheers,
> Jędrek
Seems that something got completely broke
There is datacenter hardware maintenance break on Tuesday 21st of June
(6am-8am UTC+3), Coin will be shutdown a bit earlier and hopefully restart
after.
Cheers,
Jędrek
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/
On Thursday 16 of June 2016 06:57:50 Tony Sarajärvi wrote:
> Hi,
>
> Our aim was to get new platforms in immediately after the previous platforms
> branched away from dev branch. Meaning, when 5.7 branch was created and it
> branched away from dev branch, all new platforms aiming for 5.8 should ha
On Wednesday 01 of June 2016 15:44:22 Marc Mutz wrote:
> > Subjective reasons against trailling commas:
> > - It's ugly
>
> I beg your pardon? Trailing commas are ugly? So where's the text editor
> that folds prose text to have commas on the next line?
Aesthetics are subjective by definition, you
On Wednesday 01 of June 2016 15:16:01 Andreas Aardal Hanssen wrote:
> > Den 1. jun. 2016 kl. 15.06 skrev Mark Gaiser :
> > ...
> > Funny in the coding style you mention. For operators: "An operator at the
> > end of the line is easy to miss if the editor is too narrow." The exact
> > same could be
On Monday 30 of May 2016 10:19:38 Marc Mutz wrote:
> On Sunday 29 May 2016 18:05:07 Thiago Macieira wrote:
> > I've just pushed a feature[1] to moc that makes it process multiple
> > headers
> > at the same time, producing only one output file
>
> Separate compilation is not how I would recommend
Yes and I fixed them all on Friday with a "catch all" command. I have no clue
how just one integration could stay locked.
Cheers,
Jędrek
On Tuesday 17 of May 2016 12:49:17 Oswald Buddenhagen wrote:
> On Tue, May 17, 2016 at 06:08:50AM +, Simon Hausmann wrote:
> > I just looked into it and i
> Determining architecture... ()
> make: Warning: File `../../../qt/qtbase/config.tests/arch/arch.pro' has
> modification time 1.3e+03 s in the future
> /home/qt/work/build/bin/qmake -qtconf /home/qt/work/build/bin/qt.conf
> -nocache -spec /home/qt/work/qt/qtbase/mkspecs/linux-g++ LIBS+=
> QMAKE_CX
On Tuesday 03 of May 2016 14:54:50 Sean Harmer wrote:
> On Monday 02 May 2016 11:14:24 Jędrzej Nowacki wrote:
> > On Saturday 30 of April 2016 20:26:20 Sean Harmer wrote:
> (...)
> What would be a *very* useful feature would be if we can trigger a test
> build of a chan
On Saturday 30 of April 2016 20:26:20 Sean Harmer wrote:
> Hi,
Hi,
> after yet another 5 hour wait just to be greeted with yet another random
> failure with no build logs I'm getting really tired of the poor reliability
> of the Qt CI system.
I'm sorry about that.
> https://codereview.qt-project
On Thursday 17 of March 2016 12:29:46 André Somers wrote:
> Op 17/03/2016 om 11:24 schreef Mathias Hasselmann:
> > Am 17.03.2016 um 10:01 schrieb Sorvig Morten:
> >> How about treating the coding guidelines as \internal documentation?
> >> We could then at some point build and publish it together w
On Friday 18 of March 2016 09:13:13 Knoll Lars wrote:
> I’m all for an automated solution for code formatting, so we can remove
> discussions/comments about wrongly placed braces or spaces from code review
> and can rather focus more on the content. But there will be still a need
> for some coding
Hi,
> Just fast update on the issue. I thought that this is fixed:
> http://testresults.qt.io/coin/integration/qt/qtbase/tasks/1456811813.thrift_
> bin Thanks for pointing it out. Time handling in virtualiazed environment is
> not reliable, and sometimes source packages are created in future... An
On Sunday 06 of March 2016 09:16:13 Sean Harmer wrote:
> As per the subject. Can the sysadmins please install a new certificate
> please?
>
> Sean
> --
> Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK
> Klarälvdalens Datakonsult AB, a KDAB Group company
> Tel. Sweden (HQ) +46-563-540
On Monday 29 of February 2016 08:38:30 Thiago Macieira wrote:
> On segunda-feira, 29 de fevereiro de 2016 10:09:51 PST Jędrzej Nowacki
wrote:
> > On Friday 26 of February 2016 15:56:08 Thiago Macieira wrote:
> > > > I.e. what problems would we get from having to install
On Friday 04 of March 2016 13:22:05 Ulf Hermann wrote:
> > The option is being evaluated. The main problem is that it seems that the
> > installer size grows 2x with force-debug-info enabled, we need to confirm
> > that it is not the case.
>
> You can add the debug symbols as optional separate pac
On Wednesday 02 of March 2016 09:00:35 Gunnar Roth wrote:
> >On 2016-03-01, Milian Wolff wrote:
> >> b) Apparently there are never any debug symbols shipped for the release
> >> build fo Qt. Having debug symbols even for a release build is crucial
> >> for a good profiling experience. Could we may
On Tuesday 01 of March 2016 14:15:30 Tim Blechmann wrote:
> hi all,
>
> it seems that i cannot integrate changes into 5.6 anymore:
> > http://testresults.qt.io/coin/integration/qt/qtbase/tasks/1456811813.thrif
> > t_bin
> seems that i'm always hitting a timeout somewhere ... is this a known
> issu
On Monday 29 of February 2016 11:11:28 Иван Комиссаров wrote:
> 2016-02-26 11:43 GMT+03:00 Jędrzej Nowacki > On Thursday 25 of February 2016 19:22:55 Milian Wolff wrote:
> >
> > The thought evolved over last months and now I think that QAIM should not
> > be
> >
On Friday 26 of February 2016 15:56:08 Thiago Macieira wrote:
> > I.e. what problems would we get from having to install the
> > moc files?
>
> Lots.
And probably all go away if instead of installing anything we use
QMetaObjectBuilder (assuming it's api stabilization). Yes it would have
perform
On Thursday 25 of February 2016 19:22:55 Milian Wolff wrote:
> On Donnerstag, 25. Februar 2016 09:02:11 CET Thiago Macieira wrote:
> > On quinta-feira, 25 de fevereiro de 2016 17:33:52 PST Cristian Adam wrote:
> > > This might be a burden for some of the Qt developers (Windows ones).
> > >
> > > B
On Friday 26 of February 2016 00:16:35 Shaw Andy wrote:
> I was creating another bug report earlier today in JIRA and I noticed that
> it was assigning to someone who didn't seem to be right for the component
> at all since I don't believe they are the maintainer for it and I recalled
> that this i
On Thursday 25 of February 2016 09:56:01 Smith Martin wrote:
> Send ideas for upgrading the Qt documentation to C++11.
>
> 1. Which C++11 constructs will be used in Qt?
All of them, in longer run C++14 too :-)
> 2. Which of these should appear in the documentation?
I do not understand the question
On Monday 01 of February 2016 15:16:33 you wrote:
> I am a great fanboy of algorithms and the STL, as should be clear by now
You are excused ;-) But seriously I do not think there is anything wrong about
it, STL is a bit obscure, but fast and sometimes a code needs to be fast.
> But I find the i
On Monday 01 of February 2016 11:08:54 Marc Mutz wrote:
> Hi,
>
> We're seeing increasing use of lambdas in dev, and I'm a bit unhappy about
> the result.
>
> E.g. (not picking on Anton here, I have done the same before):
>
> auto firstEqualsName = [&name](const QPair &header)
> {
> retur
On Thursday 28 of January 2016 12:37:14 Hausmann Simon wrote:
> Regarding the server that is used for Qt 5.6 and onwards: It is an exact
> clone of the virtual machine that ran in Jenkins with no changes to the
> services, but it is in a different virtual network segment.
It is exactly the same,
On Friday 22 of January 2016 08:50:52 Thiago Macieira wrote:
> On Friday 22 January 2016 11:26:55 Bogdan Vatra wrote:
> > AFAIK C++11/14 compilers have zero-cost exception, so, is there any reason
> > why not start using them in Qt 6.0 ?
>
> Yes. There's a couple of man-decades worth of work to m
On Tuesday 19 of January 2016 13:51:56 Marc Mutz wrote:
> On Tuesday 19 January 2016 11:15:43 Milian Wolff wrote:
> > On Dienstag, 19. Januar 2016 11:51:42 CET Marc Mutz wrote:
> > > I missed one:
> > >
> > > On Monday 18 January 2016 23:43:37 Marc Mutz wrote:
> > > > #include
> > > > #in
On Thursday 14 of January 2016 06:39:29 Thiago Macieira wrote:
> On Thursday 14 January 2016 10:15:40 Jędrzej Nowacki wrote:
> > I guess the whole point of having Ubuntu 14.04 LTS in CI is to support
> > that
> >
> > platform as long as it is important. As yo
On Monday 11 of January 2016 00:27:08 Pier Luigi Fiorini wrote:
> Hi,
>
> We are starting to have QtWayland patches that require at least Wayland 1.6
> available, such as:
>
> - https://codereview.qt-project.org/#/c/104222/
> - https://codereview.qt-project.org/#/c/112141/
> - https://codereview.
And every small, movable object kept in QVariant is affected. QMetaType also
keeps pointers to functions defined in plugins if such register a type. I
believe that we had that discussion around Qt4->Qt5 migration. Unloading
plugins is not safe, sometimes it works but still it is very tricky. I a
On Wednesday 29 of July 2015 10:31:01 Marc Mutz wrote:
> Hi,
>
> Example: https://codereview.qt-project.org/95533
>
> Output link posted there:
> http://testresults.qt.io/logs/qt/qtbase/98ca8036c6d5b37be676503e463c49e8dcc9
> c5de/windows8x86_64winrt8x86_64msvc2013developer-
> build_release_disabl
On Wednesday 24 of June 2015 14:03:07 Zhang Qun wrote:
> QMetaType::registerType: Binary compatibility break -- Size mismatch for
> type 'QPaintBufferCacheEntry' [1024]. Previously registered size 0, now
> registering size 16.
Hi,
It looks like a build issue, qt library version mismatch... Does
On Friday 28 of November 2014 13:55:44 Simon Hausmann wrote:
> On Friday 28. November 2014 12.41.47 Olivier Goffart wrote:
> > On Friday 28 November 2014 12:19:45 Simon Hausmann wrote:
> > > Hi,
> > >
> > > Monsieur Goffart did awesome work in the dev branch on allowing
> > > structures
> > > with
On Friday 24 of October 2014 11:37:29 Oswald Buddenhagen wrote:
> On Fri, Oct 24, 2014 at 10:26:20AM +0200, Jędrzej Nowacki wrote:
> > On Thursday 23 of October 2014 19:03:32 Oswald Buddenhagen wrote:
> > > just to be clear, everybody is expected to use these scripts after th
On Thursday 23 of 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.
Hi,
Now, you got my attention. To be honest I'm a bit surprised. Personally I
di
On Saturday 02 of August 2014 14:53:10 Lisandro Damián Nicanor Pérez Meyer
wrote:
> Just for the record, I'm also seeing this while compiling:
>
> /home/lisandro/qtcreator/src/plugins/qmldesigner/designercore/model/qmltextg
> enerator.cpp: In member function 'QString
> QmlDesigner::Internal::Qml
On Monday 21 of July 2014 23:12:04 Olivier Goffart wrote:
> Hi,
>
> I just debugged a quite weird bug with QueuedConnection and foinction
> pointer base connection.
>
> There is a compiler bug in clang 3.4 with precompiled header.
> Normally, a static variable within a template should have a diff
On Thursday 17 of July 2014 13:33:49 Daniel Teske wrote:
> On Thursday 17 Jul 2014 13:28:10 Jędrzej Nowacki wrote:
> > On Thursday 17 of July 2014 10:51:03 you wrote:
> > > QVariant::operator== is not symmetric
> > >
> > > QDateTime d
On Thursday 17 of July 2014 10:51:03 you wrote:
> QVariant::operator== is not symmetric
>
> QDateTime dateTime = QDateTime::currentDateTime();
> QTime time = dateTime.time();
>
> qDebug() << (QVariant(dateTime) == QVariant(time));
> qDebug() << (QVariant(time) == QVariant(dateTim
On Wednesday 16 of July 2014 06:37:25 Ziller Eike wrote:
> I don’t think we have a single place in Qt Creator where we want automatic
> conversions when using QVariant. A search for QVariant(Map) returns 5400
> hits. In the map case, we usually expect the one retrieving the value for a
> key to kno
On Wednesday 16 of July 2014 12:51:36 Olivier Goffart wrote:
> On Wednesday 16 July 2014 10:06:52 Poenitz Andre wrote:
> > Jędrzej Nowacki wrote:
> > > Eike wrote:
> > > > [...]
> > > >
> > > >>> We use common sense on a case by c
On Wednesday 16 of July 2014 08:41:07 Poenitz Andre wrote:
> Olivier Goffart wrote:
> > > > I'd say yes, for sensible conversion
> > > > You are right that it is a behaviour change, but i think it is worth
> > > > changing it.
> > >
> > > Why?
> > >
> > > On one hand you promise binary compatibil
On Wednesday 16 of July 2014 06:37:25 Ziller Eike wrote:
> [...]
> > When one use QVariant, it is because we want to enjoy dynamic typing and
> > nice conversions.
>
>
> I don’t think we have a single place in Qt Creator where we want automatic
> conversions when using QVariant. A search for QV
On Tuesday 15 of July 2014 10:38:52 Poenitz Andre wrote:
> Olivier Goffart wrote:
> > Jędrzej Nowacki wrote:
> > > 1. Are we allowed to add new conversions?
> > >
> > > The question is tricky because adding a new conversion is a
> > >
On Tuesday 15 of July 2014 11:59:03 Olivier Goffart wrote:
> > 1.3 Should we try to support a user's type conversions out of the
> >box?
> > Currently a user needs to manually register a conversion function
> >
> > so Qt can know it and use it. For certain types we can do much better
Hi,
I would like to discuss type conversions in Qt. As you may know, Qt has
the ability to convert a known type to another known type. This works for
trivial cases like, for example, "int" to "long", but also for more complex
ones like "QByteArray" to "QString" or "CustomType" to "OtherCust
On Monday 30 of June 2014 09:48:05 Stephen Kelly wrote:
> On Friday, June 27, 2014 14:50:39 you wrote:
> > Hi,
> >
> > It seems that Jocelyn answered most of the questions, but I put my
> > answers
> >
> > anyway :-)
> >
> > On Wednesday 25 of June 2014 15:42:36 Stephen Kelly wrote:
> > > (.
On Monday 30 of June 2014 10:06:12 Olivier Goffart wrote:
> On Sunday 29 June 2014 16:19:59 Lisandro Damián Nicanor Pérez Meyer wrote:
> > No if it uses private headers.
> >
> > I currently need to rebuild on all arches gammaray, fcitx-qt and pyqt5
> > each
> > time I upload a new point release fo
On Sunday 29 of June 2014 16:19:59 Lisandro Damián Nicanor Pérez Meyer wrote:
> > That's of course only the binary installer ... I can't judge whether e.g.
> > distributions would appreciate separate releases of QtWebEngine.
>
> No if it uses private headers.
>
> I currently need to rebuild on al
Hi,
It seems that Jocelyn answered most of the questions, but I put my answers
anyway :-)
On Wednesday 25 of June 2014 15:42:36 Stephen Kelly wrote:
> (...)
>> Conclusion 1) Even if a Qt module has a disparate version scheme, bumping
> its major version and changing its SONAME are not acceptabl
On Thursday 12 of June 2014 18:24:38 Thiago Macieira wrote:
> > > if we modularize the repos more, we need to go full monty and modularize
> > > *everything*.
> > > i really wouldn't want to do that with the current build system.
> >
> >
> >
> > I guess it would be a nice long term goal.
>
> I'm
On Thursday 12 of June 2014 11:47:49 Oswald Buddenhagen wrote:
> On Thu, Jun 12, 2014 at 10:40:03AM +0200, Jędrzej Nowacki wrote:
> > Hi,
> >
> > Thanks for sending the notes :-) I have a question about this point:
> > > Move QtNetowrk into its own git modules
&
Hi,
Thanks for sending the notes :-) I have a question about this point:
> Move QtNetowrk into its own git modules
>Thiago: Network cannot swapped out into its own module, due to dbus
>reqiring it in the future
Why dbus can not be moved to a separate module or together with networking
On Friday 16 of May 2014 12:33:49 Ben Lau wrote:
> Why? Is there any special reason to implement in this order? or it is a bug?
It look like a bug.
Cheers,
Jędrek
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mail
On Wednesday 14 of May 2014 08:01:33 Oliver Wolff wrote:
> On 13/05/2014 16:47, Thiago Macieira wrote:
> > Em ter 13 maio 2014, às 09:57:59, Knoll Lars escreveu:
> >>> That won't help unless we also disable the revdep for QtQuick, as
> >>> QtQuick
> >>> depends on QtNetwork.
> >>
> >> That doesn’t
On Friday 25 of April 2014 13:03:33 Richard Moore wrote:
> On 25 April 2014 11:51, Alberto Mardegan wrote:
> > For instance, I would like to have a GeoPoint type with "latitude" and
> > "longitude" properties; if I exposed it as a QVariantMap, I wouldn't be
> > able to prevent the QML code from doi
On Friday 11 of April 2014 08:31:41 Rutledge Shawn wrote:
> On 11 Apr 2014, at 10:11 AM, Poenitz Andre wrote:
> > shawn.rutle...@digia.com wrote:
> >> On 10 Apr 2014, at 7:20 PM, Frederik Gladhorn wrote:
> >>> Hi all,
> >>>
> >>> I just started to port accessibility to the new and shiny categorize
On Monday 06 of January 2014 17:23:43 Frederik Gladhorn wrote:
> Hello,
>
> we (some of us at Digia) have been working on Enginio - a convenient cloud
> storage for Qt applications. Since the library is actively maintained we
> would like to integrate it into the official Qt release for Qt 5.3.
>
93 matches
Mail list logo
