Hello Przemek <<< It's problem with GUI GTs: GTWVT and GTXWC. In the most of GUI system application has to redraw its screen contents. Probaly in each OS some hacks exists which alows to move this job to OS. F.e. on some X-Window systems it's possible to set bitamp as window background and it will be redrawn automatically by window manager so GT only have to update this bitamp on output. Probably sth like that exists also for MS-Windows. But because it will be hack which can cause troubles in portability I left it for the future. >>>
Exactly this I wanted for GTWVG but could not find a better way. <<< BTW I do not like that GTWVG draws into two areas: directly to window and to internal bitamp. IMHO it will be much easier to update only internal bitmap and restore the screen from this bitamp or if possible to make it window background as I wrote above. >>> As I said I could not find other ways to achieve this. May be my knowledge in WinAPI was very limited then. Can you please give me a clue how this can be changed. A line or two of code will be enough to move into that direction. <<< Please remember that we also need common system for inspecting incomming events. >>> For this point in mind I just suggested HB_GTE_INKEY but still has not been accepted by the group. <<< So far I'm using my own library which uses select() for it (in *nixes select() can watch for any type of handles not only for sockets like in MS-Win). Anyhow it will be very nice to have a solution on Harbour level which will work also in MS-Windows and as I said I plan to work on it. >>> For sure I will wait for it to happen. Regards Pritpal Bedi -- View this message in context: http://www.nabble.com/Window-updates-vs.-long-Harbour-processes-tp17787182p17790192.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
