Threads can be a solution if all Windows platforms
(including all WinCE platforms) support it, but still
only for Windows.
We should also think about GTXWC, and maybe even
future GTs, so I think we need to look for a solution
which works without threads, and works above al GTs.
We happen to have a function called hb_idleState(),
which _may_ be used for such purpose.
Brgds,
Viktor
On 2008.06.11., at 23:36, Randy Portnoff wrote:
Hi Pritpal,
I don't think a timer (on the current thread) will work. In many
cases, the process consumes all the resources of the current thread
so a timer event would not fire until the process was complete.
Therefore, I think to accomplish this, a second thread would need to
be started that could have a timer associated with it.
Randy.
At 05:31 PM 6/11/2008, you wrote:
Hello Viktor
Szakáts Viktor wrote:
>
> 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.
>
You just catched my thoughts, just.
One way, specific to GTWVT, is to implement a timer
with unique id whose sole function is to refresh the window.
Because though this is not desirable under all circumstances,
can be a starting point for thoughts.
Regards
Pritpal Bedi
--
View this message in context:
http://www.nabble.com/Window-updates-vs.-long-Harbour-processes-tp17787182p17787715.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
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
