On 26.03.2014 15:31, Sergio Ahumada wrote:
Hi,
I'd like to nominate Bernd Weimer as approver for the Qt Project.
Bernd has been around Qt since 2007 as a Professional Services Engineer
in Trolltech, then as part of Nokia and now in BlackBerry.
Bernd has contributed mostly to the QNX and
On 04/15/2014 07:13 PM, Thiago Macieira wrote:
I'd like to nominate Jake Petroules as approver.
+1
Christian
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
On Tuesday 15 April 2014 08:02:56 Thiago Macieira wrote:
Em ter 15 abr 2014, às 09:49:53, Matthew Woehlke escreveu:
If you add the rule that callbacks can't be removed once registered, you
could do an atomic exchange of the old callback for the new, and require
that any attached callback
15 working days have passed, so Bernd is now an approver of the Qt Project.
I've added him to the Approvers group on Gerrit, but somebody else would
need to grant him rights in JIRA.
Done.
--
Alex
___
Development mailing list
Hi all,
Qt Embedded Enterprise update and Qt Creator 3.1 are now released.
For more details and download instructions, check the blog posts:
http://blog.qt.digia.com/blog/2014/04/15/update-for-qt-enterprise-embedded
http://blog.qt.digia.com/blog/2014/04/15/qt-creator-3-1-0-released
Br,
Kalle
Hello Fabian, all.
Like you, I also suspect that the fact that QWidget stays on the screen has to
do with the 4 platform windows or something like that. All I know is that,
once setScreen() is called on a QWidget, it gets to the point where it makes
the QWidgetBackingStore dirty, issuing an
Hi,
Option #2 is good enough, isn't it? QWindow::setScreen() already states If the
window has been created, it will be recreated on the \a newScreen. This could
be extended with a note about the visibility, like in QWindow::create(): the
window remains hidden until setVisible() is called.
As
On 14 Apr 2014, at 2:26 PM, Simon Hausmann wrote:
We have various parsers in Qt that parse source code and do things with it,
such as the QML parser…
I was just baffled by this issue this morning for a couple of hours: tried to
port some QML code that was working fine with Qt 5.2.1 to
Hi,
this is tracked by https://bugreports.qt-project.org/browse/QTBUG-37423
- keeping an eye on the release blocking bugs
https://bugreports.qt-project.org/browse/QTBUG-37065 occasionally helps
to minimize surprises ;-) .
Friedemann
--
Friedemann Kleint
Digia, Qt
As mentioned on https://codereview.qt-project.org/#change,83272 Kevin Funk
measured the difference between the current approach and using atomics using
Olivier's initial benchmark, it's about 4-5x slower for checking if there's a
callback set. Since this is affecting every Qt application on a
Hi,
actually re-creating the window is a bit wasteful given that the screens
are part of a larger virtual desktop in most cases. A move() would be
sufficient. The QWindow/QScreen logic as it is is somehow not well
suited for virtual desktops in which the screen is determined by the
geometry.
On Wed, Apr 16, 2014 at 02:47:03PM +0200, Friedemann Kleint wrote:
Hi,
actually re-creating the window is a bit wasteful given that the screens
are part of a larger virtual desktop in most cases. A move() would be
sufficient. The QWindow/QScreen logic as it is is somehow not well
suited
Em seg 14 abr 2014, às 10:33:48, Thiago Macieira escreveu:
Em seg 14 abr 2014, às 09:59:18, Thiago Macieira escreveu:
Also, the Unix philosophy is that UTF-8 BOMs should not be used. This
started on Windows, with tools like Notepad, where changing the system
locale is not an option.
To
Em qua 16 abr 2014, às 07:51:50, Blasche Alexander escreveu:
15 working days have passed, so Bernd is now an approver of the Qt Project.
I've added him to the Approvers group on Gerrit, but somebody else would
need to grant him rights in JIRA.
Done.
Hi Alex
Can you do the same for Sze? I
Hi Thiago,
I did that already:
http://lists.qt-project.org/pipermail/development/2014-April/016378.html
I think you just doubled up on Gerrit later on :).
--
Alex
From: development-bounces+alexander.blasche=digia@qt-project.org
On Wed, Apr 16, 2014 at 6:18 AM, Rafael Roquetto
rafael.roque...@kdab.com wrote:
On Wed, Apr 16, 2014 at 02:47:03PM +0200, Friedemann Kleint wrote:
Hi,
actually re-creating the window is a bit wasteful given that the screens
are part of a larger virtual desktop in most cases. A move() would
On 2014-04-16 03:18, Volker Krause wrote:
On Tuesday 15 April 2014 08:02:56 Thiago Macieira wrote:
In other words: use QBasicAtomicPointer.
As mentioned on https://codereview.qt-project.org/#change,83272 Kevin Funk
measured the difference between the current approach and using atomics using
On Mon, Apr 14, 2014 at 12:25 PM, Matt Broadstone mbroa...@gmail.comwrote:
On Mon, Apr 14, 2014 at 7:07 AM, Rutledge Shawn
shawn.rutle...@digia.comwrote:
On 11 Apr 2014, at 10:15 PM, Matt Broadstone wrote:
Hi,
We're experiencing an odd crash while running our Qt Quick application
in a
On Wed, Apr 16, 2014 at 1:21 PM, Matt Broadstone mbroa...@gmail.com wrote:
On Mon, Apr 14, 2014 at 12:25 PM, Matt Broadstone mbroa...@gmail.comwrote:
On Mon, Apr 14, 2014 at 7:07 AM, Rutledge Shawn shawn.rutle...@digia.com
wrote:
On 11 Apr 2014, at 10:15 PM, Matt Broadstone wrote:
Hi,
Hi guys,
I am working in a qtorganizer plugin[1] for EDS, it is almost done, I still
have some missing features to implement but is already usable for most
common use cases.
But what I facing now is the lack of API to update recurrence events, I
would like to have a way to say to
Why? Is there any sense in modifying a generated recurrence item? AFAIK,
you should work on that generated recurrence item's parent and modify it's
recurrence rules instead.
Am I missing something?
Regards,
Konstantin
2014-04-16 21:56 GMT+03:00 Renato Araujo rena...@gmail.com:
Hi guys,
I
21 matches
Mail list logo
