Re: [Development] Two source incompatibilities in Qt 5.5 with Clang

2015-03-12 Thread Thiago Macieira
On Thursday 12 March 2015 23:22:17 Stephen Kelly wrote: > Thiago Macieira wrote: > > This was intentional and the minor SIC was expected. It only happens if > > you're calling a static function that only exists for Q_ASSERT -- not many > > people do that. > > Oops, nobody told Allen: > > https:/

Re: [Development] Two source incompatibilities in Qt 5.5 with Clang

2015-03-12 Thread Stephen Kelly
Thiago Macieira wrote: > This was intentional and the minor SIC was expected. It only happens if > you're calling a static function that only exists for Q_ASSERT -- not many > people do that. Oops, nobody told Allen: https://github.com/KDAB/GammaRay/commit/44ac33d970e I think this affects far

Re: [Development] The dark side of QtSvg

2015-03-12 Thread Massimo Callegari
Guido, Giuseppe, I got your points. It's so sad to read "we don't have the resources" cause I believe Qt has an enormous potential and I enjoy every day using it (except when I can't get things to work lol) As for me taking care of such matterswellyou don't really want that :) (and I hav

Re: [Development] qt3d examples with qt5.5 crashing (Friedemann Kleint)

2015-03-12 Thread Arjun Das
>When i try to run any of the compiled qt3d application's release version.The application crashes, and this are the error details collected by windows: >>I don''t see any crashes with MSVC2013 64bit/5.5. Can you please provide >>a stack trace and the output of the qtdiag tool? Hi, I am sorry bu

Re: [Development] The dark side of QtSvg

2015-03-12 Thread Guido Seifert
> So my wonder is this: if the SVG rendering of QtWebKit/QtWebEngine is modern > and solid, why not "extracting" it > from those monsters and place it into a brand new QtSvg ? Very easy to ask for something like that. When do you start? > This would bring two advantages:1- applications that n

Re: [Development] The dark side of QtSvg

2015-03-12 Thread Giuseppe D'Angelo
On 12 March 2015 at 16:47, Massimo Callegari wrote: > > 3- it removes duplicated code between QtSvg and QtWebEngine But there's no such code. QtWebEngine is a "thin" wrapper around Blink/Chromium. The idea is precisely that Qt currently does not have the resources for maintaining its port/fork of

Re: [Development] The dark side of QtSvg

2015-03-12 Thread Julien Blanc
On 12/03/2015 16:47, Massimo Callegari wrote: Apologies if my mail doesn't have proper carriage returns in pipermail ! (my crappy webmail's fault) Just want to add a third advantage in decoupling QtWebEngine from SVG: 3- it removes duplicated code between QtSvg and QtWebEngine Just a note. F

[Development] The dark side of QtSvg

2015-03-12 Thread Massimo Callegari
Apologies if my mail doesn't have proper carriage returns in pipermail ! (my crappy webmail's fault) Just want to add a third advantage in decoupling QtWebEngine from SVG: 3- it removes duplicated code between QtSvg and QtWebEngine Cheers, Massimo___ Dev

[Development] The dark side of QtSvg

2015-03-12 Thread Massimo Callegari
Hi everyone,following my last November's email about QtMultimedia  (http://lists.qt-project.org/pipermail/development/2014-November/019035.html)  (where in 4 months almost all the efforts kept on going to camera support...leaving almost 200 tickets rotting on JIRA) it seems that my lack of luck c

Re: [Development] qt3d examples with qt5.5 crashing

2015-03-12 Thread Friedemann Kleint
Hi, >When i try to run any of the compiled qt3d application's release version.The application crashes, and this are the error details collected by windows: I don''t see any crashes with MSVC2013 64bit/5.5. Can you please provide a stack trace and the output of the qtdiag tool? Regards, Fried

Re: [Development] QtCore missing check for memory allocation

2015-03-12 Thread Thiago Macieira
On Tuesday 10 March 2015 10:10:46 Alex Montgomery wrote: > > Note that we're talking about a standard violation in the first place. The > > standard says you can replace operator new, so if MSVC doesn't allow you > > to do it properly, then you can throw the standard out of the window. If > > an in