[Development] Deprecation of Qt Canvas3D in 5.12

[Miller, Douglas K. CONT NAVAIR 2109, 1, N139]

I just realized from the Qt 5.12 New Features posting that Qt Canvas 3D will be 
deprecated in 5.12.  I'm working on my second application that uses it now and 
I'm concerned that the decision to deprecate it has been made too hastily.  The 
real advantage I see in using it is that it offers a three.js development 
environment which is higher level, has plethora of code that can be easily 
ported to the Qt Canvas 3D, is well documented, has a lot of books published 
for it.  It seems to be the most productive way to do 3D graphics programming 
in Qt unless there is a need for higher performance.  Qt 3D has several 
advantages over Canvas 3D, but is disadvantaged in all the areas where I 
mentioned that Canvas 3D/Three.js excels.  So, can we please keep longer?
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Opinions on QTBUG-71545

[Luca Beldi]

I'm in favour of just adding a line of documentation and maybe include Thiago's 
workaround. Should take 30seconds and hurt nobody

Luca Beldi (VRonin)
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [HEADS UP] 5.12 locked down (Re: Merge and Integration status report - 2018.11.08)

[Thiago Macieira]

On Thursday, 8 November 2018 08:01:48 PST Oswald Buddenhagen wrote:
> On Thu, Nov 08, 2018 at 04:26:04PM +0100, Liang Qi wrote:
> > I thought qtbase 5.12 got locked since previous email. Looks like not,
> > or some people(with privilege) are still eager to hit the stage
> > button. I will not try more during tonight.
> 
> yes, because someone keeps re-adding thiago and several others to the
> release team's gerrit group. that's what you get when you let people
> without a system overview try to solve problems.

My bad.

I staged things at 7 am before reading the 4 am email.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center



___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [HEADS UP] 5.12 locked down (Re: Merge and Integration status report - 2018.11.08)

[Oswald Buddenhagen]

On Thu, Nov 08, 2018 at 04:26:04PM +0100, Liang Qi wrote:
> I thought qtbase 5.12 got locked since previous email. Looks like not,
> or some people(with privilege) are still eager to hit the stage
> button. I will not try more during tonight.
> 
yes, because someone keeps re-adding thiago and several others to the
release team's gerrit group. that's what you get when you let people
without a system overview try to solve problems.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [HEADS UP] 5.12 locked down (Re: Merge and Integration status report - 2018.11.08)

[Liang Qi]

> On 8 Nov 2018, at 13:00, Oswald Buddenhagen  wrote:
> 
> On Thu, Nov 08, 2018 at 08:29:47AM +, Liang Qi wrote:
>> I don't know how to use [Grafana] to show the statistic of qtbase 5.12
>> integrations in coin. There are only 3 successful integrations
>> yesterday: [...]
>> 
> because this situation has been persisting for weeks and we've been
> essentially just burning energy and motivation with doomed integration
> attempts, we decided to lock down 5.12 until the situation is under
> control. a somewhat optimistic ETA is maybe a week, depending on the CI
> team's progress with deploying infrastructure software updates (it's a
> bit more involved than it sounds, so bear with them).
> 
> if you have critical changes which justify spending extra effort to get
> them in soon, talk to liang.

I thought qtbase 5.12 got locked since previous email. Looks like not, or some 
people(with privilege) are still eager to hit the stage button. I will not try 
more during tonight.

—Liang

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Closing bugs as won't fix or out of scope

[Tuukka Turunen]

Hi,

Would be great if you add that info as a comment to the bug reports.

Yours,

Tuukka

From: Massimo Callegari 
Date: Thursday, 8 November 2018 at 15.05
To: Qt Project Development Mailing List , Tuukka 
Turunen 
Subject: Re: [Development] Closing bugs as won't fix or out of scope

Hello Tuukka,
on my end you can close the following.

https://bugreports.qt.io/browse/QTBUG-58987
https://bugreports.qt.io/browse/QTBUG-46707
https://bugreports.qt.io/browse/QTBUG-49788
https://bugreports.qt.io/browse/QTBUG-53580
https://bugreports.qt.io/browse/QTBUG-44923

I do believe Qt3D issues need some more love by maintainers.
For example https://bugreports.qt.io/browse/QTBUG-69721 is a plain regression 
reported on August 1st and completely ignored.

This can also be closed: https://bugreports.qt.io/browse/QTBUG-62578 (not 
reproduced anymore with recent Qt versions)

Thanks,
Massimo

