Am 19.09.16 um 18:52 schrieb Robert Iakobashvili:
> On Mon, Sep 19, 2016 at 5:25 PM, Jason H wrote:
>> There is a 9-month old github; https://github.com/msorvig/qt-and-swift for
>> integrating the two.
>>
>> Are there any plans for formal Qt support of Swift? Obj-C is painful.
>
> +2
As far as
Apologies, if this mail already came up. I had trouble posting to this
group and hence posting it again.
Hi all,
Recently started working with Qt3d for our in-house geometry file viewer.
I'm relatively new to OpenGL. So, please bear with me if my question sounds
silly.
I'm going through the examp
On segunda-feira, 19 de setembro de 2016 13:51:00 PDT Thiago Macieira wrote:
> On segunda-feira, 19 de setembro de 2016 21:56:12 PDT Alexander Carôt wrote:
> > Hi all,
> >
> > in my pro file I added CONFIG += console in order to have console output.
> >
> > This works fine on Windows but on OSX t
On segunda-feira, 19 de setembro de 2016 21:56:12 PDT Alexander Carôt wrote:
> Hi all,
>
> in my pro file I added CONFIG += console in order to have console output.
>
> This works fine on Windows but on OSX the console does not show up.
>
> Is there anything I need to add ?
You need to launch T
On segunda-feira, 19 de setembro de 2016 18:35:43 PDT Etienne Sandré-
Chardonnal wrote:
> Yes, but for instance you can't move-pass an object between signals and
> slots across a queued connection, unless I'm wrong. You have to make your
> object implicitely shared. This causes lots of copies when
2. There are still bugs from 5.2 that need fixing.
3. QmlListProperty has a LOT of requests against it. https://bugreports.qt.io/browse/QTBUG-34015?jql=text%20~%20%22QQmlListProperty%22
PS> Like https://qpm.io?
Sent: Monday, September 19, 2016 at 4:03 PM
From: "Jérôme Godbout"
To: "interest@q
On 19/09/2016 17:35, Etienne Sandré-Chardonnal wrote:
Yes, but for instance you can't move-pass an object between signals and
slots across a queued connection, unless I'm wrong. You have to make
your object implicitely shared. This causes lots of copies when passing
a std::vector, for instance.
For myself I would love to see those changes (mostly to Qml, the C++ part
is fairly striaght forward and we mostly no more used QWidgets):
1. Ability to extend or declare basic type into Qml (not only QObject),
QQuaternion QMatrix4x4 functions are too limited and it's painful to have a
s
Hi all,
in my pro file I added CONFIG += console in order to have console output.
This works fine on Windows but on OSX the console does not show up.
Is there anything I need to add ?
Thanks in advance,
best
Alex
--
http://www.carot.de
Email : alexan...@carot.de
Tel.: +49 (0)177 5719797
___
19.09.2016, 21:54, "André Pönitz" :
> On Sat, Sep 17, 2016 at 09:20:43PM +0100, Sérgio Martins wrote:
>> Hi,
>>
>> It's not unusual for us developers and contributors to lose
>> perspective of what's important.
>> After many years spent on very particular implementation details, it
>> become
On Sat, Sep 17, 2016 at 09:20:43PM +0100, Sérgio Martins wrote:
> Hi,
>
>
> It's not unusual for us developers and contributors to lose
> perspective of what's important.
> After many years spent on very particular implementation details, it
> becomes difficult to see outside of the box.
>
> And
On Mon, Sep 19, 2016 at 5:25 PM, Jason H wrote:
> There is a 9-month old github; https://github.com/msorvig/qt-and-swift for
> integrating the two.
>
> Are there any plans for formal Qt support of Swift? Obj-C is painful.
+2
Kind regards,
Robert
___
I
Yes, but for instance you can't move-pass an object between signals and
slots across a queued connection, unless I'm wrong. You have to make your
object implicitely shared. This causes lots of copies when passing a
std::vector, for instance.
2016-09-19 18:10 GMT+02:00 Konstantin Tokarev :
>
>
> 1
19.09.2016, 19:09, "Thiago Macieira" :
> On segunda-feira, 19 de setembro de 2016 10:40:08 PDT Etienne Sandré-
> Chardonnal wrote:
>> - C++ style is a little bit outdated (no move semantics fir instance)
>
> Move semantics support have been in Qt since 5.0 or so.
4.8
http://doc.qt.io/qt-4.8
On segunda-feira, 19 de setembro de 2016 10:40:08 PDT Etienne Sandré-
Chardonnal wrote:
>- C++ style is a little bit outdated (no move semantics fir instance)
Move semantics support have been in Qt since 5.0 or so.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - In
I've heard that a lot of Cordova apps are breaking on iOS 10 because of changes
to Webkit. I figure Qt is in a similar situation when using Webkit. Cordova's
issue tracker is full of people reporting issues, but they keep getting closed
as 'invalid' because it seems that application code tweaks
There is a 9-month old github; https://github.com/msorvig/qt-and-swift for
inegrating the two.
Are there any plans for formal Qt support of Swift? Obj-C is painful.
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/l
1. Qt progresses at a glacial pace, and often neglects the more urgent/parity
issues.
- a. As more organizations adopt agile, this becomes all that more apparent.
I've got to wait for a year for a code change to hit a release? Sorry, that's
just too long.
- b. Basic stuff like controlling the LE
On 19/09/2016 9:11 AM, Konstantin Tokarev wrote:
19.09.2016, 16:08, "Henry Skoglund" :
Ok here's my number #1 complaint:
the MaintenanceTool app, when you start it, why is the default selected
choice to remove Qt??? It should be to update Qt of course.
(Such a design could get you fired if y
19.09.2016, 16:08, "Henry Skoglund" :
> Ok here's my number #1 complaint:
>
> the MaintenanceTool app, when you start it, why is the default selected
> choice to remove Qt??? It should be to update Qt of course.
>
> (Such a design could get you fired if you worked for say, Microsoft. :=)
I'd rat
Ok here's my number #1 complaint:
the MaintenanceTool app, when you start it, why is the default selected
choice to remove Qt??? It should be to update Qt of course.
(Such a design could get you fired if you worked for say, Microsoft. :=)
Rgrds Henry
On 2016-09-19 05:20, Bo Thorsen wrote:
* Designer plugin development/deployment sucks (should be in a
scripting language or json, and should be possible to do per project)
I don't know if you count Python as a scripting language or not, but
just in case, you can do this with PyQt.
http://p
On Sat, 17 Sep 2016 21:20:43 +0100, Sérgio Martins wrote:
> Please state your top ones, even if it was already stated by someone
> else, so we have an idea about which ones matter more.
a) C++ ( far beyond everything else )
The 2 language approach is a pain. In our application we have thousands
On 19 September 2016 at 17:20, Michael Sué wrote:
> Hi,
>
> - nothing new for widgets.
> - not yet full support for VS 2015, missing "Addin" that is, for more than a
> year now.
> - missing C++ support for mobile platforms.
> - unusable Docs for Qt3D.
>
> Best, Michael.
Hi Michael,
Regarding VS
On 19 September 2016 at 01:14, Nate Rogers via Interest
wrote:
>
> I'm a Linux user but a guy at work was trying out Qt on windows for a project
> he was working on. He tried the new installer and it didn't come
> preconfigured with a compiler like it used to. I didn't have time to trouble
> sh
Inside Plane.qml is currently not possible.
There is one patch under review that adds the MapItemGroup item,
meaning a way to group map items as you ask.
That's however 5.9 material :)
best,
Paolo
On Wed, 14 Sep 2016 09:52:16 +0530
Kishore J wrote:
> And I should mention that the circle should
Hi,
- nothing new for widgets.
- not yet full support for VS 2015, missing "Addin" that is, for more than a
year now.
- missing C++ support for mobile platforms.
- unusable Docs for Qt3D.
Best, Michael.
___
Interest mailing list
Interest@qt-project.or
Okay, I'll bite:
* Poor standard of some modules - Qt Multimedia and Qt Components especially
* Too much focus on features instead of fixing bugs
* Designer plugin development/deployment sucks (should be in a scripting
language or json, and should be possible to do per project)
* Current gerrit
1) I don't like the distribution being so monolithic.
I'd rather see the packages being shipped individually and having explicit
version dependencies, like QML modules do and like qpm.io is doing.
Maybe this kind of approach will be easier/possible with the new config
system?
2) I don't like qml
Hi,
I have a some missing things for nearly all topics Qt covers:
1. moc is lacking some sort of plugin mechanism. If there where, developers
could extend the autocreation of QObjects, with their own ideas.
2. The build system, qmake. It feels very unusable and you have to use a lot
of hidden
Qt Commercial user here.
I do not like:
- Long time to get bugs fixed
- QtQuick requires switching to QML and is not usable directly in C++
- Widgets development got less attention due to QtQuick development.
HiDPI support was a good idea but it introduced many bugs
- C++ style is
31 matches
Mail list logo
