Re: [Development] Qt::WA_PaintOnScreen Changes
On Sat, Aug 23, 2014 at 12:40 PM, David Narvaez david.narv...@computer.org 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 with this flag set. Could somebody take a quick look at that report and tell me if I should add to that report or create a new one? I am just wondering since the bug report is quite old. Ping? David E. Narvaez ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Qt::WA_PaintOnScreen Changes
On Thu, Aug 14, 2014 at 12:34 PM, Shaw Andy andy.s...@digia.com 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 have read the docs carefully) but after adding that the widget keeps painting black. I'll prepare a simple case to reproduce this and file a bug report. David E. Narvaez ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Qt::WA_PaintOnScreen Changes
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 rendering fine again. I would like to know if that was a good idea and what are the implications or if this is a bug in Qt. Thanks. David E. Narvaez [0] http://edu.kde.org/images/screenshots/kig.png [1] http://blog.dmaggot.org/wp-uploads/2014/08/kigbug.png ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Compiling with GCC 4.8
On Tue, Apr 23, 2013 at 6:45 PM, Thiago Macieira thiago.macie...@intel.com 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 Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Compiling with GCC 4.8
On Wed, Mar 27, 2013 at 12:20 PM, Olivier Goffart oliv...@woboq.com 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 specifier. — end note ]
Which I read that this explicitly allows code like this:
templatetypename T constexpr int foo(T) { return 0; };
template int foo(int) { return 1; }
So the bug should be reported to GCC if it still do not compile with the
4.8
release.
(Note: this does not mean it was a bad idea to work around the bug)
Thanks for the clarification, I reported the bug[0] - just fixed the
section number to 7.1.5. Your sample code compiles fine in Clang, btw.
David E. Narváez
___
Development mailing list
Development@qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Compiling with GCC 4.8
On Wed, Mar 27, 2013 at 9:51 AM, Thiago Macieira thiago.macie...@intel.com 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 release. We don't need the churn in our code. In this particular case, the situation was a semantic problem with our code that GCC 4.8 would no longer allow, so it was clearly not a compiler bug. In those situations, maybe we can agree to make sure the patch goes to the release branch too. David E. Narvaez ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] [GSTREAMER/QML] How to pass custom options from qml to gst
On Wed, Mar 27, 2013 at 8:27 AM, Matteo Brichese mbrich...@came.it 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 it's hw accelerated, now I'm trying to make some test with QtMultimedia5 and the Video element inside QML. The video element with my video test don't work out of the box, so I'm asking you if there is some particular method to pass some extra parameter to the gstreamer for playing the video. I've some particular command for the gst pipeline like nv_omx_videosink and other nvidia related things that the default video element can't know. So, how can I play a video embedded in a qml file thru gst? You're better off asking this question in the gstreamer-devel[0] list. David E. Narvaez [0] http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Disconnect Signal 0
On Fri, Mar 8, 2013 at 1:48 AM, Thiago Macieira thiago.macie...@intel.com 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 QDBusAbstractInterface::disconnectNotify in this case and it iterates over all signal names to pass them along, right? David E. Narváez ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Disconnect Signal 0
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 take care of this bug but the question is how do we prefer to fix it: should we multiplex at QObject::disconnect level or start looking around to support signal = 0 in all other places? David E. Narváez [0] https://bugreports.qt-project.org/browse/QTBUG-29498 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] QTBUG-29082 and Next Releases
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 4.8 since it was marked as critical? Also, will 4.7 have a patch release? If so, will this fix be backported to 4.7? Thanks and sorry for the confusion. David E. Narváez ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Compiling with GCC 4.8
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 ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Compiling with GCC 4.8
On Sat, Feb 23, 2013 at 12:29 PM, Thiago Macieira thiago.macie...@intel.com 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 errors. No one has reported anything. Well, I think I got scared with the amount of errors I got from my first try but apparently it is all solved with a rather simple patch I have put on codereview. I added you as a reviewer, if anybody else is interested just let me know. David E. Narváez ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