Il giovedì 8 novembre 2018, 13:05:53 CET, Tuukka Turunen  
ha scritto:
Hi,

I was looking a bit into our older bugs and found quite many that in my opinion 
could be closed. We do not have a QUIP to define the policy of closing bugs 
currently, so this is a bit of a matter of viewpoint. In my opinion we should 
be more active in closing a bug that no-one has an intention of fixing. If the 
bug later turns out to be relevant to fix, it can always be re-opened.



Some of the bugs I was looking at were

· reported to happen in some exotic device, sometimes also quite old 
one (by now, if bug has been hanging for a long time)

· reported to happen only in an old version of the operating system

· fixed in a later version of Qt, but left open as bug was not feasible 
to fix in the version it was reported from

· reported for old version of Qt, and no longer relevant functionality 
in the current versions

· caused by a bug in the operating system

· maybe possible to fix, but with a risk of causing a regression or a 
behavior change

· such that would require a major rewrite of the functionality to fix

· not reproduceable any more (or reported by the user not to be able to 
reproduce)

· marked as duplicate, but both instances of the bug were open/reported 
state

· not actually bugs, but suggestions for new functionality reported as 
a bug (should be moved to be a suggestion)



Different persons have unique viewpoints to what kind of bug should be closed 
and what not. Keeping everything open until the reported issue fixed, is also a 
valid view, but that leads to a large number of bugs and can hinder getting the 
right understanding of what is planned to be fixed or finding the important 
items to fix. Of course sometimes we also simply forget to close a bug or some 
bug gets fixed in conjunction of other changes (and bug report is not closed).



I am not saying that we should necessarily close immediately all and every bug 
that match criteria I mentioned in the bullet list. What would be good is a bit 
more of a common agreement of what to do with the bugs that are not indented to 
be fixed (or at least very likely not going to be fixed).



Yours,



Tuukka
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Qt 5.12.0 Beta4 released

[ekke]

Am 08.11.18 um 13:38 schrieb Eike Ziller:
>
>> On 8. Nov 2018, at 13:04, ekke  wrote:
>>
>> just downloading Beta 4
>>
>> why is QtCreator 4.8.0 Beta-2 not available under "Preview" from Online 
>> Installer ?
> We haven’t released it yet.
> We would like to update Qt Creator to use Qt 5.12 before we release beta2, 
> and are facing infrastructure issues after performing some required updates 
> for that. We hope to have packages soon.
> Qt 5.11-based nightly packages are available at 
> http://download.qt.io/snapshots/qtcreator/4.8/4.8.0-beta2/
thx Eike,

now I understand it better - have overlooked that the 4.8.0-beta2
downloads are from nightly build snapshots

ekke
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Closing bugs as won't fix or out of scope

[Massimo Callegari via Development]

 Hello Tuukka,on my end you can close the following.
https://bugreports.qt.io/browse/QTBUG-58987
https://bugreports.qt.io/browse/QTBUG-46707
https://bugreports.qt.io/browse/QTBUG-49788
https://bugreports.qt.io/browse/QTBUG-53580
https://bugreports.qt.io/browse/QTBUG-44923

I do believe Qt3D issues need some more love by maintainers.For example 
https://bugreports.qt.io/browse/QTBUG-69721 is a plain regression reported on 
August 1st and completely ignored.
This can also be closed: https://bugreports.qt.io/browse/QTBUG-62578 (not 
reproduced anymore with recent Qt versions)
Thanks,Massimo
Il giovedì 8 novembre 2018, 13:05:53 CET, Tuukka Turunen 
 ha scritto:  Hi,
 
I was looking a bit into our older bugs and found quite many that in my opinion 
could be closed. We do not have a QUIP to define the policy of closing bugs 
currently, so this is a bit of a matter of viewpoint. In my opinion we should 
be more active in closing a bug that no-one has an intention of fixing. If the 
bug later turns out to be relevant to fix, it can always be re-opened.

 
 
 
Some of the bugs I was looking at were

   - reported to happen in some exotic device, sometimes also quite old one (by 
now, if bug has been hanging for a long time)
   - reported to happen only in an old version of the operating system
   - fixed in a later version of Qt, but left open as bug was not feasible to 
fix in the version it was reported from
   - reported for old version of Qt, and no longer relevant functionality in 
the current versions
   - caused by a bug in the operating system
   - maybe possible to fix, but with a risk of causing a regression or a 
