On Fri, Dec 21, 2012 at 9:54 AM, Bache-Wiig Jens
<[email protected]> wrote:
>> Hi Jens,
>>
>> I find the Qt decision in this area a bit strange - to put it mildly.
>> Text should imho look good at it's defaults (that's called strong
>> defaults). Zooming is a nice feature in QML, but remember, the
>> majority of apps are probably not even going to have zooming support
>> so perhaps it's wise to make "renderType: Text.NativeRendering" the
>> default and let the user enable the distance field based rendering
>> when they need it.
>
> Sorry, don't misunderstand. What you are seeing is _not_ how the fonts are 
> supposed to look. Do file a bug against it.
> As far as I can tell, hinting looks incorrect in your picture. This is how it 
> looks on mac: http://i.imgur.com/rEq9x.png
> It is clearly more readable. I was suggesting the native text as a workaround.
>
> Having said that, I was also violently opposing this change when it first 
> came up. But after having seen some of the benefits of distance field when it 
> comes to animating and perhaps more importantly sub-pixel butter-smooth list 
> scrolling, I am mostly ok with it. Notice that even Microsoft does the exact 
> same thing by default:
> http://blogs.msdn.com/b/text/archive/2009/08/24/wpf-4-0-text-stack-improvements.aspx
>
> They added a hint for "Display optimised text" so you could revert to the old 
> behaviour, but by default they give you scene graph optimised text rendering 
> as we do. I have already changed all the upcoming Qt Quick desktop controls 
> in such as Label, Button, TextArea and TextField to use the native font 
> rendering by default so in practice the problem will be less of an issue.
>
>> Note: the renderType property is not documented:
>> http://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-text.html
>
> Indeed! Thanks for pointing that out.
>
> Regards,
> Jens
>
>
>> Cheers,
>> Mark
>>>
>>> On Dec 20, 2012, at 10:15 PM, Mark <[email protected]> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm just running the default examples, but the font looks.. Way too
>>>> blurry to me! How is that possible and how can i fix that? Or is it a
>>>> bug?
>>>>
>>>> A screenshot: http://ompldr.org/vZ3JyaQ/qtquick2_blurry_font.png
>>>> The example: "QML Examples - Text"
>>>>
>>>> But i see this in every single place that uses text in QML.
>>>>
>>>> Hardware spec:
>>>> AMD CPU (1100XT)
>>>> AMD 6870 GPU
>>>> Latest catalyst
>>>> Windows 7 fully updated.
>>>> _______________________________________________
>>>> Interest mailing list
>>>> [email protected]
>>>> http://lists.qt-project.org/mailman/listinfo/interest
>>>
>

<please do bottom posting>

Reported the issue: https://bugreports.qt-project.org/browse/QTBUG-28782
Also you say that you changed to NativeRendering in the desktop
components.. I don't think that's a good idea since then it will be
very likely that one app that uses the components will have two
different fonts. Native rendered fonts for the components and the Qt
default for the ones that aren't in your component set. That's not
ideal - far from it.

It would be better to:
- either optimize displacement stuff to look good enough and use that everywhere
- use native rendering everywhere and let the user decide when to change.

Another option would be a command line argument. For example something
like this:
qmlapp myapp.qml -fontrendering native

Where qmlapp is the executable to run a qml file.

Cheers,
Mark
_______________________________________________
Interest mailing list
[email protected]
http://lists.qt-project.org/mailman/listinfo/interest

Reply via email to