Re: [Interest] Current QDataStream format documentation?

On sexta-feira, 23 de setembro de 2016 17:41:30 PDT Jason H wrote: > > > commits to find out what changed? I wouldn't even know where to start. > > > > The expectation is that you read QDataStream with QDataStream. You don't > > need to know what it writes, only that it can read what it writes. >

Re: [Interest] New iTunes Connect Errors - NSPhotoLibraryUsageDescription ?

Never mind. NSPhotoLibraryUsageDescription is legitimate. Sorry. I let user browse the photo library to select a logo for their PDF reports. They must be inspecting deeper than have done in the past. -Ed On Sep 23, 2016, at 3:42 PM, Edward Sutton

Re: [Interest] Optimizations in debug configuration

On Fri, Sep 23, 2016 at 5:31 AM, Thiago Macieira wrote: > > The flag is not passed to the build. > > Debug builds use -O0 on Linux. > I'm building a module and what I observe is getting -g -O2 for CONFIG+=debug. One thing I was able to infer was that setting

Re: [Interest] Qt mouse poll rate too slow

Thanks, this is the issue. At least I'm not the only one! Josh Hi,I think mouse events are subject to compression, so you might be getting only part of the real number of "mouse moves" if Qt decides it can't keep up with the speed.For example this bugreport[1] looks relevant. [1]: 

Re: [Interest] Optimizations in debug configuration

On Sat, Sep 24, 2016 at 1:35 AM, Allan Sandfeld Jensen wrote: > > Maybe it is following Qt's configuration instead of the one you request > locally. Yes, that'd be my guess too. What I imagine is happening is that I have -O2 coming from the configure flags Qt was built with

Re: [Interest] Current QDataStream format documentation?

On sábado, 24 de setembro de 2016 00:47:16 PDT Reinhardt Behm wrote: > > Which is great until it's writing to another device that does not > > implement > > Qt, because it's an Arduino or similar. I don't think it's an unusual > > scenario that you're using QDataStream to exchange data to a device

[Interest] Qt mouse poll rate too slow

Hello all, I'm running into a problem where the mouse (and touchscreen) poll rate is too slow for my application. At first I thought it was the device (mouse and/or touchscreen), but after trying in different apps, I discovered it is Qt. I am simply subclassing a QLabel and adding points to a

Re: [Interest] Optimizations in debug configuration

On Sat, Sep 24, 2016 at 3:23 AM, Thiago Macieira wrote: > > run qmake with -d -d switches and look for where that "-g -O2" is coming > from. The best I can tell it comes from this line: QMAKE_CXXFLAGS = -g -O2 -fdebug-prefix-map=/build/

Re: [Interest] Current QDataStream format documentation?

On sexta-feira, 23 de setembro de 2016 19:05:28 PDT Giuseppe D'Angelo wrote: > Il 23/09/2016 17:14, Thiago Macieira ha scritto: > > The expectation is that you read QDataStream with QDataStream. You don't > > need to know what it writes, only that it can read what it writes. > > Where has this

Re: [Interest] Optimizations in debug configuration

On sábado, 24 de setembro de 2016 00:37:54 PDT Konstantin Shegunov wrote: > I'm building a module and what I observe is getting -g -O2 for > CONFIG+=debug. One thing I was able to infer was that > setting QMAKE_CXXFLAGS to nothing seems to solve it for me. I wouldn't even > dream of speculating

Re: [Interest] Optimizations in debug configuration

On Sat, Sep 24, 2016 at 3:50 AM, Konstantin Shegunov wrote: > On Sat, Sep 24, 2016 at 3:23 AM, Thiago Macieira < > thiago.macie...@intel.com> wrote: >> >> run qmake with -d -d switches and look for where that "-g -O2" is coming >> from. > > > The best I can tell it comes

Re: [Interest] Qt mouse poll rate too slow

Hi, I think mouse events are subject to compression, so you might be getting only part of the real number of "mouse moves" if Qt decides it can't keep up with the speed. For example this bugreport[1] looks relevant. [1]: https://bugreports.qt.io/browse/QTBUG-44964 I hope that helps. Kind

Re: [Interest] Optimizations in debug configuration