behavior change
   - such that would require a major rewrite of the functionality to fix
   - not reproduceable any more (or reported by the user not to be able to 
reproduce)
   - marked as duplicate, but both instances of the bug were open/reported state
   - not actually bugs, but suggestions for new functionality reported as a bug 
(should be moved to be a suggestion)
 
 
 
Different persons have unique viewpoints to what kind of bug should be closed 
and what not. Keeping everything open until the reported issue fixed, is also a 
valid view, but that leads to a large number of bugs and can hinder getting the 
right understanding of what is planned to be fixed or finding the important 
items to fix. Of course sometimes we also simply forget to close a bug or some 
bug gets fixed in conjunction of other changes (and bug report is not closed).
 
  
 
I am not saying that we should necessarily close immediately all and every bug 
that match criteria I mentioned in the bullet list. What would be good is a bit 
more of a common agreement of what to do with the bugs that are not indented to 
be fixed (or at least very likely not going to be fixed).
 
  
 
Yours,
 
  
 
    Tuukka
 ___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
  ___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] [Qt-creator] Qt 5.12.0 Beta4 released

[Eike Ziller]

> On 8. Nov 2018, at 13:04, ekke  wrote:
> 
> just downloading Beta 4
> 
> why is QtCreator 4.8.0 Beta-2 not available under "Preview" from Online 
> Installer ?

We haven’t released it yet.
We would like to update Qt Creator to use Qt 5.12 before we release beta2, and 
are facing infrastructure issues after performing some required updates for 
that. We hope to have packages soon.
Qt 5.11-based nightly packages are available at 
http://download.qt.io/snapshots/qtcreator/4.8/4.8.0-beta2/

Br, Eike

> Am 08.11.18 um 11:52 schrieb Jani Heikkinen:
>> Hi,
>> 
>> We have released Qt 5.12.0 Beta4 today. As earlier you can get it via online 
>> installer. Delta to beta3 attached.
>> 
>> Please make sure you will report all findings in Jira. Please make sure all 
>> Qt 5.12.0 release blockers are visible in release blocker list (
>> https://bugreports.qt.io/issues/?filter=19961
>> ). Target is to get RC out 15th November so all fixes needs to be in latest 
>> Tue 13th November; there isn't that much time anymore to fix remaining 
>> blockers...
>> 
>> br,
>> Jani Heikkinen
>> Release Manager
>> 
>> 
>> 
>> 
>> 
>> ___
>> Development mailing list
>> 
>> Development@qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/development
> 
> ___
> Qt-creator mailing list
> qt-crea...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/qt-creator

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Rudower Chaussee 13
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Mika Harjuaho
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Closing bugs as won't fix or out of scope

[Tuukka Turunen]

Hi,

I was looking a bit into our older bugs and found quite many that in my opinion 
could be closed. We do not have a QUIP to define the policy of closing bugs 
currently, so this is a bit of a matter of viewpoint. In my opinion we should 
be more active in closing a bug that no-one has an intention of fixing. If the 
bug later turns out to be relevant to fix, it can always be re-opened.

Some of the bugs I was looking at were

  *   reported to happen in some exotic device, sometimes also quite old one 
(by now, if bug has been hanging for a long time)
  *   reported to happen only in an old version of the operating system
  *   fixed in a later version of Qt, but left open as bug was not feasible to 
fix in the version it was reported from
  *   reported for old version of Qt, and no longer relevant functionality in 
the current versions
  *   caused by a bug in the operating system
  *   maybe possible to fix, but with a risk of causing a regression or a 
behavior change
  *   such that would require a major rewrite of the functionality to fix
  *   not reproduceable any more (or reported by the user not to be able to 
reproduce)
  *   marked as duplicate, but both instances of the bug were open/reported 
state
  *   not actually bugs, but suggestions for new functionality reported as a 
bug (should be moved to be a suggestion)

Different persons have unique viewpoints to what kind of bug should be closed 
and what not. Keeping everything open until the reported issue fixed, is also a 
valid view, but that leads to a large number of bugs and can hinder getting the 
right understanding of what is planned to be fixed or finding the important 
items to fix. Of course sometimes we also simply forget to close a bug or some 
bug gets fixed in conjunction of other changes (and bug report is not closed).

I am not saying that we should necessarily close immediately all and every bug 
that match criteria I mentioned in the bullet list. What would be good is a bit 
more of a common agreement of what to do with the bugs that are not indented to 
be fixed (or at least very likely not going to be fixed).

Yours,

Tuukka
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.12.0 Beta4 released

[ekke]

just downloading Beta 4

