Will you be rolling this change into the baseline any time soon? I would like to see if this solves a similar problem I have with OS X's threading. I really prefer the threaded tile loader as it gives me a much smoother frame rate.
Thanks,
Jonathan Polley
On Tuesday, December 3, 2002, at 07:29 PM, Norman Vine wrote:
I have updated this tarball to a version that does NOT have a problem exiting.The way I fixed the 'thread not receiving a cancel event' was to make the global_tile_mgr a pointer to an allocated instance of a FGTileMgr and its FGTileLoader member an allocated object also. Then deletiing the global_tile_mgr at exit time automagically destroys the threads :-) This begs the question "How do we want to handle 'Singleton Objects' like this" The static nature they currently have is I believe a leftover from the pre C++ era My instinct is that all of these should be moved into the fgGlobals class and be allocated objects derived from an abstract Singleton class Cheers Norman
_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
