Norman Vine wrote: > > I have placed a MingW32 < native win32 > fgfs executable compiled > from yesterday's CVS files at > http://rockfish.net/~nhv/fgfs/fgfs_ming_thread.tgz > > This uses the threaded tile pager and I have included > a pthread.dll that must be kept in the same directory > as the executable > > This will require the CVS version of the base files > > There is a 'known' problem exiting the program with the > pager thread not getting a 'quit' mesage
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
