Hello all,
while(g_main_iteration(FALSE)) did help!!! That's great.
Anyway, I think I'll go the multithreaded approach
(more elegant and 'clean'). Just takes more time...
Thanks to you all for the fast replies and given help!!!
Many cheers,
Michael.
--
GMX - Die Kommunikationsplattform im
From: [EMAIL PROTECTED]
X-Priority: 3 (Normal)
X-Authenticated-Sender: #[EMAIL PROTECTED]
X-Authenticated-IP: [128.131.86.231]
X-Flags: 0001
Content-Type: text/plain; charset=us-ascii
Sender: [EMAIL PROTECTED]
X-BeenThere: [EMAIL PROTECTED]
X-Loop: [EMAIL PROTECTED]
X-Mailman-Version:
Oh hell!!!
Now I'm scared! Why did nobody tell me before? Is that common
with all GUI toolkits?
Not unless you create a separate thread for the calculations. When the
calculations finish, you should be able to interact with the GUI again.
The problem is: I'm no (good) thread programmer and
yes, it is common to more or less all GUI toolkits, regardless of OS
platform.
Isn't there a way to shortly stop calculations (for a necessary minimum
of time) and let the GUI gather possible events? Could this work
this way somehow? Any suggestions?
somewhere inside your calculations, call
From: Paul Davis [EMAIL PROTECTED]
yes, it is common to more or less all GUI toolkits, regardless of OS
platform.
Isn't there a way to shortly stop calculations (for a necessary minimum
of time) and let the GUI gather possible events? Could this work
this way somehow? Any suggestions?
[EMAIL PROTECTED] writes:
Oh hell!!!
Now I'm scared! Why did nobody tell me before? Is that common
with all GUI toolkits?
Pretty much (it's true of all X toolits that I know of). And every
new GUI programmer gets bitten by it.
Not unless you create a separate thread for the