why is QtCreator 4.8.0 Beta-2 not available under "Preview" from Online
Installer ?

Am 08.11.18 um 11:52 schrieb Jani Heikkinen:
> Hi,
>
> We have released Qt 5.12.0 Beta4 today. As earlier you can get it via online 
> installer. Delta to beta3 attached.
>
> Please make sure you will report all findings in Jira. Please make sure all 
> Qt 5.12.0 release blockers are visible in release blocker list 
> (https://bugreports.qt.io/issues/?filter=19961). Target is to get RC out 15th 
> November so all fixes needs to be in latest Tue 13th November; there isn't 
> that much time anymore to fix remaining blockers...
>
> br,
> Jani Heikkinen
> Release Manager
>
>
>
>
> ___
> Development mailing list
> Development@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] [HEADS UP] 5.12 locked down (Re: Merge and Integration status report - 2018.11.08)

[Oswald Buddenhagen]

On Thu, Nov 08, 2018 at 08:29:47AM +, Liang Qi wrote:
> I don't know how to use [Grafana] to show the statistic of qtbase 5.12
> integrations in coin. There are only 3 successful integrations
> yesterday: [...]
> 
because this situation has been persisting for weeks and we've been
essentially just burning energy and motivation with doomed integration
attempts, we decided to lock down 5.12 until the situation is under
control. a somewhat optimistic ETA is maybe a week, depending on the CI
team's progress with deploying infrastructure software updates (it's a
bit more involved than it sounds, so bear with them).

if you have critical changes which justify spending extra effort to get
them in soon, talk to liang.
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

Re: [Development] Qt 5.12.0 Beta4 released

[Massimo Callegari via Development]

 https://bugreports.qt.io/browse/QTBUG-71444
is a blocker for my project.
Il giovedì 8 novembre 2018, 11:52:39 CET, Jani Heikkinen 
 ha scritto:  
 
 Hi,

We have released Qt 5.12.0 Beta4 today. As earlier you can get it via online 
installer. Delta to beta3 attached.

