Hi all, There is a problem when an application is calling a process which takes a long time, and doesn't involve screen activity or user input processing. (aka the code does't return to the HVM loop for a longer time). Like a dbSetFilter() or dbPack() call on a large table, or indexing without a progress callback.
While Harbour is doing the processing, the GTWVT window doesn't get refreshed, so the content is pure blank if minimizing and restoring the window. It also doesn't react to any system inputs. Maybe other GTs are affected too. I think we should have an idle call processing ability built into the GTs. This call may be called by some generic idle processing functions in Harbour, and finally this function would need to be called regularly by these time-consuming Harbour functions. Or maybe something completely different, but the goal is given. Opinions, suggestion? Brgds, Viktor _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
