http://doc-snapshot.qt-project.org/5.0/qflag.html says "The QFlag class is
a helper data type for QFlags You should never need to use this class
in your applications."
Sounds like it shouldn't be exposed in the public API then. Thoughts?
Regards,
Sze-Howe
FWIW, +1 - with one modification - reflect at least the minor version in the
install path - so $prefix/libexec/qt5.0, if not $prefix/libexec/qt5.0.0.
I think there is probably a simple rule we could maintain: Keeping the names of
developer visible tools the same is, IHMO, a must. Tools that are
On Oct 18, 2012, at 10:07 AM, Sorvig Morten wrote:
> According to git grep Qt 4 has 47 semi-public exported "qt_platform"
> functions offering platform-spesific functionality. Most platform code is now
> in plugins and can no longer export symbols. We need a plan for dealing with
> these in Qt
Digia has said that the company is willing to support and maintain the module.
It'll be part of the Qt 5 release as well. So it's mainly a problem with the
generated documentation currently.
Cheers,
Lars
On Oct 20, 2012, at 2:31 PM, Sze Howe Koh
mailto:szehowe@gmail.com>> wrote:
(Re-inclu
On Oct 20, 2012, at 5:18 AM, d3fault wrote:
> On Fri, Oct 19, 2012 at 3:37 PM, Knoll Lars wrote:
>> This is just wrong, and I'm getting tired of your ramblings on this mailing
>> list. Just because you send something to the ML and people get tired of
>> answering you doesn't mean your proposa
On sábado, 20 de outubro de 2012 10.28.35, Stephen Kelly wrote:
> On Saturday, October 20, 2012 10:30:36 Alberto Mardegan wrote:
> > On 10/20/2012 02:16 AM, Thiago Macieira wrote:
> > [...]
> >
> > > 3) In addition, we'll create a *new* tool also called qmake that will be
>
> I wonder how FindQt4.c
Wow. I don't usually "rubber-neck" as I drive by car-crashes, but I
must say, this has been one of the more fascinating email chains.
Not because of content; but rather, because in my introverted
"I'm-so-lonely!" world, observing humans-being-human has recently
become fascinating to me.
I had to
(Re-including the mailing list)
The snapshot is the more recent version of the page you linked. But in any
case, I found an old thread (
http://www.mail-archive.com/development@qt-project.org/msg01737.html),
which suggests that there's no active maintainer at the moment.
Regards,
Sze-Howe
On Sa
Hi all,
I'm curious about the status of ActiveQt. The QAxContainer and QAxServer
modules seem to still exist in the code base, but aren't listed in
http://doc-snapshot.qt-project.org/5.0/modules.html. Is this simply an
omission in documentation, or are they being removed?
Regards,
Sze-Howe
_
On Saturday, October 20, 2012 12:12:39 Alberto Mardegan wrote:
> On 10/20/2012 11:28 AM, Stephen Kelly wrote:
> >> And from that time on one doesn't need to remember what qt version or
> >> toolchain one has to use for a project, and just always type "qmake"
> >> from the project base directory.
>
On 10/20/2012 11:28 AM, Stephen Kelly wrote:
>> And from that time on one doesn't need to remember what qt version or
>> toolchain one has to use for a project, and just always type "qmake"
>> from the project base directory.
>
> This is the right goal imo, but the wrong implementation.
I'm not s
On Saturday, October 20, 2012 10:30:36 Alberto Mardegan wrote:
> On 10/20/2012 02:16 AM, Thiago Macieira wrote:
> [...]
>
> > 3) In addition, we'll create a *new* tool also called qmake that will be
I wonder how FindQt4.cmake will react to that. If that module finds Qt 5 it is
supposed to keep l
On sábado, 20 de outubro de 2012 09.53.24, Alberto Mardegan wrote:
> As you mentioned in another message, it would be great if these paths
> were discoverable, either with a qt5-config tool or (better, IMHO) with
> a qt5.pc pkg-config file defining these variables, so that one could do:
>
> $ pkg-c
On 10/20/2012 02:16 AM, Thiago Macieira wrote:
[...]
> 3) In addition, we'll create a *new* tool also called qmake that will be
> installed to $bindir. This tool shall have the following behaviours:
>
> a) under most circumstances, it will simply find another qmake and pass
> through all argume
14 matches
Mail list logo
