On 17/12/10 7:09 AM, "Alhola Kate (Nokia-FNDC/Helsinki)"
<[email protected]> wrote:

>
>>________________________________________
>>From: [email protected] [[email protected]] on
>>behalf of ext [email protected] >[[email protected]]
>>Sent: Thursday, December 16, 2010 8:34 PM
>>To: [email protected]
>>Subject: Re: [MeeGo-dev] Writing code in Qt for MeeGo platform
>>
>>On 17/12/10 2:38 AM, "ext Bernd Stramm" <[email protected]> wrote:
>>
>>>On Wed, 15 Dec 2010 20:30:43 +0100
>>>Thiago Macieira <[email protected]> wrote:
>>>
>>>> On Wednesday, 15 de December de 2010 14:19:00 Bernd Stramm wrote:
>>>> > This seems to be the current situation, applications take a wild
>>>> > guess to decide what they are running on.
>>>> >
>>>> > This means different applications take different guesses.
>>>> >
>>>> > It would be really really nice if there was a better way. You know,
>>>> > something reliable and/or organized.
>>>>
>>>> I agree. Tell me which information will help you make the right
>>>> decision.
>>>
>>>It would help to know the physical size of the display.
>>>
>>>Perhaps in millimeters, or perhaps just as a category.
>>>
>>>Something like "theater-size", "desktop-size", "pocket-size",
>>>"fingernail-size". Each of these different types would need
>>>different UI designs.
>>>
>>>And similar to what Kate wrote, it could help to know characteristics
>>>of the available input device(s) and pointing devices.
>>
>>Sounds like you should look at QtMobility's QSystemInfo classes. :)
>>http://doc.qt.nokia.com/qtmobility-1.1.0/qtsysteminfo.html
>
>There is good information about input device to determine is the device
>touch screen and even multitouch.
>enum     InputMethod { Keys, Keypad, Keyboard, SingleTouch, MultiTouch,
>Mouse }
>
>Funny thing was that displayinfo, there was only color depth. Not even
>resolution or physical size.

Coming in 1.2
http://qt.gitorious.org/qt-mobility/qt-mobility/blobs/3175868881f409a119a26
38a4a757a93136ac72b/src/systeminfo/qsystemdisplayinfo.h

>
>Kate
>
>>But you might have to wait for QtMobility 1.2 which will bring support
>>for
>>meego...
>
>Hopefully you add resolition and size there.

Indeed. In the meantime, one could use:

QDesktopWidget.screen(0).
To get the QPaintDevice stuff for the desktop widget.

Not very intuitive, but it's there.


--
Lorn Potter
Senior Software Engineer, Nokia, Qt Development Frameworks




_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to