Re: [Development] Image and PreserveAspectCrop

> On 02 Aug 2016, at 18:03, Albert Astals Cid > wrote: > > On Tue, Aug 2, 2016 at 1:56 PM, Gunnar Sletta wrote: >> Hi, >> >> I think the most sensible solution is to handle this inside the image >> provder. When I've seen this problem

Re: [Development] Image and PreserveAspectCrop

On 2 August 2016 at 19:56, Gunnar Sletta wrote: > Hi, > > I think the most sensible solution is to handle this inside the image > provder. When I've seen this problem previously, it has was solved using a > custom image provider for local files, but as you say, when the

Re: [Development] Programs crashing left and right in the CI

On terça-feira, 2 de agosto de 2016 17:17:59 PDT Thiago Macieira wrote: > Ok, this is the first time that the compiler itself has crashed. Can you > retry the integration with the exact same commits in the same order? If it > crashes again compiling .obj/debug-iphoneos/qjsonparser.o, it's a

Re: [Development] Programs crashing left and right in the CI

On quarta-feira, 3 de agosto de 2016 01:05:00 PDT Giuseppe D'Angelo wrote: > On Thu, Jul 28, 2016 at 10:06 AM, Michal Klocek wrote: > > It seems to happen in different modules (here qttools and qtlocation) > > and in different branches (here dev and 5.6), but on mac/clang and

Re: [Development] Programs crashing left and right in the CI

On Thu, Jul 28, 2016 at 10:06 AM, Michal Klocek wrote: > > It seems to happen in different modules (here qttools and qtlocation) > and in different branches (here dev and 5.6), but on mac/clang and during > moc compilation. Now I've got an ICE:

Re: [Development] QtCon rooms for QCS

On terça-feira, 2 de agosto de 2016 17:50:24 PDT Gabriel de Dietrich wrote: > Hi Thiago, > > I’m replying on Morten’s behalf since that session was initially suggested > by me and Jake. > It’s going to be a QtCS session. We need to discuss some recurring issues > related to rendering on Mac.

Re: [Development] QtCon rooms for QCS

Hi Thiago, I’m replying on Morten’s behalf since that session was initially suggested by me and Jake. It’s going to be a QtCS session. We need to discuss some recurring issues related to rendering on Mac. Other related topics may arise, but no formal presentation AFAIK. Best regards, Dr.

Re: [Development] QtCon rooms for QCS

On sexta-feira, 29 de julho de 2016 09:57:11 PDT Morten Sorvig wrote: > Is there a sharp division between QtCon and QCS? > > I was told I should register my QCS topics for QtCon, which I have. If > others have done the same then rooms may already have been reserved. (An > extra free room for the

Re: [Development] Image and PreserveAspectCrop

On Tue, Aug 2, 2016 at 1:56 PM, Gunnar Sletta wrote: > Hi, > > I think the most sensible solution is to handle this inside the image > provder. When I've seen this problem previously, it has was solved using a > custom image provider for local files, but as you say, when the

Re: [Development] Image and PreserveAspectCrop

> On 02 Aug 2016, at 13:56, Gunnar Sletta wrote: > > A bit unfortunate that we have to add a V2 version of the image provider, > though. Would be nice if we could extend what is already there somehow. > However you end up solving it, it needs to be a bit more flexible than

Re: [Development] Behavior of mapToGlobal function when application is not the one active.

Den 02-08-2016 kl. 14:22 skrev NIkolai Marchenko: A little bit of context: I am trying to organize getting interface positions/sizes out of an application via RPC interface. To do this I have inserted grpc server code into a GUI app and grpc client into another, testing application.

[Development] Behavior of mapToGlobal function when application is not the one active.

A little bit of context: I am trying to organize getting interface positions/sizes out of an application via RPC interface. To do this I have inserted grpc server code into a GUI app and grpc client into another, testing application. Essentially, when the client app sends a signal, the main app

Re: [Development] Image and PreserveAspectCrop

Hi, I think the most sensible solution is to handle this inside the image provder. When I've seen this problem previously, it has was solved using a custom image provider for local files, but as you say, when the resources are scattered across the local and network alike, then you want the

Re: [Development] Image and PreserveAspectCrop

Ping anyone? On Mon, Jul 18, 2016 at 10:24 AM, Albert Astals Cid wrote: > There is a problem when trying to optimally[*] show an Image with > PreserveAspectCrop fillMode. > [*]optimally => as best looking as possible while using as litte > memory as possible > > You