Please make sure you will report all findings in Jira. Please make sure all Qt 
5.12.0 release blockers are visible in release blocker list 
(https://bugreports.qt.io/issues/?filter=19961). Target is to get RC out 15th 
November so all fixes needs to be in latest Tue 13th November; there isn't that 
much time anymore to fix remaining blockers...

br,
Jani Heikkinen
Release Manager

___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
  ___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development

[Development] Qt 5.12.0 Beta4 released

[Jani Heikkinen]

Hi,

We have released Qt 5.12.0 Beta4 today. As earlier you can get it via online 
installer. Delta to beta3 attached.

Please make sure you will report all findings in Jira. Please make sure all Qt 
5.12.0 release blockers are visible in release blocker list 
(https://bugreports.qt.io/issues/?filter=19961). Target is to get RC out 15th 
November so all fixes needs to be in latest Tue 13th November; there isn't that 
much time anymore to fix remaining blockers...

br,
Jani Heikkinen
Release Manager


qt5.git
417d293fa73b34c4004017d2d7aa19c6a292acde Add 'qttools' dependency for WebEngine
9a9f35850828f7448e293a10d1d4210a9f5f59d2 Graduate qtremoteobjects and 
qtwebglplugin
01faa84629cfbbbe4c5bbb457d31bad50dc7883c Update qt3d-runtime.txt targets
3b4ca5d6c0b44e64efd3776327b4f6714d0d8969 Provisioning: Update openssl to 
version 1.0.2p
d65d71731f8b50ee8912134e81418178a0a158a7 CI platform config: Make 32 bit 
msvc2017 config as default
ff2c96f48345a132106f276069ea0d9e2d21e377 Adjust submodule branches
qt3d:
3314694004b825263c9b9f2d69bd85da806ccbbc Fix crash due to racecondition in 
renderer on shutdown
3bc2e44bd387aa2185083fcf9467f37380f3 Don't trigger Q_UNREACHABLE if passed 
invalid render buffer formats
62a30edbd5b61e1b9dd5eca119710c5a54d6e803 Doc: Fix external link error
qtactiveqt:
qtandroidextras:
qtbase:
60197af4850e13409f26551ce812e866602e6926 Android: Fix build.gradle
47869340b97686a4bf852f94edc3bae1e50d7053 Doc: Solve issue with gridlayout image 
file
afba8fcc4914b80be7733a059b26411bdde510eb Doc: Add description for mode argument 
of qmake's $$system()
3fbf8fbc85143e713946ece3036b7303b8268f05 Update to CLDR v34
c9d18d4a9c9d1243a267316e2a702f9ba69de2fd eglfs_kms: initialize m_deviceListener
1b9af84c1bb66770f607e157991375f7cb7ae0fb Don't create an offscreen surface when 
not on the GUI thread
3b8075de3b3c842311c157476a85d2cf9ddff403 Fix deleting of QSharedPointer 
internals in case QPointer loses the race
58d2180dfac2e279b7fae89d467b16d82d80eb7e Add since 5.11 markers to two QFile 
enums
d4e937a6280f34bc1cce8c8cea3806a741312fbc xcb: Don't get initial screen rotation
e02d758c9509de31aafc82d53296f1acdab55151 macOS: Treat explicitly set 
Qt::SubWindows as not needing a NSWindow
d02fed67814a3cb8f28a4f0ec61e075858fce238 macOS: restore hidden popup windows
95476bfcf64aa9cb43775ebfe3410ce9565de4d5 qendian: Fix float conversions
acf5c37046944d6483cfc68b3d877b015292d415 macOS: Add local auto-release pool 
during updating of window flags
d555327a57cb1419fbc19c7dd0b12f6c845598a5 macOS: Explicitly define lower bound 
for supported SDK version
199b67f11c7c5b9ae0aaf60f3e7ea20dafc21ce4 macOS: Log Qt and macOS version 
information at startup
269172037db11d6e62bcef2d5c7491af9244f203 wasm: use maintainTimers instead of 
processEvents for touch callback
d2e0e416dccf3c208d6770e32ff0fb04b543 Fix leaking QTabletEventPrivate 
instance
ae57e271e8d37c05cede83ada594b0f58d388a58 Fix out of bounds memory access when 
setting motif window hint properties
b10ee45546e152e08b2494bd45eb22426e9d2dc9 tst_qeventdispatcher: remove macOS 
from the BLACKLIST
321f11db53422fe797c881cafa36ee44406d803c tst_QLocalSocket::processConnections: 
remove QSKIP
95ba049f8787258ccb28eeda72d1fac71f90e6f6 Remove QSKIP and bring the test back 
to business
8e1c8076282f87a8d19f73feb1bb5baf068de1e1 xcb: fix unresponsive mouse clicks 
after VT switch
88fe7c8cad0bb8e9aee1373c7a7a24d1e4be24ca Windows QPA: Fix 2-finger scroll not 
working with some touchpads
013cf4aeb3e705165614715fcda59c22f58cc5b0 angle: Add additional information to 
qt_attribution.json
e524724f9dc6f64f6f94b842682c751dcd07225f tst_qfilesystemmodel: Do not use 
nested calls of auto test functions
38afa46c47f4401cd5fe8ce6eb93978d5287cfbc macOS: Only detect changes to the SDK 
version within the same developer dir
509d566ec0f257f7f1a723096b57a718d43d5002 Don't block mouse events if the window 
is a Tooltip type
72bedd49bfb02ba7c7abf2a1a4c6cd165ebcd447 [cocoa] Disable offline renderers for 
dual AMD FirePro GPU
ebfad73b4e44fe6db8059200da105b4b87888718 macOS: Fix NSOpenGLContext view 
association check
c0538857358e57c1551f7d10c07a9bb80d848cd7 Windows/QPA: Fix receiving mouse 
clicks after double clicks in QQuickWidget
903666a6027cec25010a99c05824df14ce26e7bf qtriangulator: Remove a bunch of dead 
code
1bb8627f8f1dea546f766a37888fe331381fa333 Extend PDF engine to allow the 
generation of PDFs with huge pages
0cb44e2cfb11033cdb7e3b73a25f1ec394b08d6e Fix stylesheet example for 
QLineEdit:read-only code example
a87f85dbf9bd1ea90936bd9a4609229edb15c264 Linux Accessibility: Fix expandable 
state
1c614d07fbb3ec190b7ed3fc5eb24a200f282c0f tst_QAccessibilityLinux make state 
checking more convenient
07f79a8029674f47b92a04646df6dfa9cedf894f qimagescale: Get rid of the memset call
1a6a78171adaaf2f4bb7f4668533ccc2c06f6db4 qdir: Fix a condition typo
ef02dd14cddf42ff8bfcf70d38098defe47fa739 QMovie: use rvalue more
qtcanvas3d:
qtcharts:
0d02273f948243e799dc00e84134679a8b1ac652 Add changes file for Qt 5.12.0