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 http://doc.qt.io/qt-5/search-results.htm

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

so the question: how to make it matter? On Thu, Sep 22, 2016 at 4:52 PM, Jason H wrote: > I've never seen it claimed that voting matters 1 iota. > > I guess what we're asking for here is more prioritization transparency? > > > *Sent:* Thursday, September 22, 2016 at 2:27 AM > *From:* "Vlad Stelm

Re: [Interest] Optimizations in debug configuration

On sexta-feira, 23 de setembro de 2016 01:52:28 PDT Konstantin Shegunov wrote: > Hello, > What's the rationale of having -O2 for debug builds on Linux (g++)? As the > compiler moves the assembly around it becomes hell stepping through with > the debugger. Is the flag passed intentionally (and why)?

Re: [Interest] Current QDataStream format documentation?

On sexta-feira, 23 de setembro de 2016 03:01:40 PDT Jason H wrote: > The documentation should be current. Maintaining documentation is part os > selling the toolkit. The maintainer of QDataStream (me) disagrees. I don't like the versioning support in the first place, since it's an all-or-nothing.

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

On sexta-feira, 23 de setembro de 2016 01:06:31 PDT René J. V. Bertin wrote: > Ch'Gans wrote: > >> It's not possible to connect to another user's session bus. > > > > I'm not trying to say that this is what René should do, I'm just > > saying that it is technically possible, for the sake of correc

Re: [Interest] Current QDataStream format documentation?

> On quinta-feira, 22 de setembro de 2016 20:10:32 PDT Jason H wrote: > > > On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote: > > > > So I'm still looking for protocol 17 documentation. I need to provide > > > > this > > > > documentation to an outside implementer. > > > > > > It

Re: [Interest] Optimizations in debug configuration

On Fri, Sep 23, 2016 at 2:19 AM, Giuseppe D'Angelo < giuseppe.dang...@kdab.com> wrote: > > Hope this helps > It does, thanks! I wasn't talking about profiling, but your answer pointed me in the right direction. Apparently I have a sneaky flag somewhere in my build configuration which shouldn't be

[Interest] dynamically populated submenus remaining empty/disabled on OS X

Hi, I'm seeing a weird issue with two of Kate's menu items, on OS X. When the menubar sits at the top of the screen as is the default on OS X, 2 the Tools/Mode menu that selects the document content type contains only disabled submenus. Normally those submenus (Markup, Sources, Science etc) con

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

Il 18/09/2016 12:02, Elvis Stansvik ha scritto: >>> >> It lets you filter Google searches such that only your specified >>> >> version of Qt is shown. >> > >> > >> > Nice, I use Firefox but that's a good thing to share :) >> > I just tried : QObject, QString, QList point to Qt 5.7 first, but for >>

Re: [Interest] Optimizations in debug configuration

Hi, Il 23/09/2016 00:52, Konstantin Shegunov ha scritto: > What's the rationale of having -O2 for debug builds on Linux (g++)? As > the compiler moves the assembly around it becomes hell stepping through > with the debugger. Is the flag passed intentionally (and why)? This kind of builds ("profil

Re: [Interest] Current QDataStream format documentation?

On 22 September 2016 at 23:11, Jason H wrote: > Nevermind. The trick does work. I have no idea what I did wrong. > http://doc.qt.io/qt-5/datastreamformat.html > > "qt5 serialization" is what I had to search for. The 5.x page never came up > in the Google results, only 4.8. I think we need to add

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

Ch'Gans wrote: >> It's not possible to connect to another user's session bus. > I'm not trying to say that this is what René should do, I'm just > saying that it is technically possible, for the sake of correctness. My first attempts to get a privileged service to work involved exporting my la

[Interest] Optimizations in debug configuration

Hello, What's the rationale of having -O2 for debug builds on Linux (g++)? As the compiler moves the assembly around it becomes hell stepping through with the debugger. Is the flag passed intentionally (and why)? Kind regards. ___ Interest mailing list I

Re: [Interest] Current QDataStream format documentation?

2016-09-22 21:12 GMT+02:00 Thiago Macieira : > On quinta-feira, 22 de setembro de 2016 20:10:32 PDT Jason H wrote: >> > On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote: >> > > So I'm still looking for protocol 17 documentation. I need to provide >> > > this >> > > documentation t

Re: [Interest] Current QDataStream format documentation?

On quinta-feira, 22 de setembro de 2016 20:10:32 PDT Jason H wrote: > > On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote: > > > So I'm still looking for protocol 17 documentation. I need to provide > > > this > > > documentation to an outside implementer. > > > > It doesn't exist

Re: [Interest] Current QDataStream format documentation?

On quinta-feira, 22 de setembro de 2016 19:03:29 PDT Giuseppe D'Angelo wrote: > On Thu, Sep 22, 2016 at 7:00 PM, Thiago Macieira > > wrote: > > We don't update the QTextStream format documentation. > > Do you mean QDataStream? > > Anyhow, well, that's the problem. We should do it, at review tim

Re: [Interest] Current QDataStream format documentation?

> On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote: > > So I'm still looking for protocol 17 documentation. I need to provide this > > documentation to an outside implementer. > > It doesn't exist. You'll have to write it. I'm not the one who made the changes, so I don't know w

