Hello everyone,
Just want to let you know that we released the first update for alpha 4.
You can find the full announce here:
https://groups.google.com/group/android-qt/browse_thread/thread/8f005b555fc16a59
Cheers,
BogDan.
___
Development mailing
I assume this is related to changes in native events filtering.
I'd also treat this as a regression since 4.x, until the way to fix an
existing code is clearly documented somewhere.
Konstantin
2012/9/15 Joseph Crowell :
> I got the old Qt4 QtSingleApplication addon compiling under Qt5 by
> updat
Check what the _POSIX_C_SOURCE is defined to.
>From qfiledialog.cpp
#if defined(Q_OS_SOLARIS) && (_POSIX_C_SOURCE - 0 < 199506L)
tmpPw = getpwnam_r(userName.toLocal8Bit().constData(), &pw,
buf, bufSize);
#else
err = getpwnam_r(userName.toLocal8Bit().constData(), &pw, buf,
bufSize, &
Hi,
I'm developing a qt-based implementation of an OMG specification with
defines a number of
classes in different (nested) namespaces. I'd be nice to have the
implementation as close as possible
to the spec. For that purpose, headers would be included like:
#include
Module's .pro just defines
As a Qt Widget user (and contributor) I consider this as really good news
Qt Widgets. :) I might just bring cake to my work office when this is a
reality. Though it is (hopefully) just a formality, I am a bit impatient on
getting some maintainers to second (for all of the above) ...
On Wed, Sep 19
On Wed, Sep 19, 2012 at 6:32 AM, Andras Mantia wrote:
>
> As adding a new non-virtual function is binary compatible, there should be
> no problem to add a QSqlQuery::value(const QString&) method in 5.1.
>
Ah, cool. I wasn't sure about that. I shall then send a patch for 5.1
branch when it's ready
On quarta-feira, 19 de setembro de 2012 14.39.06, Marc Mutz wrote:
> Hi Lars,
>
> On Wednesday September 19 2012, Knoll Lars wrote:
> > For the rest of Qt Widgets Marc Mutz has volunteered. I'm really happy to
> > see him step up to this and support the nomination. But as the area is
> > rather lar
Exactly. Just like with KDE, those projects are probably better served by
maintaining their own platform plugin rather than depend on upstream changes
that might block their releases. I would of course welcome anyone to step up
and maintain those styles as an addon, but I would prefer that we fo
On Wednesday September 19 2012, Gladhorn Frederik wrote:
[...]
> Since we don't see a way to fix the modularized build of the docs without
> big issues (predictive links seem hard to get right and we couldn't show
> warnings about them easily), we propose to actually make use of a mixed
> approach
Hi,
while we all love our documentation we also need to work on polishing it some
more ;)
Today there was a discussion in Oslo about the "how to link between modules"
problems we're facing with qdoc.
I'll try to illustrate the problem and show the solution we would like to
propose.
We have two
I guess OpenCDE project could pick-up these [abandoned] styles and
maintain them on their own, if needed.
Another good solution I see is to bundle these styles as Qt Addons.
regards,
Konstantin
2012/9/19 Konstantin Tokarev :
> There's OpenCDE project, and original CDE was open sourced not so lon
19.09.2012, 15:16, "Bache-Wiig Jens" :
> As we are cleaning up some QStyle related things for Qt5, we are planning on
> removing the now ancient motif and cde styles from qtbase. These were
> designed for platforms and desktops that are no longer supported in Qt5 and
> there is not much value i
Hi Lars,
On Wednesday September 19 2012, Knoll Lars wrote:
> For the rest of Qt Widgets Marc Mutz has volunteered. I'm really happy to
> see him step up to this and support the nomination. But as the area is
> rather large, I would longer term be happier if we have separate
> maintainers for QGrap
my Qt build script configure options for years: -opensource
-developer-build -no-style-motif -no-style-cde ...
I mean I'm +1 for removing those mammoths :)
regards,
Konstantin
2012/9/19 Bache-Wiig Jens :
> As we are cleaning up some QStyle related things for Qt5, we are planning on
> removing t
Hi,
I'd like to nominate a couple of new maintainers for some parts of Qt currently
lacking a maintainer.
For the kernel subdirectory in Qt Widgets, I'd like to nominate Samuel Roedal.
He's been working a lot with the QPA infrastructure and implemented most of the
QWidget/QWindow split.
For
As we are cleaning up some QStyle related things for Qt5, we are planning on
removing the now ancient motif and cde styles from qtbase. These were designed
for platforms and desktops that are no longer supported in Qt5 and there is not
much value in including them in all of our Qt 5 source packa
On 19 September 2012 10:40, André Somers wrote:
>
> Just a bit of syntactic sugar, of course, but nice. I do think there are
> some problems with error checking though. What happens if "MyColumnName"
> doesn't contain an int but a string in the above call?
The same that would happen with
query.va
yes, this is my want! thanks for you reply!
and I has another question, why text component has not 'delete' function,
just 'cut', it will replace clipboard content and sometime I don't want it.
will text add more operation api for more flexible usage?
On Sep 19, 2012 4:30 PM, "Jiang Jiang" wrote:
André Somers wrote:
> Op 19-9-2012 11:32, Andras Mantia schreef:
>> Thiago A. Corrêa wrote:
>>
>>> Hi,
>>>
>>>I'd like to propose a templated QSqlQuery::value in the same way
>>> QVariant::value works. This syntax suggar allows one to write:
>>>
>>>QSqlQuery query;
>>>...
>
Op 19-9-2012 11:32, Andras Mantia schreef:
> Thiago A. Corrêa wrote:
>
>> Hi,
>>
>>I'd like to propose a templated QSqlQuery::value in the same way
>> QVariant::value works. This syntax suggar allows one to write:
>>
>>QSqlQuery query;
>>...
>>int myvalue = query.val
Thiago A. Corrêa wrote:
> Hi,
>
> I'd like to propose a templated QSqlQuery::value in the same way
> QVariant::value works. This syntax suggar allows one to write:
>
> QSqlQuery query;
> ...
> int myvalue = query.value(0);
>
> Instead of the current:
> int my
Hi Liang,
On Wed, Sep 19, 2012 at 10:16 AM, liang wrote:
> I read the source, every text component has a QTextDocument object,
> and it support full-function document layout, It seem too weight for a
> text component.
>
> for most time, I just use text component with one-line (or one-word),
> lik
I read the source, every text component has a QTextDocument object,
and it support full-function document layout, It seem too weight for a
text component.
for most time, I just use text component with one-line (or one-word),
like text-label in a video game, It is very simple, and will be made a
ma
23 matches
Mail list logo
