Re: [Development] Qt 5 Mac losing window focus/active state

Hi, On Sep 11, 2012, at 9:59 PM, ext Stephen Chu wrote: > I am having a lot of issue with window active state (or focus?) on Mac. > In addition to losing focus after clicking a combo box, I ran into this one: > > > Basically after clicking

Re: [Development] Plugin loading issue on Mac OS X

On Jul 10, 2012, at 11:39 AM, ext Thiago Macieira wrote: > Are you sure that some plugins are only built in debug mode? That sounds > really weird. They should be built however they wish, but there should be at > least one file without the "_debug" image suffix. I found it strange as well. The p

[Development] Plugin loading issue on Mac OS X

Hi, Due to an autotest regression, I recently discovered that if plugins built with both release and debug version (-debug-and-release) are loaded, it will cause warning messages like: objc[26809]: Class QNSListener is implemented in both /Users/jjgod/qtbase/plugins/bearer/libqcorewlanbearer.

Re: [Development] Retina display

On Jun 13, 2012, at 3:35 PM, ext Jason Dictos wrote: > Oh wait, I see, so I moved it out of the bundle and ran Designer, and wow > looks great. > > I wonder how I can enable this mode in my application, since I'm using my own > bundle. Try adding: NSPrincipalClass NSApplication to the Info.pl

Re: [Development] [QT5] System fonts are not loaded in ubuntu 12.04

On May 14, 2012, at 10:15 AM, ext Loaden wrote: > The issue still exist. > In Ubuntu 12.04, the 'fontconfig' package installed by default. > loaden@qpsoft:~$ sudo apt-get install fontconfig > Reading package lists... Done > Building dependency tree > Reading state information... Done > fontc

Re: [Development] [QT5] System fonts are not loaded in ubuntu 12.04

On May 5, 2012, at 8:16 AM, ext liang jian wrote: >I have built Qt 5 in ubuntu 12.04, The simplified chinese > character can't be displayed. >I found that in QBaseFontDatabase::popluateFontDatabase() the font > path returned by fontDir() is "/mnt/sda8/liang/qt5/qtbase/lib/fonts/" > which is

[Development] Platform specific font matching in QPA

Hi folks, Today I want to bring up the topic on font matching in QPA. In my opinion it's broken for certain very useful cases and beyond simple fix. The first case is what Thiago brought up here [1]. Matching for aliases like "serif" and "monospace" is a commonly used feature in both desktop ap

Re: [Development] Removal of xlib plugin - a possible disaster.

On Mar 20, 2012, at 1:58 PM, ext Thiago Macieira wrote: >> Font matching in QPA is pretty much broken for these cases, I have a WIP >> patch to fix this: http://codereview.qt-project.org/20590 but it's not >> complete yet. You can of course try and see if it helps. > > Didn't see much of a differe

Re: [Development] Removal of xlib plugin - a possible disaster.

Hi Thiago, On Mar 20, 2012, at 8:31 AM, ext Thiago Macieira wrote: > That's the point: I don't want it to convert. I want to configure my system > to > use "Monospace" and let fontconfig decide which font that is. If I were to > change my fontconfig settings, the applications should change too.

Re: [Development] Removal of xlib plugin - a possible disaster.

Hi Thiago, On Mar 19, 2012, at 9:50 PM, ext Thiago Macieira wrote: >> That started happening sometime between 17 Feb. and now, FWIW; I >> suspect it's quite recent. At least the default font choice has >> gotten better. > > It's a horrible choice now. Creator uses by default the font "Monospace"

Re: [Development] Something is wrong in QFontEngineFT::loadGlyph

Hi Mark, On Feb 14, 2012, at 12:03 AM, ext Mark wrote: > While using Qt's elidedText function > http://developer.qt.nokia.com/doc/qt-4.8/qfontmetricsf.html#elidedText i > noticed the function was dog slow. For just 1000 entries (each 250 chars) > eliding them to 200px took about 190ms on window

Re: [Development] Use make before you push and stage

Hi, On Jan 25, 2012, at 9:55 AM, ext lars.kn...@nokia.com wrote: >> Yesterday was a bit of a frustrating day. I had to stage a simple >> .pro-file change of mine 8, eight, times before it finally went in. All >> of the breakages throughout the day where build breakages. Many of them >> were in the