Re: [Interest] Current QDataStream format documentation?

On Thu, Sep 22, 2016 at 7:00 PM, Thiago Macieira wrote: > We don't update the QTextStream format documentation. Do you mean QDataStream? Anyhow, well, that's the problem. We should do it, at review time (if we're touching streaming operators into QDataStream, update the corresponding doc), and a

Re: [Interest] Current QDataStream format documentation?

On Thu, Sep 22, 2016 at 6:52 PM, Thiago Macieira wrote: > It doesn't exist. You'll have to write it. This is actually pointing out a problem in the review process and in the release process, which we should solve. My 2 c, -- Giuseppe D'Angelo ___ Inte

Re: [Interest] Current QDataStream format documentation?

On quinta-feira, 22 de setembro de 2016 18:56:31 PDT Giuseppe D'Angelo wrote: > On Thu, Sep 22, 2016 at 6:52 PM, Thiago Macieira > > wrote: > > It doesn't exist. You'll have to write it. > > This is actually pointing out a problem in the review process and in > the release process, which we shou

Re: [Interest] Current QDataStream format documentation?

On quinta-feira, 22 de setembro de 2016 17:36:44 PDT Jason H wrote: > So I'm still looking for protocol 17 documentation. I need to provide this > documentation to an outside implementer. It doesn't exist. You'll have to write it. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Ar

Re: [Interest] Current QDataStream format documentation?

> 22.09.2016, 18:11, "Jason H" : > > Nevermind. The trick does work. I have no idea what I did wrong. > > http://doc.qt.io/qt-5/datastreamformat.html > > > > "qt5 serialization" is what I had to search for. The 5.x page never came up > > in the Google results, only 4.8. I think we need to add so

Re: [Interest] Current QDataStream format documentation?

22.09.2016, 18:11, "Jason H" : > Nevermind. The trick does work. I have no idea what I did wrong. > http://doc.qt.io/qt-5/datastreamformat.html > > "qt5 serialization" is what I had to search for. The 5.x page never came up > in the Google results, only 4.8. I think we need to add something to

Re: [Interest] Current QDataStream format documentation?

Alas, still out of date: "The QDataStream allows you to serialize some of the Qt data types. The table below lists the data types that QDataStream can serialize and how they are represented. The format described below is version 12." The version in 5.6/5.7 is 17. Anyone have more recent docume

Re: [Interest] Current QDataStream format documentation?

Nevermind. The trick does work. I have no idea what I did wrong. http://doc.qt.io/qt-5/datastreamformat.html "qt5 serialization" is what I had to search for. The 5.x page never came up in the Google results, only 4.8. I think we need to add something to the Qt.io site that allows you to select

Re: [Interest] Anyone at CppCon?

On Tue, Sep 20, 2016 at 12:35 PM, Giuseppe D'Angelo < giuseppe.dang...@kdab.com> wrote: > Howdy, > > I'm at CppCon 2016 right now. Was wondering if some other fellow Qt > user/developer was around. Let's raise our hands :-) > > Cheers, > -- > Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior

[Interest] Current QDataStream format documentation?

There used to be a page on QDataStream serialization: http://doc.qt.io/qt-4.8/datastreamformat.html The normal trick does not work: http://doc.qt.io/qt-5/datastreamformat.html -> 404. Where can I find it? There were two additional protocol version since 4.8. ___

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

I've never seen it claimed that voting matters 1 iota.   I guess what we're asking for here is more prioritization transparency?     Sent: Thursday, September 22, 2016 at 2:27 AM From: "Vlad Stelmahovsky" To: "Jason H" Cc: interest Subject: Re: [Interest] What don't you like about Qt?

Re: [Interest] console on OSX

On Thu, Sep 22, 2016 at 12:27 PM, René J.V. Bertin wrote: > > That's fine if you're running in a terminal emulator which already > connects the keyboard to stdin, and stdout to the display... > Right, I misunderstood, sorry. ___ Interest mailing list In

Re: [Interest] console on OSX

On Thursday September 22 2016 12:03:21 Konstantin Shegunov wrote: > QTextStream isn't good for that? > > QTextStream in(stdin), out(stdout); That's fine if you're running in a terminal emulator which already connects the keyboard to stdin, and stdout to the display... __

Re: [Interest] console on OSX

On Thu, Sep 22, 2016 at 11:09 AM, René J. V. Bertin wrote: > but just need to be able to read from stdin and write to > stdout/stderr? > QTextStream isn't good for that? QTextStream in(stdin), out(stdout); int readFromConsole; in >> readFromConsole; out << readFromConsole; ___

Re: [Interest] console on OSX

Thiago Macieira wrote: PS: is there no (free) 3rd party QtConsole class out there, one that implements a more-or-less minimal console for applications that do not use *curses, readline, etc. but just need to be able to read from stdin and write to stdout/stderr? R. ___

Re: [Interest] console on OSX

Thiago Macieira wrote: > For macOS, there may be something equivalent in the Info.plist file for your > bundle. Please consult Apple documentation. No, not that I know of. The automatic way of launching a console application via Terminal is to build is as a traditional (POSIX-style) executable