Re: [Development] CI for Qt WebKit

> Lähettäjä: Development > > käyttäjän puolestaHeikkinen Jani > Lähetetty: 12. huhtikuuta 2016 9:46 > Vastaanottaja: Thiago Macieira; development@qt-project.org > Aihe: Re: [Development] CI for Qt WebKit > >>>That's exactly the time that they should

Re: [Development] CI for Qt WebKit

>>That's exactly the time that they should be in the way... We may break those >>modules temporarily, but not leave them broken at the time of the release. I disagree. If module is removed (obsolete in .gitmodules) that cannot delay the release: It is just insane. if there is some reason(s) for t

Re: [Development] CI for Qt WebKit

On segunda-feira, 11 de abril de 2016 20:34:44 PDT Knoll Lars wrote: > The reason is that they should not be in the way to getting our releases > out. That's exactly the time that they should be in the way... We may break those modules temporarily, but not leave them broken at the time of the rel

[Development] CI for Qt WebKit

Hi, we’re planning on doing a slight adjustments to how Qt WebKit and other unsupported modules are CI tested for 5.7 and onwards. Basically, they will not be tested as part of qt5.git integrations anymore and thus won’t block releases. But they will stay CI controlled and will be compile tes

Re: [Development] QColor and HSL's hue

On 2016-04-09 09:02, Curtis Mitch wrote: > Is there any technical reason (besides compatibility) why QColor::hslHueF() > can't return a value between 0 and 1? > > If the colour being represented by QColour is black, QColor::hslHueF() will > return -1: I think there is a misunderstanding here...

Re: [Development] Qt Keyboard Shortcuts broken in Qt 5.6 (since 4.8 at least). Reproducible test case included.

On Mon, Apr 11, 2016, at 12:20 AM, Ziller Eike wrote: > This bug report is more about that you could not assign such a shortcut in Qt > Creator to begin with. > That is a different problematic though. To check if Qt (Creator) in principle > is able to handle a certain shortcut, > you should open

Re: [Development] Qt 5.7.0 beta snapshot available - gtk 3 and packaging on RHEL 6

On Monday 11 April 2016 16:50:18 Frederik Gladhorn wrote: > Hello all, [snip] > For Qt 5.7, the options seem to be: > 1.) ignore the problem and ship Qt packages in the installer without gtk > theme 2.) revert the patch to have the gtk2 theme for one release longer > and only have gtk3 with Qt 5.8

Re: [Development] MSVC2012 in CI

On Monday, April 11, 2016 06:03:18 PM Frederik Gladhorn wrote: > On Thursday, April 07, 2016 02:41:03 PM Friedemann Kleint wrote: > > Hi, > > > > >I'd love to remove it, but it's blocked by > > > > https://bugreports.qt.io/browse/QTBUG-51934 > > > > >We cannot just remove test coverage without

Re: [Development] MSVC2012 in CI

On Thursday, April 07, 2016 02:41:03 PM Friedemann Kleint wrote: > Hi, > > >I'd love to remove it, but it's blocked by > > https://bugreports.qt.io/browse/QTBUG-51934 > > >We cannot just remove test coverage without testing some of the > > features on more modern platforms. > > We blackliste

Re: [Development] Qt 5.7.0 beta snapshot available - gtk 3 and packaging on RHEL 6

Hello all, for Linux packaging we currently use a Red Hat 6 which seemed like a good compromise at the time. I have been pondering https://bugreports.qt.io/browse/QTBUG-52259 for a while and don't seem to reach a conclusion. We had a contribution porting our gtk 2 theme to gtk 3 (thanks Dmitry!

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

Hi ekke, I have tried. Image item will just ignore the devicePixelRatio set in QImage. Similar report: [QTBUG-38127] devicePixelRatio not supported by QQmlImageProvider - Qt Bug Tracker On 11 April 2016 at 20:47, ekke wrote: > perhaps devicePixelR

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

perhaps devicePixelRatio is 3.0 - this would have the effect to get 170.666 http://doc.qt.io/qt-5/qimage.html#setDevicePixelRatio ekke Am 11.04.16 um 14:36 schrieb Federico Buti: > Hi Ben, > > I've solved the issue by multiplying width/height to > qApp->devicePixelRatio(). That should be 3 on iPho

[Development] Qt 5.7.0 beta snapshot available

Hi all, We have new Qt 5.7.0 beta snapshot available Windows: http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/407/ Linux: http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/389/ Src:http://download.qt.io/snapshots/qt/5.7/5.7.0-beta/latest_src/ (Under mirroring) Mac packages are still miss

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

Hi Ben, I've solved the issue by multiplying width/height to qApp->devicePixelRatio(). That should be 3 on iPhone 6 and should provide the correct result. I'm not sure if that's a bug or it is intended behaviour and I actually didn't investigate the issue a lot since I was just testing stuff. Hop

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

On 11 April 2016 at 20:19, ekke wrote: > Am 11.04.16 um 14:07 schrieb Ben Lau: > > > On 11 April 2016 at 19:59, ekke wrote: > >> Am 11.04.16 um 12:38 schrieb Ben Lau: >> >> Hi, >> >> I am writing an image provider that read all the images to memory at >> startup. And I found that the behaviour i

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

Am 11.04.16 um 14:07 schrieb Ben Lau: > > On 11 April 2016 at 19:59, ekke > wrote: > > Am 11.04.16 um 12:38 schrieb Ben Lau: >> Hi, >> >> I am writing an image provider that read all the images to memory >> at startup. And I found that the behaviour is

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

On 11 April 2016 at 19:59, ekke wrote: > Am 11.04.16 um 12:38 schrieb Ben Lau: > > Hi, > > I am writing an image provider that read all the images to memory at > startup. And I found that the behaviour is different from 5.5.1 to 5.6 in > iOS. Seems that it is undocumented. I wonder is it an expec

Re: [Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

Am 11.04.16 um 12:38 schrieb Ben Lau: > Hi, > > I am writing an image provider that read all the images to memory at > startup. And I found that the behaviour is different from 5.5.1 to 5.6 > in iOS. Seems that it is undocumented. I wonder is it an expected > behaviour or a bug? > > That is the exa

[Development] The behaviour of Image / image provider are different from 5.5.1 to 5.6 in iOS

Hi, I am writing an image provider that read all the images to memory at startup. And I found that the behaviour is different from 5.5.1 to 5.6 in iOS. Seems that it is undocumented. I wonder is it an expected behaviour or a bug? That is the example project: https://github.com/benlau/quickcross/t

Re: [Development] Wiki in read only state for acute fixes

The wiki is now returning to normal, as soon as the DNS changes propagate everywhere. Thanks for your patience! From: Development [mailto:development-bounces+tero.kojo=theqtcompany@qt-project.org] On Behalf Of Kojo Tero Sent: maanantaina 11. huhtikuuta 2016 11.14 To: development@qt-project

[Development] Wiki in read only state for acute fixes

Hello, The Qt Wiki is going to read-only state due to a need to move the service immediately from its current server to a more stable set-up. As you may have noticed, we have had recurring issues with the web services, the past weekend was particularly bad, so these changes are being done immed

Re: [Development] Qt Keyboard Shortcuts broken in Qt 5.6 (since 4.8 at least). Reproducible test case included.

> On Apr 10, 2016, at 7:22 AM, jaso...@mail-central.com wrote: > > Use of Qt Keyboard shortcuts has been broken in Qt for years. > > There are lots of bugs about it in Qt and KDE projects. > > This one looks close to what I'm seeing, > > Can't assign keyboard shortcut with Meta modifiers