On Sat, Aug 23, 2014 at 12:40 PM, David Narvaez
wrote:
> I was ready to create my bug report with sample code etc, and came across
>
> https://bugreports.qt-project.org/browse/QTBUG-26358
>
> which seems to be related because I was able to confirm paintEvent is
> not called
On Wed, Aug 20, 2014 at 12:17 PM, David Narvaez
wrote:
> On Thu, Aug 14, 2014 at 12:34 PM, Shaw Andy wrote:
>> If you were using WA_PaintOnScreen then you also need to ensure you
>> reimplement paintEngine() to return 0. Had you done that at all?
>
> Thanks for your help a
On Thu, Aug 14, 2014 at 12:34 PM, Shaw Andy wrote:
> If you were using WA_PaintOnScreen then you also need to ensure you
> reimplement paintEngine() to return 0. Had you done that at all?
Thanks for your help and sorry for the late reply. I was missing the
return 0 on paintEngine() (I should hav
Hi,
I am porting an application to Qt5/KF5 and was surprised to see the
main widget of the application was showing all black. There are
screenshots of the original version and the buggy version[1] online. I
removed
setAttribute( Qt::WA_PaintOnScreen, true );
on that widget and the widget was ren
On Tue, Apr 23, 2013 at 6:45 PM, Thiago Macieira
wrote:
> [0] was missing. Can you give me the link?
It was left as an exercise for the reader.
David E. Narvaez
[0] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56871
___
Development mailing list
Develop
On Wed, Mar 27, 2013 at 12:20 PM, Olivier Goffart wrote:
> I don't think the problem was in our code.
> I beleive GCC 4.8 Is wrong.
>
> The C++11 standard § 7.5.1 1 says:
> [ Note: An explicit specialization can differ from the template
> declaration
> with respect to the constexpr specifi
On Wed, Mar 27, 2013 at 8:27 AM, Matteo Brichese wrote:
> Hi everyone, I don't know if this is the right place to ask this question,
> but I cannot find better ML than this, so, if you know a better ML to ask,
> please tell me and sorry.
>
> I've a gstreamer 0.10.36 installation on my board and
On Wed, Mar 27, 2013 at 9:51 AM, Thiago Macieira
wrote:
> 1) I don't want fixes to issues that don't make it to the release of that
> compiler. If you can find in the standard saying the new behaviour is
> correct,
> then fine. But otherwise, it might be a compiler bug that gets fixed
> before the
On Fri, Mar 8, 2013 at 1:48 AM, Thiago Macieira
wrote:
> Effectively, disconnectNotify will get a null pointer (Qt4) or an invalid
> QMetaMethod (Qt5) to mean that all signals are being disconnected. The
> receiver needs to deal with it.
So wildcard arguments are detected at
QDBusAbstractInterfac
Hi all,
I was taking a look at bug 29498[0] and the explanation is pretty
clear on what's happening: disconnect admits char * signal = 0 as a
parameter (which means all signals) but then forwards that parameter
to other calls that apparently do not commit to support 0 as a
possible value.
I can t
Hi,
As I come to understand the branch workflow a bit better, I think I
messed up the information in QTBUG-29082 when closing the bug. Since
it was committed to stable, it means it won't be available in the next
patch release, right? Should it be made available in the next patch
releases in 5 and
On Sat, Feb 23, 2013 at 12:29 PM, Thiago Macieira
wrote:
> I haven't seen any patches fixing warnings or compilation errors come in for
> 4.8. Usually, there are a few warnings that need fixing but until my -Werror
> patches land, those are not stoppers.
>
> Usually, there are no compilation error
Hi,
Is anybody currently working on compatibility with GCC 4.8? I know
that, at the moment, qtdelcarative (stable) can be built with GCC 4.8
and qtbase (stable) cannot; and I'd like to know if anybody has a
branch where this is being fixed.
David E. Narváez
___
13 matches
Mail list logo
