Re: [Development] QtMultimedia and Musepack

2014-10-20 Thread Thiago Macieira
On Monday 20 October 2014 23:46:03 Lisandro Damián Nicanor Pérez Meyer wrote: > On Monday 06 October 2014 10:18:41 Kevin Kofler wrote: > > Cornelius Hald wrote: > > > AFAIK QtMultimedia on Linux uses Gstreamer for video and audio playback, > > > so installing the right Gstreamer plugins should (hop

Re: [Development] QtMultimedia and Musepack

2014-10-20 Thread Lisandro Damián Nicanor Pérez Meyer
On Monday 06 October 2014 10:18:41 Kevin Kofler wrote: > Cornelius Hald wrote: > > AFAIK QtMultimedia on Linux uses Gstreamer for video and audio playback, > > so installing the right Gstreamer plugins should (hopefully) fix this > > issue. > > > > Maybe this will help: > > https://apps.ubuntu.com

Re: [Development] Optional Dependencies and Distribution of Examples

2014-10-20 Thread Lisandro Damián Nicanor Pérez Meyer
On Tuesday 14 October 2014 06:22:51 Knoll Lars wrote: [snip] > A possible solution that we had discussed in Oslo was to create a > dedicated example repository that contains a set of high quality examples > that we also want to show in Creator. If this repo is built at the end, we > could make use

Re: [Development] CI broken again

2014-10-20 Thread Saether Jan-Arve
And this didn't get caught because we don't have CI revdep coverage for OSX (we revdep only linux it seems). Jan Arve Fra: development-bounces+jan-arve.saether=theqtcompany@qt-project.org på vegne av Hausmann Simon Sendt: 20. oktober 2014 21:57 Til

Re: [Development] CI broken again

2014-10-20 Thread Hausmann Simon
Great analysis - thanks guys for fixing this! Simon Original Message From: Morten Johan Sørvig Sent: Monday, October 20, 2014 21:06 To: Qt Development Group Subject: Re: [Development] CI broken again > On 20 Oct 2014, at 15:04, Saether Jan-Arve > wrote: > > Change: https://codereview.qt-pro

Re: [Development] CI broken again

2014-10-20 Thread Morten Johan Sørvig
> On 20 Oct 2014, at 15:04, Saether Jan-Arve > wrote: > > Change: https://codereview.qt-project.org/97600 > (comment from 97600) // On OS X the windows might get positioned exactly on top of each other // that means no repaint for the bottom window will ever occur And why did this start to fa

Re: [Development] Qt5*Config.cmake files: _qt5_*_check_file_exists macros and plugins

2014-10-20 Thread Rex Dieter
Lisandro Damián Nicanor Pérez Meyer wrote: > On Friday 17 October 2014 17:02:04 Kevin Kofler wrote: >> Hi, > > tl;dr; We have found the same problem in Debian, but steveire told us that > the idea of those CMake files is to provide a way to find the plugins if a > developer is doing it's own inst

Re: [Development] CI broken again

2014-10-20 Thread Saether Jan-Arve
Change: https://codereview.qt-project.org/97600 Fra: development-bounces+jan-arve.saether=theqtcompany@qt-project.org på vegne av Sarajärvi Tony Sendt: 20. oktober 2014 09:37 Til: BogDan; Qt Development Group Emne: Re: [Development] CI broken again That

Re: [Development] QSettings refactor updates

2014-10-20 Thread Thiago Macieira
On Monday 20 October 2014 14:26:17 Simon Hausmann wrote: > > Should be completely transparent and orthogonal. The data types supported > > by the front-end should not be affected by whatever it uses for caching. > Ah, so that means custom types (types other than what QJson supports) will > be conve

Re: [Development] QSettings refactor updates

2014-10-20 Thread Simon Hausmann
On Monday 20. October 2014 20.11.20 Thiago Macieira wrote: > On Monday 20 October 2014 08:36:17 Simon Hausmann wrote: > > On Monday 20. October 2014 07.06.00 Thiago Macieira wrote: > > > On Sunday 19 October 2014 22:39:42 Branislav Katreniak wrote: > > > > > Cache format: binary json > > > > > > >

Re: [Development] QSettings refactor updates

2014-10-20 Thread Thiago Macieira
On Monday 20 October 2014 08:36:17 Simon Hausmann wrote: > On Monday 20. October 2014 07.06.00 Thiago Macieira wrote: > > On Sunday 19 October 2014 22:39:42 Branislav Katreniak wrote: > > > > Cache format: binary json > > > > > > You use json internally as cache. What is the motivation to introduc

Re: [Development] QtRemoteObjects (was Replicant)

2014-10-20 Thread Branislav Katreniak
What about removing the hard dependency of type safe replicas on the rep language and rep compiler? Can we extend moc compiler? When we write the server objects, we already have the QObject with all the signals and slots visible for moc. Moc could generate the type safe replica objects based on th

Re: [Development] QtRemoteObjects (was Replicant)

2014-10-20 Thread Simon Hausmann
On Monday 20. October 2014 10.38.26 Stottlemyer, Brett wrote: > On Monday, October 20, 2014 2:32 AM Simon Hausmann wrote: > > So what would a .proto file look like for a Q_OBJECT? That's not evident > > to me > yet. > > > However a .proto file could be written (manually) that describes the > > mes

Re: [Development] QtRemoteObjects (was Replicant)

2014-10-20 Thread Stottlemyer, Brett (B.S.)
On Monday, October 20, 2014 2:32 AM Simon Hausmann wrote: > So what would a .proto file look like for a Q_OBJECT? That's not evident to > me yet. > > However a .proto file could be written (manually) that describes the messages > needed to allow calling into QObjects. Basically a schema for what

Re: [Development] CI broken again

2014-10-20 Thread Sarajärvi Tony
That QtDeclarative 5.4 needs our attention. As of now we have no idea why it has begun failing. We can't recall changing anything on the macs except updating xcode -Tony From: BogDan [mailto:bog_dan...@yahoo.com] Sent: 17. lokakuuta 2014 16:03 To: Sarajärvi Tony; Qt Development Group Subject: R

Re: [Development] Compiler warnings

2014-10-20 Thread Ziller Eike
On Oct 17, 2014, at 7:26 PM, Mathias Hasselmann wrote: > > > Am 17.10.2014 um 18:31 schrieb Thiago Macieira: >> On Friday 17 October 2014 13:06:39 Milian Wolff wrote: >>> enum Foo { >>> Bar = 1, Baz = 2 >>> }; >>> >>> Foo foo = static_cast(3); >>> >>> Now what do you do without a default cl