On Friday 23 September 2016, Konstantin Shegunov wrote: > On Fri, Sep 23, 2016 at 5:31 AM, Thiago Macieira > > > wrote: > > The flag is not passed to the build. > > > > Debug builds use -O0 on Linux. > > I'm building a module and what I observe is getting -g -O2 for

Re: [Interest] Current QDataStream format documentation?

On sábado, 24 de setembro de 2016 12:50:10 PDT Ch'Gans wrote: > If the other side of the pipe is arduino, maybe try to use JSON (very > easy to use on Qt side), and i'm sure arduino as some library for > this. If JSON is an option, you should use CBOR. -- Thiago Macieira - thiago.macieira (AT)

Re: [Interest] Qt, running as root (sudo/setuid), DBus and OS X

Thiago Macieira wrote: >> My first attempts to get a privileged service to work involved exporting my >> launchd session bus socket to root, via launchctl. That worked; I think >> that's sufficient proof that root at least can connect to a lesser user's >> session bus, on OS X. > > Probably

Re: [Interest] Dealing with Qt 4.x docs in Google searches (Was: "What don't you like about Qt?")

Using https://duckduckgo.com as my search engine helps a lot along with their bangs . The !qt bang normally opens the search in the Qt 5 docs, for example searching for `!qt QString ` opens

[Interest] .remove() feature?

Currently working at a site which is using 5.4 commercial under Ubuntu 14.04 to develop an embedded system. Spent days tracking down a bug in the current project code base. There was an ugly for() loop which was processing a QHash (which really should have been a queue). They were calling

Re: [Interest] What you don't like about Qt

Tried replying to this earlier, but didn't see the content come up so will toss in my 0.0003 cents on this thread. >>- C++ is difficult, Qt lacks quality bindings for mainstream languages - moc (on build systems that don't automate this step) - FUD around licensing Well, Digia has itself to

Re: [Interest] What you don't like about Qt

> -Original Message- > From: Interest [mailto:interest-bounces+tuukka.turunen=qt.io@qt- > project.org] On Behalf Of Roland Hughes > Sent: perjantaina 23. syyskuuta 2016 13.50 > To: interest@qt-project.org > Subject: Re: [Interest] What you don't like about Qt > > Tried replying to this

Re: [Interest] .remove() feature?

> It was a C++ for (int x=0;...) loop, but we are compiling for C++ 11 Hm, then my guess would be that they were working on a QHash/container that was shared and the first remove() performed a detach. Thus the loop worked on a copy. Best Lorenz ___

Re: [Interest] What you don't like about Qt

On 09/23/2016 06:18 AM, Konstantin Tokarev wrote: 23.09.2016, 13:50, "Roland Hughes" : [snip] What I don't like right now about Qt is the 3-legged arthritic dog running in deep snow called QML. It was a bastardized concept when first conceived and it hasn't gotten

Re: [Interest] .remove() feature?

It was a C++ for (int x=0;...) loop, but we are compiling for C++ 11 On 09/23/2016 07:44 AM, Lorenz Haas wrote: Hi, Has anybody else seen this behavior in 5.x? Is removeAt() really queueing a low priority event so the removeAt() doesn't actually happen until the event queue is processed

Re: [Interest] .remove() feature?

Hi, > Has anybody > else seen this behavior in 5.x? Is removeAt() really queueing a low priority > event so the removeAt() doesn't actually happen until the event queue is > processed completely? my QHash only has a remove() function. Also, it removes the item right away, no events involved:

Re: [Interest] .remove() feature?

Lorenz, Good call. I went back through the code. Was actually a QList<> not a QHash, but . . . your mention of shared was the light which shined on the monster. The pointer held in the QList was a pointer to an object declared with CANBUSSHARED_EXPORT. Thank you very much! I hate mystery

Re: [Interest] Current QDataStream format documentation?

> Sent: Friday, September 23, 2016 at 11:14 AM > From: "Thiago Macieira" > To: interest@qt-project.org > Subject: Re: [Interest] Current QDataStream format documentation? > > On sexta-feira, 23 de setembro de 2016 17:05:26 PDT Jason H wrote: > > > Sent: Thursday,

Re: [Interest] What you don't like about Qt

> Not an isolated case. Client after client tells the same story. The > licensing team at Digia must be paid on commission because _every_ use > requires a license when you first contact them. FWIW, My dealings with the licensing people have been good. > What I don't like right now about Qt

