Please ensure https://codereview.qt-project.org/#change,80277 makes it into
4.8.6; this fixes a very serious issue with QProcess on OS X 10.9.
On Mon, Mar 10, 2014 at 10:55 AM, Salovaara Akseli <
akseli.salova...@digia.com> wrote:
> Hi all,
>
> New snapshot build from Qt 4.8.6 available:
> http:
On Monday 10 March 2014 14:43:42 Agocs Laszlo wrote:
> Yes, one platform window for each native widget and one backingstore per top
> level window. (where the toplevel's backingstore is the common backingstore
> for all of its child widgets)
>
> QPA (QPlatformBackingStore) does not know anything
Can you please explain what this feature is about, why do you think
it's useful, how it's supposed to be used, etc.?
On 10 March 2014 17:30, mikhail.svet...@gmail.com
wrote:
> Hello, I would like to clarify wherein the complexity
> (https://codereview.qt-project.org/#change,80412)?
> Ready to lis
Hello, I would like to clarify wherein the complexity
(https://codereview.qt-project.org/#change,80412)?
Ready to listen to any suggestions and implement them.
--
Mikhail Svetkin
___
Development mailing list
Development@qt-project.org
http://lists.qt-p
On Monday, March 10, 2014 10:24:08 Sarajärvi Tony wrote:
> Does anyone have any experience setting up a page like that?
You could ask Kitware about setting up a project on http://my.cdash.org/ .
Several KDE project builds are submitted there already.
I'm intending to get something like that wor
Hi all,
New snapshot build from Qt 4.8.6 available:
http://download.qt-project.org/snapshots/qt/4.8/2014-03-10_510/
Packages are built against sha1 0315971ee951e9abe7f288564ddf2e81aeed1fd8 "Qt 3
Support: Prevent double deletion of QObjectPrivate::threadData in QSettings"
(HEAD) and this build
Yes, one platform window for each native widget and one backingstore per top
level window. (where the toplevel's backingstore is the common backingstore for
all of its child widgets)
QPA (QPlatformBackingStore) does not know anything about paint devices, paint
engines and such. It allows you to
On Monday 10 March 2014 09:20:14 Agocs Laszlo wrote:
> > > I'm implementing a QPA plugin (now with 5.3 snapshot) and there's
> > > something
> > > I do not understand: When I use native widgets, every widget creates a
> > > QPlatformWindow, but only a toplevel window creates a
> > > QPlatformBacki
Hi
While in Berlin, I was asked if Qt couldn't have a dashboard to which anyone
could append build and test results of Qt in different platform and compilers.
Just like this one for CMake: http://open.cdash.org/index.php?project=CMake
Does anyone have any experience setting up a page like that?
On 03/08/2014 09:36 PM, Thiago Macieira wrote:
>> If someone, including the requesting party themselves, does such work, I’m
>> >sure there are reviewers / approvers ready to do the reviewing.
> Oh, sure. If someone supplied the rewrite, I'm sure we'd be happy to take it
> in. We might even help ou
On 10 March 2014 09:27, Kurt Pattyn wrote:
> But we can use a QueuedConnection if the PauseMode is set to
> PauseOnSslErrors, or can't we?
The idea is that you can. The socket will be paused and won't proceed
until a call to resume.
If the QueuedConnection usage comes from the idea of using mul
On Monday 10 March 2014 09:20:14 Agocs Laszlo wrote:
> > > Question: when a QWidget now creates a QPainter on it, how does my QPA
> > > plugin know onto which QWindow it is currently acting, when there's only
> > > one paintDevice/one backing store ?
> As for the painting step, QPA has almost noth
> > I'm implementing a QPA plugin (now with 5.3 snapshot) and there's something
> > I do not understand: When I use native widgets, every widget creates a
> > QPlatformWindow, but only a toplevel window creates a
> > QPlatformBackingStore, which is the class which delivers the paintDevice
> > imple
Hi,
Sorry to disappoint, but to the best of my knowledge there is no ongoing port
for iOS at this point in time.
--
Alex
From: development-bounces+alexander.blasche=digia@qt-project.org
[development-bounces+alexander.blasche=digia@qt-project.org] on b
> On 10 Mar 2014, at 08:37, "Giuseppe D'Angelo" wrote:
>
>> On 10 March 2014 07:43, Kurt Pattyn wrote:
>> Is the documentation on the signal sslErrors() still correct then: "Note:
>> You cannot use Qt::QueuedConnection when connecting to this signal, or
>> calling QSslSocket::ignoreSslErrors()
Fredag 7. mars 2014 17.18.58 skrev Jan Kundrát:
> On Tuesday, 25 February 2014 20:12:57 CEST, Thiago Macieira wrote:
> > Also, I don't know of any project that has a CI-controlled integration.
>
> OpenStack. Full documentation on their setup (which, btw, tests each and
> every commit separately) i
On 10 March 2014 07:43, Kurt Pattyn wrote:
> Is the documentation on the signal sslErrors() still correct then: "Note:
> You cannot use Qt::QueuedConnection when connecting to this signal, or
> calling QSslSocket::ignoreSslErrors() will have no effect." ?
I presume it's still correct in order to
17 matches
Mail list logo
