On Thu, Jan 29, 2004 at 01:38:09PM +0100, Pieter Grimmerink wrote:
> All this would cause constant allocating and freeing of memory.
> Doesn't this cause heap fragmentation very quickly?
> Or am I just being paranoid?
I guess you know your device better than I. But with a modern
well-designed mem
Looking at the internals of the server and the client, I see a lot of
malloc/free going on.
I am usually very cautious of heap fragmentation, and I'm afraid PicoGUI will
seriously decrease the stability of our device.
This is what it would be doing continuously:
To get a different window 'on t
One connection can host any number of applications, so it sounds like
multithreading would be enough for you. However, AFAIK the C client lib
has no multithreading support at all. As picogui development is essentially
dead, I'd recommend looking for alternatives.
--Micah
On Thu, Jan 29, 2004 at 0
I'm thinking about writing a new c client for PicoGUI.
The current one is not usable in my situation, since I need either multithread
support, or multiconnection support, so that each thread can call pgInit.
If we can register multiple applications through the same connection,
multithread would
