RE: [Flightgear-devel] enrty and exit points of main loop
I remember some documentation on the different sockets available through flightgear, but can't seem to find them on the site. Do you know where I can find these? Thanks, Adam -Original Message- From: David Megginson [mailto:[EMAIL PROTECTED] Sent: Friday, January 23, 2004 6:21 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] enrty and exit points of main loop Erik Hofman wrote: I am trying to add some calls to flightgear's main loop in order to set up shared memory and semaphores, and then remove them when FG exits. The easy part is the initialization but I can't find a good spot in the code to do any cleanup, due to the glutMainLoop. Any suggestions? Is there a special reason for using shared memory when we already have all internals exposed using the property tree and they are all accessible using local sockets or pipes? Or to be more specific and less polite than Erik, NO SHARED MEMORY! I know that FlightGear is not a Unix-only thing, but the Unix programmers have it right using simpler IPC mechanisms like sockets. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] enrty and exit points of main loop
Snyder Adam D Civ AFRL/VACD wrote: I remember some documentation on the different sockets available through flightgear, but can't seem to find them on the site. Do you know where I can find these? Most of it should be present in: FlightGear/docs-mini/README.IO Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] enrty and exit points of main loop
Snyder Adam D Civ AFRL/VACD wrote: Not really, I just need to find a way to clean-up when I am finished. Here's one option. If you put all your code inside a class, then you should be able to put your clean up stuff into the class destructor. That should automatically be called when the program exits. Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.flightgear.org/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] enrty and exit points of main loop
On Fri, 23 Jan 2004 15:39:23 -0500 Snyder Adam D Civ AFRL/VACD [EMAIL PROTECTED] wrote: Hello, I am trying to add some calls to flightgear's main loop in order to set up shared memory and semaphores, and then remove them when FG exits. The easy part is the initialization but I can't find a good spot in the code to do any cleanup, due to the glutMainLoop. Any suggestions? Have you considered registering your cleanup function with atexit()? Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] enrty and exit points of main loop
Erik Hofman wrote: I am trying to add some calls to flightgear's main loop in order to set up shared memory and semaphores, and then remove them when FG exits. The easy part is the initialization but I can't find a good spot in the code to do any cleanup, due to the glutMainLoop. Any suggestions? Is there a special reason for using shared memory when we already have all internals exposed using the property tree and they are all accessible using local sockets or pipes? Or to be more specific and less polite than Erik, NO SHARED MEMORY! I know that FlightGear is not a Unix-only thing, but the Unix programmers have it right using simpler IPC mechanisms like sockets. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
