On Tuesday, 18 December 2018 14:14:57 PST Sérgio Martins wrote:
> Can't pronounce about the TQC decision, but the qt-project decision is
> easy: We won't choose a build system with unclear future, with vague
> declarations of intent by 1 maintainer.
The question here was only about Qt Creator's
On Tue, Dec 18, 2018 at 9:43 PM Richard Weickelt wrote:
>
> On 18.12.2018 21:20, Thiago Macieira wrote:
> > On Tuesday, 18 December 2018 11:44:38 PST Denis Shienkov wrote:
> >> If Qt maintainers says that they will not remove the QtCreator && QBS
> >> integration in future (I'm about QBS project
On 18.12.2018 21:20, Thiago Macieira wrote:
> On Tuesday, 18 December 2018 11:44:38 PST Denis Shienkov wrote:
>> If Qt maintainers says that they will not remove the QtCreator && QBS
>> integration in future (I'm about QBS project manager plugin), then I
>> will not worry (don't care) about CMake.
On Tue, Dec 18, 2018 at 12:20:37PM -0800, Thiago Macieira wrote:
> On Tuesday, 18 December 2018 11:44:38 PST Denis Shienkov wrote:
> > If Qt maintainers says that they will not remove the QtCreator && QBS
> > integration in future (I'm about QBS project manager plugin), then I
> > will not worry
> On Sunday, 16 December 2018 20:12:47 PST Richard Weickelt wrote:
>> ... and if you cross-compile, you definetly don't want to your build system
>> to stick its nose into your system librararies on any platform.
>
> No, you really DO. The issue is what "system" is: it's the sysroot for your
>
Hi,
Thank you for reply. I uploaded image here: https://ibb.co/T8ZSPV6
I found, that workaround is to set: background.width: width
Tom
út 18. 12. 2018 v 18:29 odesílatel Vlad Stelmahovsky <
vladstelmahov...@gmail.com> napsal:
> I can confirm the issue
>
> partial workaround is to assign width
On Tuesday, 18 December 2018 11:44:38 PST Denis Shienkov wrote:
> If Qt maintainers says that they will not remove the QtCreator && QBS
> integration in future (I'm about QBS project manager plugin), then I
> will not worry (don't care) about CMake. I will use QBS in any case.
So long as someone
> preferably one that doesn't involve Qt specific stuff
A main point is that we discuss about using the CMake as an 'advanced'
buld system in context of Qt.
> Please show a concrete example
I already provided that example - it is cross-compilation. You can try
to cross-compile a simple
On Tue, Dec 18, 2018 at 11:49:22AM +, Eike Ziller wrote:
>
>
> > On Dec 18, 2018, at 11:25, Konstantin Shegunov
> > wrote:
> >
> > On Tue, Dec 18, 2018 at 9:39 AM Martin Smith
> > wrote: I'll argue with you about it being a p1. If the problem is
> > confined to the all-members list, it's
On Tuesday, 18 December 2018 10:38:09 PST Matthew Woehlke wrote:
> > I work in the Anaconda Distribution as a software packager and spend
> > a significant amount of my working day battling cmake. As I say it's
> > "ok" for developers but not for packagers.
>
> AFAIK, that experience is
On Dec 18, 2018 12:33 PM, "Matthew Woehlke"
wrote:
On 15/12/2018 15.49, Ray Donnelly wrote:
> Do you know for example that cmake will find dlls in C:\Windows\System32,
Uh... yeah? I think most people *expect* that...
Would you also rather CMake didn't look in /usr/lib[64] on Linux
systems?
On 16/12/2018 12.00, Denis Shienkov wrote:
> As we all can see, the CMake loses even QBS. We need to spent a tens of
> hours/days to find out the solution, using CMake's , but with QBS same
> issue solves for 30 mins or work immediatelly. Its very funny.
Really? Because *I* don't see that.
This
On 16/12/2018 08.21, Ray Donnelly wrote:
> In particular ide generators cannot express complex build
> dependencies very well and any use of scripts will tend not to work unless
> you hardcore them for each one.
Scripts can be problematic if they need to run stuff that is part of the
build,
On 15/12/2018 15.49, Ray Donnelly wrote:
> Do you know for example that cmake will find dlls in C:\Windows\System32,
Uh... yeah? I think most people *expect* that...
Would you also rather CMake didn't look in /usr/lib[64] on Linux
systems? *Why*?
> find_package is still inscrutable, and it's
I can confirm the issue
partial workaround is to assign width to undefined
br,
Vlad
On 12/18/18 3:02 PM, Tomas Konir wrote:
Hi,
I'm using this qml code:
importQtQuick2.12
importQtQuick.Controls2.4
importQtQuick.Window2.12
Window{
visible:true
title:qsTr("HelloWorld")
TextField{
> -Original Message-
> From: Development On Behalf Of
> Tomas Konir
> Sent: Tuesday, 18 December 2018 3:03 PM
> To: development@qt-project.org
> Subject: [Development] qml TextField in material design has too short
> bottom line
>
> Hi,
>
> I'm using this qml code:
>
> import QtQuick
Hi,
I'm using this qml code:
import QtQuick 2.12
import QtQuick.Controls 2.4
import QtQuick.Window 2.12
Window {
visible: true
title: qsTr("Hello World")
TextField {
anchors.fill: parent
}
}
with this result:
[image: textfield.png]
You can see too short
Hi
We’ll perform some firewall switch overs tomorrow morning. While at it, we’ll
move some infra services from one address space to an other enabling us to
create better rules for traffic.
We’ll probably perform a shutdown of the CI at 9 o’clock EET, and we’ll
probably be done with it in an
> On Dec 18, 2018, at 11:25, Konstantin Shegunov wrote:
>
> On Tue, Dec 18, 2018 at 9:39 AM Martin Smith wrote:
> I'll argue with you about it being a p1. If the problem is confined to the
> all-members list, it's not a p1 problem because the information is still
> there via the inherits
On Tue, Dec 18, 2018 at 9:39 AM Martin Smith wrote:
> I'll argue with you about it being a p1. If the problem is confined to the
> all-members list, it's not a p1 problem because the information is still
> there via the inherits links, which are more useful for seeing what is
> inherited anyway.
Hi again,
But it sounds like you're asking for a better search mechanism.
Not really. Sometimes you need to read a bit to see what is there and
what can be done. But if half of the members is inherited, it's hard to
get an overview.
André
From:
On Tuesday, December 18, 2018 9:23:20 AM CET Martin Smith wrote:
> There are no technical limitations, and it will be kept. I expect
> the fix will be fairly simple.
>
> But it sounds like you're asking for a better search mechanism.
For me, that page is also very useful. Sometimes I do not know
There are no technical limitations, and it will be kept. I expect the fix will
be fairly simple.
But it sounds like you're asking for a better search mechanism.
From: André Hartmann
Sent: Tuesday, December 18, 2018 9:19:07 AM
To: Martin Smith;
Hi Martin,
the all-members list is very useful to get an overview about a class.
You're searching for a function to perform a specific task, that you
assume to be in a class. Searching through all inherited classes is a
tedious task.
If there are no technical limitations, I'm for keeping
24 matches
Mail list logo
