On Sep 25, 2014, at 4:07 PM,
wrote:
>
>> I think if this feature would be added to QtCore, it should be by extending
>> QMetaObject::invoke to work with functors.
>> By using Qt::BlockingQueuedConnection that would be very similar to what you
>> have done.
>
> I reported this before in Qt is
On Thursday 25 September 2014 16:33:12 Tomaz Canabrava wrote:
> Long that that I have send this e-mail already, but better late than never.
> In the Qt Develompent Summit I raised my hand to get one dirty thing done:
>
> The Settings.
>
> After a good while with negative time ( Real Work, KDE, Su
On 5September2014, at 12:33, Tomaz Canabrava wrote:
> Long that that I have send this e-mail already, but better late than never.
> In the Qt Develompent Summit I raised my hand to get one dirty thing done:
>
> The Settings.
>
The general idea appeals to me.
> After a good while with nega
Long that that I have send this e-mail already, but better late than never.
In the Qt Develompent Summit I raised my hand to get one dirty thing done:
The Settings.
After a good while with negative time ( Real Work, KDE, Subsurface, and
other personal stuff ) I have finally had the time to start.
On Thursday 25 September 2014 15:12:01 Andreas Hartmetz wrote:
> Hello,
>
> we have a customer who is interested (among possibly other font
> rendering improvements) in using the same high-quality font stack on all
> platforms, for which HarfBuzz-NG / FreeType is the obvious candidate. I
> wonder
On Thursday 25 September 2014 10:17:25 Knoll Lars wrote:
> Windows: Friedemann
> WinRT: Andrew Knight
> OS X: Morten
> Linux (X11): Jørgen Lind
> Linux (Wayland): Already covered by Andy Nichols
> iOS: Tor Arne
> Android: Bogdan
> Windows CE: Björn Breitmeyer
>
> QNX is open for the moment, I’d lo
> I think if this feature would be added to QtCore, it should be by extending
> QMetaObject::invoke to work with functors.
> By using Qt::BlockingQueuedConnection that would be very similar to what you
> have done.
I reported this before in Qt issue tracker. I would really like to see
this impl
Hi,
2014-09-25 17:12 GMT+04:00 Andreas Hartmetz :
> Hello,
>
> we have a customer who is interested (among possibly other font
> rendering improvements) in using the same high-quality font stack on all
> platforms, for which HarfBuzz-NG / FreeType is the obvious candidate. I
> wonder if patches t
Technically it sounds good to me. But would it be consistent with the
responsibility of QMetaObject? It doesn't use any metadata from the object
passed, unlike the other overloads.
On Sep 25, 2014 3:14 PM, "Olivier Goffart" wrote:
> On Saturday 20 September 2014 12:41:07 Yam Marcovic wrote:
> > H
Hello,
we have a customer who is interested (among possibly other font
rendering improvements) in using the same high-quality font stack on all
platforms, for which HarfBuzz-NG / FreeType is the obvious candidate. I
wonder if patches to do that would be accepted. It seems fairly
uncontroversia
So let's all upvote https://bugreports.qt-project.org/browse/QTBUG-37253.
BTW, the way you've implemented the Dispatcher constructor is off. You
can't give it a parent from another thread. You should use
QObject::moveToThread() instead.
Björn
2014-09-25 14:14 GMT+02:00 Olivier Goffart :
> On Sa
On Saturday 20 September 2014 12:41:07 Yam Marcovic wrote:
> Hello,
>
> In my company, we started getting all tangled up with loads of signals and
> slots for many components. We also have a habit of renaming things as time
> goes by, and that can also pose a bit of a problem when dealing with
> s
But say, if I want to submit this as part of QtCore, doesn't that package
use one consistent license which I'll have to use?
On Sep 24, 2014 3:05 PM, "Tomasz Siekierda" wrote:
> On 24 September 2014 11:34, Sune Vuorela wrote:
> > On 2014-09-24, Yam Marcovic wrote:
> >> However, I will say I don
Robert Knight gmail.com> writes:
>
> Hi Alexander,
>
> See the 'fixup_framework_bundle' function in
>
https://github.com/Mendeley/Mac-OS-X-Bundle-Utilities/blob/master/
hdiutil-codesign.rb
> for code which can fix a Qt bundle.
>
> In short:
> - There should be no files in the root of the
> 'Qt
> To make it explicit, I’d like to propose the following people as
> Maintainers for different platforms:
>
> Android: Bogdan
+1
daniel
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Hi Alexander,
See the 'fixup_framework_bundle' function in
https://github.com/Mendeley/Mac-OS-X-Bundle-Utilities/blob/master/hdiutil-codesign.rb
for code which can fix a Qt bundle.
In short:
- There should be no files in the root of the
'Qt.framework' directory other than a 'Versions'
directory,
Hi,
There are currently a few empty spots in our maintainer list, and I’d like
to fill them again and make that list more complete before we have 5.4 out.
To start with, I’d like to pick up a topic that had been discussed in the
past without reaching a conclusion. It is about having platform
main
On Thursday 25. September 2014 09.44.51 Nils Jeisecke wrote:
> Hi Simon,
>
> thank you very much for the explanation. No need for bug hunting then.
>
> On Thu, Sep 25, 2014 at 7:55 AM, Simon Hausmann
>
> wrote:
> > We've changed this in Qt 5.4 slightly: When
> > converting a JavaScript object b
Hi Simon,
thank you very much for the explanation. No need for bug hunting then.
On Thu, Sep 25, 2014 at 7:55 AM, Simon Hausmann
wrote:
> We've changed this in Qt 5.4 slightly: When
> converting a JavaScript object back to a QVariant, we won't try to "destroy"
> it but instead we'll give you a Q
Sorvig Morten digia.com> writes:
>
> Is there a “QtCore.prl” at the root of the framework? If so then remove it.
>
> Morten
>
>
> ___
> Development mailing list
> Development qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development
> On 24 Sep 2014, at 16:17, Alexander Ilyin
> wrote:
>
> CODESIGN FAILED WITH MESSAGE "unsealed contents present in the root
> directory of an embedded framework In subcomponent:
> /Developer/res-plan/bin/s-test.app/Contents/Frameworks/QtCore.framework"
> (Please look at the listing below)
>
>
21 matches
Mail list logo
