[Interest] How to remove some features from QtWebKit.

2015-04-27 Thread Kim Min-chul
Hi I would like to get some advices or suggestions for removing some features from qtwebkit. I am using qtwebkit(qt 5.2.1). I think that it spends too much memory. The reason is why I want to remove some features like Video and Audio. Of course it will be good for removing other features in order

Re: [Interest] iOS-Dev: XCode 6.3.1 Crashes with QtCreator Created Projects

2015-04-27 Thread Hamish Moffatt
On 28/04/15 14:05, Robert Iakobashvili wrote: > On Tue, Apr 28, 2015 at 3:48 AM, Hamish Moffatt > wrote: >> Just downgrade to Xcode 6.2. It works fine. Available in the Apple Developer >> Member Center. >> >> > When you need to develop for the recent iOS-8.3 and > your devices are with iOS-8.3, Xc

Re: [Interest] iOS-Dev: XCode 6.3.1 Crashes with QtCreator Created Projects

2015-04-27 Thread Robert Iakobashvili
On Tue, Apr 28, 2015 at 3:48 AM, Hamish Moffatt wrote: > On 28/04/15 01:02, Eddie Sutton wrote: >> >> My crash stack trace matches the one you attached to the bug report: >> >> ASSERTION FAILURE in >> /SourceCache/DVTFrameworks/DVTFrameworks-7703/DVTKit/CustomUI/FileIcons/DVTFileIconCreator.m:198

Re: [Interest] iOS-Dev: XCode 6.3.1 Crashes with QtCreator Created Projects

2015-04-27 Thread Hamish Moffatt
On 28/04/15 01:02, Eddie Sutton wrote: > My crash stack trace matches the one you attached to the bug report: > > ASSERTION FAILURE in > /SourceCache/DVTFrameworks/DVTFrameworks-7703/DVTKit/CustomUI/FileIcons/DVTFileIconCreator.m:198 > > https://bugreports.qt.io/browse/QTCREATORBUG-14339 > > I nee

Re: [Interest] iOS-Dev: XCode 6.3.1 Crashes with QtCreator Created Projects

2015-04-27 Thread Eddie Sutton
My crash stack trace matches the one you attached to the bug report: ASSERTION FAILURE in /SourceCache/DVTFrameworks/DVTFrameworks-7703/DVTKit/CustomUI/FileIcons/DVTFileIconCreator.m:198 https://bugreports.qt.io/browse/QTCREATORBUG-14339 I need Xcode to archive, validate archive, and upload to t

[Interest] Bad application rendering on Remote Desktop

2015-04-27 Thread Calogero Mauceri
Hi all, switching my application from using QGLWidget to the new QOpenGLWidget I noticed a very weird problem when using the application through Remote Desktop on Windows. The whole application is fully black, it is not properly rendered, not only the QOpenGLWidget, but also the other widgets

Re: [Interest] [Development] Sound routing

2015-04-27 Thread Federico Buti
On 27 April 2015 at 13:07, Lopes Yoann wrote: > > On 27 Apr 2015, at 12:23, Federico Buti wrote: > > it seems to me that sound is automagically routed to the outer speaker, > not the dialling speaker. The outer speaker should never play sound in my > app, i.e. with a tablet device I'm limited

Re: [Interest] [Development] Sound routing

2015-04-27 Thread Lopes Yoann
On 27 Apr 2015, at 12:23, Federico Buti mailto:bacaro...@gmail.com>> wrote: it seems to me that sound is automagically routed to the outer speaker, not the dialling speaker. The outer speaker should never play sound in my app, i.e. with a tablet device I'm limited to using just earphones. Th

Re: [Interest] [Development] Sound routing

2015-04-27 Thread Federico Buti
Hi, it seems to me that sound is automagically routed to the outer speaker, not the dialling speaker. The outer speaker should never play sound in my app, i.e. with a tablet device I'm limited to using just earphones. --- Federico Buti On 27 April 2015 at 11:43, Lopes Yoann wrote: > > On 27

Re: [Interest] [Development] Sound routing

2015-04-27 Thread Lopes Yoann
On 27 Apr 2015, at 11:15, Federico Buti mailto:bacaro...@gmail.com>> wrote: 2) The app requires a specific sound routing: if the earphones are plugged, sound should be hear only on them. If earphones are not available, sound should be routed to the phone speaker (for smartphone devices). Such

[Interest] Sound routing

2015-04-27 Thread Federico Buti
Hi list(s), I'm in the early development stage of a mobile app and I'm currently trying to figure out which native API are mapped to Qt and which are not. Writing native code is not a problem but I would avoid wasting time for reinventing the wheel. :) Among the other things I'm concerned with th