On sexta-feira, 20 de janeiro de 2017 18:27:31 PST René J. V. Bertin wrote:
> Thiago Macieira wrote:
> > It is used in QtWidgets and possibly other modules. It may have suffered
> > from the problem of loading the wrong library at runtime, but didn't
> > crash because the new uic didn't use any sym
On sexta-feira, 20 de janeiro de 2017 17:34:50 PST Grégoire Barbier wrote:
> > See the discussion in https://codereview.qt-project.org/83404/ for why
> > this is not a good idea.
> > In summary, BlockingQueuedConnection is dangerous as it can lead to
> > deadlock if the other thread is waiting on y
On sexta-feira, 20 de janeiro de 2017 14:55:00 PST Sean Harmer wrote:
> Hi,
>
> Just a query about the coding convention around inclusion of private headers
> as specified at:
>
> https://wiki.qt.io/Coding_Conventions#Including_headers
>
> It states:
>
> If you need to include private headers,
>
> I respect the fact that you rejected Qt::BlockingAutoConnection in 2014
> because of its potential danger, but I'm not sure that it's better to let
> people use the "QThread::currentThread() == this" pattern without being
> warned rather than implementing Qt::BlockingAutoConnection, with a
Oswald Buddenhagen wrote:
> check whether qtmultimedia/{config_help.txt,configure.json} exist and
They do.
> claim support.
I think I can do better: apparently I have found the culprit. In the Features
section of qtmultimedia/src/multimedia/configure.json:
"pulseaudio": {
Sorry, wrong quotation, I meant to quote original letter
Иван Комиссаров
> 20 янв. 2017 г., в 20:26, abba...@gmail.com написал(а):
>
> Hm, I already started a project that supports that functionality as a
> replacement to the current image formats:
> https://github.com/ABBAPOH/imageformats-ng
>
20.01.2017, 00:22, "Oswald Buddenhagen" :
> On Thu, Jan 19, 2017 at 07:34:08PM +0100, Giuseppe D'Angelo wrote:
>> Nonetheless, since such loaders would be useful in more than one place
>> (qtbase, qtdeclarative, qt3d) I think that the best place for them would
>> be a new private library in qt
Thiago Macieira wrote:
> It is used in QtWidgets and possibly other modules. It may have suffered from
> the problem of loading the wrong library at runtime, but didn't crash because
> the new uic didn't use any symbols that are new in 5.8.
That'd be an explanation, but is that what the "-version
Hm, I already started a project that supports that functionality as a
replacement to the current image formats:
https://github.com/ABBAPOH/imageformats-ng
http://abbapoh.github.io/docs/imageformats-ng/
Иван Комиссаров
> 20 янв. 2017 г., в 13:14, Laszlo Agocs написал(а):
>
>
> Hmm right. Could
On sexta-feira, 20 de janeiro de 2017 10:51:20 PST René J. V. Bertin wrote:
> > But uic should be suffering from this
>
> Too late to check now :)
> Is uic used during the build? If it is it was clearly not "suffering from
> this"!
It is used in QtWidgets and possibly other modules. It may have
Le 20/01/2017 à 11:14, Olivier Goffart a écrit :
On Dienstag, 17. Januar 2017 11:21:56 CET Grégoire Barbier wrote:
Le 16/01/2017 à 10:34, Olivier Goffart a écrit :
> What's the use case for this function? For direct call you better of
> calling the function directly, and the equivalent of Queue
Hi,
Just a query about the coding convention around inclusion of private headers
as specified at:
https://wiki.qt.io/Coding_Conventions#Including_headers
It states:
If you need to include private headers, be careful. Use the following syntax,
irrespective of which module or directory whatever
On Friday 20 January 2017 11:06:34 Oswald Buddenhagen wrote:
> On Fri, Jan 20, 2017 at 09:10:45AM +0100, Marc Mutz wrote:
> > I noted that mere mortals can't stage stuff to 5.6 anymore, and no-one
> > else does, either, at least for qtbase (last was on Jan 10th, when
> > appearently there wasn't a
Thiago Macieira wrote:
> Don't assume. The question stands.
QED:
%> rm -rf /path/to/build/qtmultimedia
%> tar -xf /path/to/qt-everywhere-opensource-src-5.8.0-rc.tar.xz qt-everywhere-
opensource-src-5.8.0-rc/qtmultimedia
%> (cd /path/to/build ;
/path/to/qt-everywhere-opensource-src-5.8.0-rc/conf
On Dienstag, 17. Januar 2017 11:21:56 CET Grégoire Barbier wrote:
> Le 16/01/2017 à 10:34, Olivier Goffart a écrit :
> > What's the use case for this function? For direct call you better of
> > calling the function directly, and the equivalent of QueuedConnection
> > can be achieved with QTimer::s
Hmm right. Could be that it is less relevant today. Android's etc1tool only did
PKM but perhaps that is not so interesting anymore with the advent of ETC2.
Cheers,
Laszlo
From: Giuseppe D'Angelo
Sent: Friday, January 20, 2017 11:11:09 AM
To: Laszlo Agocs; de
Il 20/01/2017 11:05, Laszlo Agocs ha scritto:
> Ok. Adding support for ETC1/2 in PKM containers may be useful too (Qt 3D
> should have some code for it IIRC), but that can be added later.
>
Is there anyone using those containers? Last time I checked I had a very
hard time finding specifications f
Ok. Adding support for ETC1/2 in PKM containers may be useful too (Qt 3D should
have some code for it IIRC), but that can be added later.
Cheers,
Laszlo
From: giuseppe.dang...@kdab.com on behalf of
Giuseppe D'Angelo
Sent: Friday, January 20, 2017 10:45 A
On Fri, Jan 20, 2017 at 09:10:45AM +0100, Marc Mutz wrote:
> I noted that mere mortals can't stage stuff to 5.6 anymore, and no-one else
> does, either, at least for qtbase (last was on Jan 10th, when appearently
> there wasn't a lock-down, yet?).
>
> There are tons of accepted backports waiting
On Freitag, 20. Januar 2017 09:59:55 CET Benjamin TERRIER wrote:
> 2017-01-20 3:01 GMT+01:00 Thiago Macieira :
> > we also catch the even more dubious code:
> > char func[] = "deleteLater";
> > QMetaObject::invokeMethod(&obj, func);
I think we should still support that.
> >
> > T
On Thu, Jan 19, 2017 at 10:20:59PM +0100, René J. V. Bertin wrote:
> Let me try to reformulate the question: what options must I pass to
> ../qt-everywhere-opensource-src-5.8.0-rc/configure so that the qtmultimedia
> component is built without pulseaudio and gstreamer support?
>
check whether qtmu
Thiago Macieira wrote:
> The tools affected are those that can be bootstrapped but weren't (because
> it's not a cross compilation). Since they weren't bootstrapped, they link to
> the Qt libraries being compiled, which results in the linking problem.
Terminology maybe, but I thought the problem
Il 20/01/2017 09:25, Laszlo Agocs ha scritto:
> This would bring the benefit of potential reuse in the Quick (Image
> element) compressed texture support, once that materializes at some
> point in the future.
>
>
> Are ETC1 and ETC2 included? They would be fairly important as well.
Yes, but only
Il 19/01/2017 22:22, Oswald Buddenhagen ha scritto:
> you can't put it there if qtbase is to use it.
*Shees* Sorry, I planned to write that Qtbase is unlikely to use it
directly, except for providing enablers to other modules. But ok, let's
put this stuff in there.
Thanks,
--
Giuseppe D'Angelo |
Edward Welbourne wrote:
> which I suppose to be fairly explicit about which configure script he's
> talking about.
Thanks, Eddy.
I know it's important to avoid ambiguity, but I have also mentioned from the
beginning that I was doing a top-level build and it simply didn't occur to me
immediatel
On quinta-feira, 19 de janeiro de 2017 22:20:59 PST René J. V. Bertin wrote:
>> I've also been talking since the beginning about configure. Sorry
>> about the confusion.
Thiago Macieira replied:
> There are two configure scripts: one in the top-level and one in
> qtbase. Please be clear which one
2017-01-20 3:01 GMT+01:00 Thiago Macieira :
> Because it's a template, so the template when Func = char* matches better than
> the overload with const char*. I assume that using nullptr without casting
> also breaks, correct?
Correct.
> From what you explained, this will not affect the case when
Hi Giuseppe,
It is hard to say for sure without seeing the actual code, but if there are no
3rd party dependencies involved and all we are talking about is a compact,
private helper class in the style of Qt3D's current TextureLoadingHelper, then
adding it next to QOpenGL* in QtGui is still th
Hi,
I noted that mere mortals can't stage stuff to 5.6 anymore, and no-one else
does, either, at least for qtbase (last was on Jan 10th, when appearently
there wasn't a lock-down, yet?).
There are tons of accepted backports waiting to be staged, some for security-
critical fixes...
What's goin
29 matches
Mail list logo
