On Tuesday, 13 November 2018 18:43:03 PST Kevin Kofler wrote:
> Thiago Macieira wrote:
> > But I've just remembered that Designer loads plugins and those are quite
> > clearly tied to the Qt version. The file format is backwards compatible
> > and has remained so for a few years. It is possible tha
Thiago Macieira wrote:
> But I've just remembered that Designer loads plugins and those are quite
> clearly tied to the Qt version. The file format is backwards compatible
> and has remained so for a few years. It is possible that the plugins
> generate the same XML regardless of version, but I thi
On Tuesday, 13 November 2018 15:19:58 PST Lisandro Damián Nicanor Pérez Meyer
wrote:
> Agreed, but this means that if an application is backwards compatible then
> it must be kept like that for all the Qt 6 lifetime. Is that feasible?
Yes. Assistant, Linguist, the D-Bus tools should be.
But I've
El martes, 13 de noviembre de 2018 19:56:29 -03 Thiago Macieira escribió:
> On Tuesday, 13 November 2018 13:43:20 PST Lisandro Damián Nicanor Pérez
> Meyer
> wrote:
> > a) Qt 5 and Qt 6 binaries should be coinstalable both in a developer
> > (libraries + binaries + build tools) and in a user's (onl
On Tuesday, 13 November 2018 13:43:20 PST Lisandro Damián Nicanor Pérez Meyer
wrote:
> a) Qt 5 and Qt 6 binaries should be coinstalable both in a developer
> (libraries + binaries + build tools) and in a user's (only required
> libraries and binaries) perspective. For example: a user should not ne
Hi! I would like to bring this issue with time so we can try to find a nice
solution for this.
Some time before Qt5 was released, in an attempt for Qt4/Qt5 coinstallability,
qtchooser was developed to help ensure e.g. moc, qdbus and rcc could coexist.
Before qtchooser came in a user could not h
On Tue, Nov 13, 2018 at 01:13:28PM +, Harald Kjølberg wrote:
> Hi,
>
>
> Referring to: https://bugreports.qt.io/browse/QTBUG-70891
>
> The suggestion is to remove Windows 7 as a supported development host,
> but keep it as a target. From the numbers I have access to, more than
> 55% of the u
> 29 okt. 2018 kl. 08:17 skrev Lars Knoll :
>
> As you will probably remember, there have been lively discussions around what
> kind of build tool to use for Qt 6 both during Qt Contributor Summits as well
> as on this mailing list.
>
> There has been a strong consent that we should move away
On 02/11/2018 13.39, Oswald Buddenhagen wrote:
> i honestly don't understand what your problem is. the only difference
> between the approaches is that you centralize the meta data, while i
> distribute it. TTA works exactly the same way.
My approach forces packages to be transactional. Either you
On Dienstag, 13. November 2018 09:30:11 CET Ulf Hermann wrote:
Just wait forever on the check in a loop. After 15 minutes the
watchdog kicks in and kills the test. If that happens, you know that
it's a real failure. This works fine for the QML debugger tests.
On 11/13/18 11:30 AM, E
Hi,
So where to develop? At Win-10 spying everything?
Since Win-7 is with paid updates due for 4 more years,
please continue to support it.
Thanks in advance.
Regards,
Robert
On Tue, Nov 13, 2018 at 3:13 PM Harald Kjølberg wrote:
>
>
> Hi,
>
>
> Referring to: https://bugreports.qt.io/browse/QT
Hi,
"From the numbers I have access to, more than 55% of the users are on
Windows 10" - what about the 45%?
Is there any reason why to drop W7 as dev. platform? I use it as my main
developer platform...
Telling the truth I use it at my home for general purpose, too, no plan to
upgrade to W10 in f
Hi, you mean I will not able to use Qt Creator on my Windows 7 machine
after 5.12? Please do not toss Windows 7 out of the window this fast.
Don't know about MSVC2021 yet, but MSVC2019 is the same 32-bit flavored
app that MSVC2017 is and MSVC2019 will run on Windows 7 SP1, i.e. I will
be able
Hi Harald,
On 13/11/2018 14:13, Harald Kjølberg wrote:
Hi,
Referring to: https://bugreports.qt.io/browse/QTBUG-70891
The suggestion is to remove Windows 7 as a supported development host, but keep
it as a target. From the numbers I have access to, more than 55% of the users
are on Windows 1
Hi,
Referring to: https://bugreports.qt.io/browse/QTBUG-70891
The suggestion is to remove Windows 7 as a supported development host, but keep
it as a target. From the numbers I have access to, more than 55% of the users
are on Windows 10. However, I would like to get feedback on this in case
On 11/13/18 11:30 AM, Edward Welbourne wrote:
> On Dienstag, 13. November 2018 09:30:11 CET Ulf Hermann wrote:
>>> Just wait forever on the check in a loop. After 15 minutes the
>>> watchdog kicks in and kills the test. If that happens, you know that
>>> it's a real failure. This works fine for the
On Dienstag, 13. November 2018 09:30:11 CET Ulf Hermann wrote:
>> Just wait forever on the check in a loop. After 15 minutes the
>> watchdog kicks in and kills the test. If that happens, you know that
>> it's a real failure. This works fine for the QML debugger tests.
I encourage you to rewrite th
Oliver Wolff (13 November 2018 09:05)
> I had a look at the problem when I blacklisted it for WinRT and one
> problem was, that QTRY_IMPL used a hard coded step interval of 50 ms,
> which of course does not make sense if you try to have a timeout of 25
> ms.
Thank you for bringing that to my atten
> Since hanging randomly is a common issue in our CI, that would be
> indistinguishable from a random failure.
It rarely hangs for 15 minutes. If that actually happens we usually hear
a lot of other screaming about the CI and then you know that it might be
a false negative. I realize that just w
On Dienstag, 13. November 2018 09:30:11 CET Ulf Hermann wrote:
> > I had a look at the problem when I blacklisted it for WinRT and one
> > problem was, that QTRY_IMPL used a hard coded step interval of 50 ms,
> > which of course does not make sense if you try to have a timeout of 25
> > ms. In addi
> I had a look at the problem when I blacklisted it for WinRT and one
> problem was, that QTRY_IMPL used a hard coded step interval of 50 ms,
> which of course does not make sense if you try to have a timeout of 25
> ms. In addition to that I don't know, how well coin copes with such
> short timeou
On 12/11/2018 23:03, Allan Sandfeld Jensen wrote:
> On Montag, 12. November 2018 22:49:02 CET Thiago Macieira wrote:
>> On Monday, 12 November 2018 12:38:38 PST Liang Qi wrote:
>>> * 10:53am staged 8 changes togehter -
>>> http://coin/coin/integration/qt/qtbase/tasks/1543764990 (failed in 53m -
>>>
22 matches
Mail list logo
