On 14/10/14 16:41, "Simon Hausmann"
wrote:
>On Tuesday 14. October 2014 14.28.05 Thiago Macieira wrote:
>> On Tuesday 14 October 2014 11:59:50 Knoll Lars wrote:
>> > >Since it's a large refactoring, if we miss 5.4, I don't think we
>>should
>> > >add it
>> > >to 5.4 at all. And since it's totally
Hi, Thiago and Giulio.
We had talk on #qt today regarding problem with &wl_display_interface
from libwayland being shadowed by &wl_display_interface from
wayland-scanner-generated source code:
WL_EXPORT const struct wl_interface wl_display_interface = {
"wl_display", 1,
2, wl_dis
On Tuesday 14 October 2014 13:44:30 Tomaz Canabrava wrote:
> On Tue, Oct 14, 2014 at 1:35 PM, Milian Wolff wrote:
> > On Tuesday 14 October 2014 13:22:51 Tomaz Canabrava wrote:
> > > People, I'v read everything on the other two e-mails and I'v changed
> >
> > quite
> >
> > > a few things here an
On Tue, Oct 14, 2014 at 1:35 PM, Milian Wolff wrote:
> On Tuesday 14 October 2014 13:22:51 Tomaz Canabrava wrote:
> > People, I'v read everything on the other two e-mails and I'v changed
> quite
> > a few things here and again I ask for some advice.
> >
> > What I'v done:
> >
> > QConfig / QConfi
On Tuesday 14 October 2014 13:22:51 Tomaz Canabrava wrote:
> People, I'v read everything on the other two e-mails and I'v changed quite
> a few things here and again I ask for some advice.
>
> What I'v done:
>
> QConfig / QConfigGroup / QConfigWatcher combo classes, to be used from the
> user
> Q
People, I'v read everything on the other two e-mails and I'v changed quite
a few things here and again I ask for some advice.
What I'v done:
QConfig / QConfigGroup / QConfigWatcher combo classes, to be used from the
user
QConfigIniBackend, to be used internally.
QConfig:
uses a 'global' QHas
On Tuesday 14. October 2014 14.28.05 Thiago Macieira wrote:
> On Tuesday 14 October 2014 11:59:50 Knoll Lars wrote:
> > >Since it's a large refactoring, if we miss 5.4, I don't think we should
> > >add it
> > >to 5.4 at all. And since it's totally binary incompatible, it wouldn't be
> > >added to 5
On Tuesday 14 October 2014 11:59:50 Knoll Lars wrote:
> >Since it's a large refactoring, if we miss 5.4, I don't think we should
> >add it
> >to 5.4 at all. And since it's totally binary incompatible, it wouldn't be
> >added to 5.x at all.
>
>
> Are you asking to delay the beta, or for an except
Hi Thiago,
On 14/10/14 13:42, "Thiago Macieira" wrote:
>On Tuesday 14 October 2014 09:08:54 Heikkinen Jani wrote:
>> Packages should have final beta content
>
>Hi guys, I need an exception for beta content. I have a pending refactor
>of
>QVersionNumber that still isn't approved. It should integ
On Tuesday 14 October 2014 09:08:54 Heikkinen Jani wrote:
> Packages should have final beta content
Hi guys, I need an exception for beta content. I have a pending refactor of
QVersionNumber that still isn't approved. It should integrate without problems
once it's approved (FamousLastWords™), bu
On Tuesday 14 October 2014 21:14:10 Ben McGinnes wrote:
> I can't speak for Kurt, but mine is just a couple of lines in one
> file, though it might be better served by a script to detect the
> correct attributes for that file and apply them during (or immediately
> after) installation.
If in doubt
On Tuesday 14 October 2014 06:22:51 Knoll Lars wrote:
> Hi Milian,
>
> On 13/10/14 12:41, "Milian Wolff" wrote:
>
>
> >Hey all,
> >
> >I have a question regarding the handling of optional dependencies, and
> >how
> >that influences the distribution of Qt code, esp. the creation of
> >tarballs
Hi,
supplying a QVariant property containing a custom type towards QML does not
work (even if it is registered as a metatype).
Currently I am explicitly converting the custom type to something QML
understands, like:
if (variant.canConvert()) {
MyCustomType1 t = variant.value();
//strea
On 14/10/2014 6:57 pm, Thiago Macieira wrote:
>
> Bug fixes go to the oldest branch where the fix is applicable, not
> the branch where the bug manifests.
I'm not entirely sure which that would be, I know it's not in 4.8.6
because it's still behaving itself as normal, along with the lib
bindings.
On Tue, Oct 14, 2014 at 09:34:47AM +0100, Sean Harmer wrote:
> On 14/10/2014 08:01, Koehne Kai wrote:
> >
> >> -Original Message-
> >> From: development-bounces+kai.koehne=theqtcompany.com@qt-
> >> [...]
> >> I don't have an "authoritative" answer, but one possible option would be an
> >> s
Hi all,
We have finally updated content in Qt5.4 beta snapshot packages.
Linux packages are here:
http://download.qt-project.org/snapshots/qt/5.4/5.4.0-beta/2014-10-13_44/
Most of windows ones here:
http://download.qt-project.org/snapshots/qt/5.4/5.4.0-beta/2014-10-14_40/
Unfortunately mac p
On 14/10/2014 09:36, Ray Donnelly wrote:
> On Tue, Oct 14, 2014 at 9:34 AM, Sean Harmer wrote:
>> On 14/10/2014 08:01, Koehne Kai wrote:
-Original Message-
From: development-bounces+kai.koehne=theqtcompany.com@qt-
[...]
I don't have an "authoritative" answer, but one po
On Tue, Oct 14, 2014 at 9:34 AM, Sean Harmer wrote:
> On 14/10/2014 08:01, Koehne Kai wrote:
>>
>>> -Original Message-
>>> From: development-bounces+kai.koehne=theqtcompany.com@qt-
>>> [...]
>>> I don't have an "authoritative" answer, but one possible option would be an
>>> sub-module that
On 14/10/2014 08:01, Koehne Kai wrote:
>
>> -Original Message-
>> From: development-bounces+kai.koehne=theqtcompany.com@qt-
>> [...]
>> I don't have an "authoritative" answer, but one possible option would be an
>> sub-module that contains the assets for examples or (easier?) separate the
>
Den 14-10-2014 08:59, Kurt Pattyn skrev:
> how do these applications comply with MISRA?
MISRA is impossible to comply with for a framework. For example,
consider the required rule 0-1-11: "There shall be no unused parameters
(named or unnamed) in non-virtual functions."
With this, void f(int /*
On Tuesday 14 October 2014 08:59:27 Kurt Pattyn wrote:
> 1. Is it worth the (big) effort to try to remove these warnings from the
> public part of Qt?
Again, it depends on how intrusive those patches are. We already build Qt with
a compiler warning check for all public headers and we could add a
On Tuesday 14 October 2014 18:13:54 Ben McGinnes wrote:
> > After a long time, I finally found time again to help Qt forward (at least
> > that is what I hope ). I have a few questions regarding the 'new'
> > branching scheme:
> > 1. Is this somewhere documented?
> > 2. Where do bug fixes go? I ta
Il 14/10/2014 08:40, Kurt Pattyn ha scritto:
I have a few questions regarding the 'new' branching scheme:
1. Is this somewhere documented?
Yes: http://qt-project.org/wiki/Branch-Guidelines
2. Where do bug fixes go? I talked to Peppe regarding this, and according to
him, bugs should be commit
On 14/10/2014 5:40 pm, Kurt Pattyn wrote:
> Hi,
>
> After a long time, I finally found time again to help Qt forward (at least
> that is what I hope :-) ).
> I have a few questions regarding the 'new' branching scheme:
> 1. Is this somewhere documented?
> 2. Where do bug fixes go? I talked to Pep
> -Original Message-
> From: development-bounces+kai.koehne=theqtcompany.com@qt-
> [...]
> I don't have an "authoritative" answer, but one possible option would be an
> sub-module that contains the assets for examples or (easier?) separate the
> Qt 3d examples and their assets into a stan
25 matches
Mail list logo