Re: [Interest] What you don't like about Qt

On 09/23/2016 10:13 AM, Jason H wrote: What I don't like right now about Qt is the 3-legged arthritic dog running in deep snow called QML. It was a bastardized concept when first conceived and it hasn't gotten any better. Nokia started that concept which explains why they are non-existent in

Re: [Interest] Current QDataStream format documentation?

On sexta-feira, 23 de setembro de 2016 17:05:26 PDT Jason H wrote: > > Sent: Thursday, September 22, 2016 at 10:12 PM > > From: "Thiago Macieira" > > To: interest@qt-project.org > > Subject: Re: [Interest] Current QDataStream format documentation? > > > > On

Re: [Interest] .remove() feature?

On sexta-feira, 23 de setembro de 2016 05:59:28 PDT Roland Hughes wrote: > Currently working at a site which is using 5.4 commercial under Ubuntu > 14.04 to develop an embedded system. Spent days tracking down a bug in > the current project code base. There was an ugly for() loop which was >

Re: [Interest] Current QDataStream format documentation?

> Sent: Thursday, September 22, 2016 at 10:12 PM > From: "Thiago Macieira" > To: interest@qt-project.org > Subject: Re: [Interest] Current QDataStream format documentation? > > On sexta-feira, 23 de setembro de 2016 03:01:40 PDT Jason H wrote: > > The documentation

Re: [Interest] What you don't like about Qt

> Digia From the 1st of May it’s The Qt Company now :) > because of this attempt to squeeze licensing and royalties out of the general > public > I highly suspect the LGPL3 move was done to help squeeze So, in your opinion it is totally fair to create “closed” products (TiVoization) using

Re: [Interest] Current QDataStream format documentation?

On Fri, Sep 23, 2016 at 11:47 AM, Reinhardt Behm wrote: > Or the have two devices are both based on Qt, but different versions. Isn't this precisely the situation that QDataStream::setVersion() is for? ___ Interest mailing list

Re: [Interest] Current QDataStream format documentation?

23.09.2016, 18:41, "Jason H" : >>  Sent: Friday, September 23, 2016 at 11:14 AM >>  From: "Thiago Macieira" >>  To: interest@qt-project.org >>  Subject: Re: [Interest] Current QDataStream format documentation? >> >>  On sexta-feira, 23 de setembro de

Re: [Interest] Current QDataStream format documentation?

On Friday 23 September 2016 17:41:30 Jason H wrote: > > Sent: Friday, September 23, 2016 at 11:14 AM > > From: "Thiago Macieira" > > To: interest@qt-project.org > > Subject: Re: [Interest] Current QDataStream format documentation? > > > > On sexta-feira, 23 de setembro

[Interest] [qt3d] Batching optimization

Hi, Does qt3d backend capable to batch geometries to reduce the number of draw calls? In our case this optimization should improve performances a lot, because we generate dynamically geometries that doesn't change often and are created in world coordinates (no transformations applied). --

Re: [Interest] Current QDataStream format documentation?

Il 23/09/2016 17:14, Thiago Macieira ha scritto: > The expectation is that you read QDataStream with QDataStream. You don't need > to know what it writes, only that it can read what it writes. Where has this expectation *ever* been stated? The very fact that we document the wire format is so

Re: [Interest] What you don't like about Qt

23.09.2016, 22:17, "Jason H" : > > Even the old Qt UI files were somewhat declarative, with signal/slot mappings > included in the UI file. This sounds like you are not sure what word "declarative" means. Of course, UI file is 100% declarative, irrespectively from if

Re: [Interest] What you don't like about Qt

On Fri, Sep 23, 2016 at 05:13:44PM +0200, Jason H wrote: > > > Not an isolated case. Client after client tells the same story. The > > licensing > > team at Digia must be paid on commission because _every_ use requires a > > license when you first contact them. > > FWIW, My dealings with the

Re: [Interest] What you don't like about Qt

> > Actually, the entire industry is moving to declarative. > > Declarative with mandatory bits of imperative Javascript? Well with blanket statement being admittedly blanket in nature and subject to all the caveats therein, yes. I realize that many of you are embedded engineers, and will