Hello
Przemyslaw Czerpak-2 wrote: > > I'm afriad it's not possible. > Inkey() release CPU only when called with some timeout parameter or 0. > Adding CPU release code to each inkey() call can kill the performance > of some which makes sth like: > > while !eof() and inkey()!=K_ESC > [...] > dbskip() > enddo > > because on some system the minimal interval can be quite huge, f.e. > 10 milliseconds so in the above example skipping throw 1000 records > will took 10 seconds only for process sleeping. > I understand. > I still haven't working environment with new Qt4.5. > In my systems the Qt is important part of the whole system > and I cannot easy add new Qt library without interactions > with existing binaries so I cannot make any tests yet with > final application. So far I only made some basic compilation > tests with Qt4.4 I have in my system but I cannot run final > binaries due to GPF. > I do not know what is the exact problem but the main difference > between inkey() and inkey(0.1) is activating idle proc. One of > jobs made by idle proc is exacting garbage collector. Maybe you > can reach the effect you are looking for by direct executing > hb_gcAll( .f. ). > It is enough that QT is a very important part of your developments. So we cn hope positively once you will setup the env properly, GTQTC ++ front is going to be accelerated. Take your own time. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/SF.net-SVN%3A-harbour-project%3A-10932--trunk-harbour-tp23226134p23257058.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
