I know that is quite silent about the Qt Windows CE port is the past, but be asured Qt for Windows CE has not been forgotten at all.
A lot of Windows CE bugs and issues have been fixed for Qt 4.6.
Some people might have noticed that a short while ago Windows Mobile 6.5 was released. Unfortunately this was a little bit to late to fully support officially Windows Mobile 6.5 in Qt 4.6.
But the good news are that we will have some support for Windows Mobile 6.5 in Qt 4.6 and will fully support it for Qt 4.7.
Qt 4.6 will contain mkspecs for Windows Mobile 6.5 and it also will contain support for the new style. This means that Qt 4.6 applications look native on Windows Mobile 6.5.
It is also worth mentioning that the new animation framework is fully supported on Windows CE, which allows some really nice effects. This means that Qt is really able to leverage the Windows Mobile experience to new heights or in more appropriate words (I am not a marketing guy.): Qt can help you to deliver astonishing applications for Windows Mobile.
Since screenshots tell more than words, here are some:
The famous Text Edit.
A styled Tab Widget.
The new List View highlight.
Commenting for this post has ended.
I really wish Qt supported ClearType on Windows CE. Other than that, great work!
Finally, guys. We really needed to know that everything is cool with WinMo ;)
@cartman: The fonts only look ugly in the emulator, because it runs on a Monitor with only 96 DPI. You may have noticed that real devices run with a lot higher DPI count. This is why Fonts on modern embedded devices can show crips fonts withour hacks like ClearType (actually, those "hacks" were only introduced to remedy low-DPI screens.
I am using Qt4.6 beta to dev on M8, a mobile which OS is basing on CE6.
What bother me most is the graphics rendering performance and the text rendering effect.
The design flaw of using float numbers in QGraphicsView has a huge detrimental affect for WM since most devices will not support Qt's heavy computation for graphics rendering.
An example, trying to do finger-scrolling with a QScrollArea embedded in a QGraphicsView results in 1-2 FPS response rate compared to native speeds > 30FPS as of Qt 4.5.
QGraphicsView using floats is not a design flaw. It's a vector-based graphic canvas, and its coordinate system cannot be bound by pixels.
i can't login in forum so here it goes another try....is there a way to use a bluetooth gps instead of embedded gps with qtmobility library?
all the best and sorry for posting here my question