On Fri, 12 Nov 2010 20:52:03 +0200 Sivan Greenberg <si...@omniqueue.com> wrote:
> On Fri, Nov 12, 2010 at 8:41 PM, Bernd Stramm > <bernd.str...@gmail.com> wrote: > > Does this address whether a widget is obscured by something else? > > > > In some windowing systems large numbers of windows are visible, or > > partially visible. In other windowing systems only a small number > > (like say, one) are visible. The windows don't know this in Qt. > > True, so it would be useful to know how far I was minimized, and do a > ratio of this and the size of the display, then you could know if it > is still worth redrawing, this could be a nice optimization direction > and still maintain highly responsive UX. Right, and it can be more than just the painting. In some cases the application may have to do significant work to know what it is redrawing. > > > More generally it would be really nice if my application would know > > what kind of device it is running on, *at run time*. And what kind > > of display is used. How large are things on the display. > > > > If those things are unknown (as I think they are at present), it is > > not practical to write applications once and have them work on > > different types of devices. > > True, I think I saw this is being worked on , but otherwise there are > nice and friendly people in #qt-labs you talk to, possibly file a > feature request, patch etc etc :) > > > > > And no, tons of #ifdefs don't count as "write once" :) > > Known, and is already somewhat described here: > http://wiki.meego.com/Qt_across_(Maemo-)MeeGo_%26_Symbian#Collecting_Porting_Experience > > -Sivan -- Bernd Stramm bernd.str...@gmail.com _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
