On Mon, 03 Jan 2011 19:36:05 +0100, Robert Clipsham
<[email protected]> wrote:
On 03/01/11 18:15, Nick Sabalausky wrote:
The typical problem with things that look native but aren't technically
native is that there's almost inevitably things that don't work right.
For
instance, they may ignore the system color scheme, they may fail to work
with tools that inspect/manipulate other app's controls, they may not
behave
correctly outside of the most common use-cases, they may ignore
system-wide
skin settings (such things do, and should, exist for Windows), and I've
even
seen ones that actually go and emulate the wrong system style (For
instance,
Chrome/Iron's dialog windows look like Aero...but I'm on XP, and if I
were
on Win7 I'd be using the Classic theme anyway. Very very sloppy).
If it turns out that Qt's self-drawn controls doesn't have any of those
issues, then I agree there's no problem at all. I'd also be incredibly
impressed.
I've not seen any such issues on Windows/Linux/OS X, could be others
though *shrugg*. I'm pretty sure Qt uses the native API as a backend
anyway, I remember reading an article about them transitioning from
carbon to cocoa on OS X (the native APIs) on their blog at some point,
I'd be surprised if they didn't do the same for Windows.
Look:
http://labs.qt.nokia.com/2007/08/09/qt-invaded-by-aliens-the-end-of-all-flicker/
Qt doesn't build up a virtual api beside from winapi. Yes qt have to use
system api, but they want the small amount of them.
Because they have to ask the system how is your state, and i want you to
do that and that.
There are always some control they have native handler - i believe it is
shown in the video. Like the MenuBar Qt Menubar in Windows feels like a
Windows Menubar and on a Mac i believe it would feel like an Mac Menubar.
But there are some components in Qt which are better than the native one
like Qt Calendar it is beauty and have more function as the windows one- I
want exchange them xd
