On Sat, 15 Dec 2018 at 01:59, Kevin Kofler wrote:
> >> This is a bug that was already fixed by:
> >> https://gitlab.kitware.com/cmake/cmake/merge_requests/2668
> >
> > Apparently it will make it into 3.14, in 2 months.
> > It's a bummer to have to maintain a work around, or should i add cmake
> >
On Sat, 15 Dec 2018 at 05:19, Jason H wrote:
>
> I request removal of artemis_poo...@aol.com for spam. Email can be forwarded
> to the appropriate party.
> Have others gotten a direct reply?
Yes, i have received 4 phishing attempts from this email.
Chris
FWIW, Denis: I feel your pain and agree that the Qt Company and Qt Project have
a responsibility to make cross compilation with CMake just work out of the box
when you have the necessary kits installed in QtCreator.
There is absolutley no excuse for us not doing this. We as a company should be
Maximilian Hrabowski wrote:
> - the cmake syntax is more difficult to learn and to read and there was
> seen no improvement to the qmake syntax
The advantages of CMake vs. QMake are not in the syntax, but in the
expressiveness. There are lots of things you just cannot do with QMake. It
is barely
There was, for example, https://phabricator.kde.org/D17015 not long time ago.
пт, 14 дек. 2018 г. в 18:36, Thiago Macieira :
>
> On Friday, 14 December 2018 01:19:20 PST Jaroslaw Kobus wrote:
> > So, I may bring it back if it's needed.
>
> Please do. Then announce the deprecation and give people tw
14.12.2018, 16:04, "Kevin Kofler" :
> Also, do not understimate what CMake can do, especially with functions,
> which make it theoretically Turing-complete. (That said, you might actually
> want to restrict or ban the use of recursive (or all) functions in your
> CMakeLists.txt coding style if yo
Unsubscribe me
Sent from my iPhone
> On Dec 14, 2018, at 12:57 AM, Christian Gagneraud wrote:
>
> Hi Kevin,
>
>> On Fri, 14 Dec 2018 at 00:54, Kevin Kofler wrote:
>> Bootstrapping QMake has always been the least pleasant part of the Qt build
>> process.
>
> Yes, i think we all agree on that
> -Original Message-
> [...]
> > > The Qt Company has been looking for "employees" to work on Qbs for
> > > month before dropping it, apparently nobody responded, or something...
> >
> > Then that would pretty much explain why they cannot maintain it in the
> > long run.
>
> You are right,
On 13. Dec 2018, at 13:02, Denis Shienkov
mailto:denis.shien...@gmail.com>> wrote:
Where is CMake advantages?
Actually that is the question i’d like to ask all the time and no one can tell
me.
In June we started to migrate a larger project from qmake which uses a lot of
code generators. Sinc
I request removal of artemis_poo...@aol.com for spam. Email can be forwarded to
the appropriate party.
Have others gotten a direct reply?
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
First use Qt interest mailing list. Since this is a developer list let's throw this out there:
Next why is an **app** **implementing** a lock screen? It would be far better for Qt to integrate with whatever authentication mechanisms provides. For example:
if (QAuthProvider::mechanisms(QAuthPro
On Friday, 14 December 2018 01:19:20 PST Jaroslaw Kobus wrote:
> So, I may bring it back if it's needed.
Please do. Then announce the deprecation and give people two years to update
their build systems to not try to use a tool that disappeared.
Please make it for 5.12.1.
> Could you give an exa
On Friday, 14 December 2018 04:51:58 PST Kevin Kofler wrote:
> > My bet is that it will never happen, you'll still need the power of
> > perl, python or javascript to do the "dirty job", CMake is not
> > expressive enough, by design.
>
> For things like custom code generators, maybe, if you cannot
Hi devs,I hate to write these emails, but Jira and Gerrit don't really work for
me. (and at this point I suspect I definitely have BAD luck)
The question this time is: what's the deal with Qt3D ?Since a year or so,
submitting Qt3D issues to Jira or even contributing on Gerrit is like writing
to
Christian Gagneraud wrote:
> On Fri, 14 Dec 2018 at 00:54, Kevin Kofler wrote:
>> I am looking forward to this bootstrapping hack going away by just using
>> CMake.
>
> So you want to replace a bunch of scripts with another bunch of
> scripts, and magically the maintenance burden will be gone?
A
+1 from me as well.
Paul is interested in many areas and taking responsibility. He also started
helping out maintaining our Gerrit instance.
Cheers,
Frederik
On onsdag 12. desember 2018 11:58:47 CET Simon Hausmann wrote:
> Hi,
>
>
> I would like to nominate Paul for approvership. He started b
On Fri, 14 Dec 2018 at 00:54, Kevin Kofler wrote:
> This is a bug that was already fixed by:
> https://gitlab.kitware.com/cmake/cmake/merge_requests/2668
Apparently it will make it into 3.14, in 2 months.
It's a bummer to have to maintain a work around, or should i add cmake
to my toolkit, so tha
That would be really nice to have a component like that and save lots of time.
Security is not my first priority at the moment but I will spend some time to
implement something useful :)
Thanks anyway
From: Edward Welbourne
Sent: Friday, December 14, 2018 12:4
Akin Gümüskavak (Friday, 14 December 2018 9:47 AM) wrote
>> I'm trying to develop a drawing pattern area as password field in
>> Qml. I've made some research but could not find anything useful.
Mitch Curtis (14 December 2018 09:59) replied:
> What do you mean by "drawing pattern area as password f
> I mean just like mobile phones lock screen. I would like to define a pattern
> as password and use it to login
Oh, right. Then I think a single MouseArea or TapHandler is probably your best
bet. You could use e.g. GridLayout with a Repeater to create a bunch of items
that the input area uses
The answer to the first question is yes. If you want to generate the qhc file
using Qt < 5.12 you need to use qcollectiongenerator, since merging took place
in 5.12 branch, not before.
So, I may bring it back if it's needed.
Could you give an example link to the project which is failing now?
> -Original Message-
> From: Development On Behalf Of
> Akin Gümüskavak
> Sent: Friday, 14 December 2018 9:47 AM
> To: development@qt-project.org
> Subject: [Development] Qml draw pattern as password
>
> Hello,
>
>
>
>
> I'm trying to develop a drawing pattern area as password field i
Hi Kevin,
On Fri, 14 Dec 2018 at 00:54, Kevin Kofler wrote:
> Bootstrapping QMake has always been the least pleasant part of the Qt build
> process.
Yes, i think we all agree on that one.
> I am looking forward to this bootstrapping hack going away by just using
> CMake.
So you want to replace
Hello,
I'm trying to develop a drawing pattern area as password field in Qml. I've
made some research but could not find anything useful.
Now, I am thinking to use MouseArea. I can identify points in this area and I
can get mouse X and Y positions on pressed. But it is getting complicated.
Is
24 matches
Mail list logo