Re: [Flightgear-devel] Addition of true comms in multiplayer

2007-09-04 Thread Holger Wirtz
Jonathan, On Mon, Sep 03, 2007 at 09:05:59AM -0500, Jonathan Wagner wrote: [...] I probably haven't been following this conversation closely enough, but what about borrowing from the KDE4 projects phonon and decibel. I know phonon will be cross-platform with a Jack, Alsa, GStreamer and

Re: [Flightgear-devel] formatting in nasal

2007-09-04 Thread Melchior FRANZ
* SydSandy -- 9/3/2007 3:11 PM: is there a way to format a double and output that to a string property with writing the double to a property first without? - sprintf() m. - This SF.net email is sponsored by: Splunk Inc.

Re: [Flightgear-devel] Google Earth FlightSimulator

2007-09-04 Thread AnMaster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Someone should contact them and ask them for ways to integrate google earth into flightgear. I tested the google earth flightsim yesterday, the scenery looks very nice in some places but is very bad in others (like around my local airport, ESOE).

Re: [Flightgear-devel] Google Earth FlightSimulator

2007-09-04 Thread Holger Wirtz
Hi all, On Tue, Sep 04, 2007 at 11:07:02AM +0200, AnMaster wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Someone should contact them and ask them for ways to integrate google earth into flightgear. I spoke to Alex Perry from Google at LinuxTag2007 in Berlin. I asked him how

Re: [Flightgear-devel] b1900d livery put-together (was: OSG and material animation, livery change ??)

2007-09-04 Thread K. Hoercher
On 8/31/07, SydSandy [EMAIL PROTECTED] wrote: Oh man I hope you put it back together again ! Ah well, you probably don't want to know to what extend I keep messing with it for unrelated learning, testing and general tweaking around purposes. But that's only because I like it very much. Thanks

Re: [Flightgear-devel] Google Earth FlightSimulator

2007-09-04 Thread AnMaster
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Holger Wirtz wrote: Hi all, On Tue, Sep 04, 2007 at 11:07:02AM +0200, AnMaster wrote: Someone should contact them and ask them for ways to integrate google earth into flightgear. I spoke to Alex Perry from Google at LinuxTag2007 in Berlin.

Re: [Flightgear-devel] Google Earth FlightSimulator

2007-09-04 Thread Leidson Campos A. Ferreira
Hello AnMaster, Last year I did a integration between FlightGear and a autonomous navigation system made by my enterprise to a research institute in Brazil and another team of project did a module to integrate the navigation system information (based on FlightGear's information) with Google Earth

Re: [Flightgear-devel] Google Earth FlightSimulator

2007-09-04 Thread Pigeon
Last year I did a integration between FlightGear and a autonomous navigation system made by my enterprise to a research institute in Brazil and another team of project did a module to integrate the navigation system information (based on FlightGear's information) with Google Earth

Re: [Flightgear-devel] Addition of true comms in multiplayer

2007-09-04 Thread Hans Fugal
On 9/3/07, Holger Wirtz [EMAIL PROTECTED] wrote: On Mon, Sep 03, 2007 at 09:07:09AM -0600, Hans Fugal wrote: libiaxclient may even work in Windows with PortAudio, though it might take some effort. Everyone on the list told me to produce something portable and it took some time to find

Re: [Flightgear-devel] The Release

2007-09-04 Thread Andy Ross
John Denker wrote: 2) It seems vacuous to compare writing via a const char* to writing via a non-const char*, because AFAIK there is no such thing as writing via a const char*. No compiler AFAIK will generate any CPU instructions for it. Oh, good grief: $ echo 'void foo(const char*

Re: [Flightgear-devel] The Release

2007-09-04 Thread Andy Ross
Csaba Halász wrote: Note that literal string constants may be allocated in read-only data section, thus causing segmentation fault at runtime. Try calling your foo function passing a literal string, What does this have to do with the discussion? We are talking about const pointers, not linker

Re: [Flightgear-devel] The Release

2007-09-04 Thread Frederic Bouvier
Quoting Andy Ross : The confusion seems to be that Microsoft declared strchr() as taking and returning a const pointer. Which is broken, because strchr() returns a pointer into the *same* memory it got. The constness needs to be synchronized between the pointers, which is outside the

Re: [Flightgear-devel] formatting in nasal

2007-09-04 Thread SydSandy
On Tue, 04 Sep 2007 10:03:55 +0200 Melchior FRANZ [EMAIL PROTECTED] wrote: * SydSandy -- 9/3/2007 3:11 PM: is there a way to format a double and output that to a string property with writing the double to a property first without? - sprintf() m. yes , without ;) thanks m , I didnt

Re: [Flightgear-devel] The Release

2007-09-04 Thread Csaba Halász
On 9/4/07, Andy Ross [EMAIL PROTECTED] wrote: And in any case I already mentioned (and dismissed) this possibility. From three posts above: Oops, missed that. Sorry. -- Csaba - This SF.net email is sponsored by: Splunk

Re: [Flightgear-devel] The Release

2007-09-04 Thread Hans Fugal
On 9/4/07, Andy Ross [EMAIL PROTECTED] wrote: John Denker wrote: 2) It seems vacuous to compare writing via a const char* to writing via a non-const char*, because AFAIK there is no such thing as writing via a const char*. No compiler AFAIK will generate any CPU instructions for it.

Re: [Flightgear-devel] The Release

2007-09-04 Thread John Denker
On 09/04/2007 09:47 AM, Andy Ross wrote: the patch I assume we are still talking about: http://sourceforge.net/tracker/index.php?func=detailaid=1584727group_id=382atid=100382 strchr() returns a pointer into the *same* memory it got. The constness needs to be synchronized

Re: [Flightgear-devel] formatting in nasal

2007-09-04 Thread Andy Ross
SydSandy wrote: Hi all , is there a way to format a double and output that to a string property with writing the double to a property first . Should be doable but it escapes me at the moment ... Example : (double) 2.30 to (string) 2:30 Nasal numbers will convert directly to strings

Re: [Flightgear-devel] The Release

2007-09-04 Thread Andy Ross
Hans Fugal wrote: I could be wrong, but I think you missed his point. I don't think he was arguing that you couldn't cast a const char* to a char*. The argument was that without the cast it doesn't work, and the cast is bad form and leads to bugs. A point, you will note, I never disagreed

Re: [Flightgear-devel] formatting in nasal

2007-09-04 Thread SydSandy
On Tue, 04 Sep 2007 09:10:02 -0700 Andy Ross [EMAIL PROTECTED] wrote: SydSandy wrote: Hi all , is there a way to format a double and output that to a string property with writing the double to a property first . Should be doable but it escapes me at the moment ... Example : (double)

Re: [Flightgear-devel] b1900d livery put-together (was: OSG and material animation, livery change ??)

2007-09-04 Thread SydSandy
On Tue, 4 Sep 2007 13:13:04 +0200 K. Hoercher [EMAIL PROTECTED] wrote: On 8/31/07, SydSandy [EMAIL PROTECTED] wrote: Oh man I hope you put it back together again ! Ah well, you probably don't want to know to what extend I keep messing with it for unrelated learning, testing and general

Re: [Flightgear-devel] formatting in nasal

2007-09-04 Thread Andy Ross
SydSandy wrote: No its not a typo , I want a single string property to hold groundspeed ,TTG and ET , depending on which mode is selected for display on the Primus PFD OK. You might want to make that property a string, though, or at least an integer. Storing a fracional number there and

Re: [Flightgear-devel] The Release

2007-09-04 Thread olaf flebbe
Hi, No, the confusion seems to come from the difference between standard C runtime and standard C++ runtime. MSVC8 wants to conform to the latter when compiling C++ code. Look at that page : Thanks. As a side note: The gcc does not enforce const-correctness very much. The SUN Compilers are

Re: [Flightgear-devel] The Release

2007-09-04 Thread olaf flebbe
Hi, I wrote: Plib's behavior in the lines touched by this patch is platform independent. And this bit of the patch is just flat wrong. The original version finds the first _ in the string and nul-terminates it at that location. The fixed code it a complete no-op. - char

Re: [Flightgear-devel] The Release

2007-09-04 Thread Andy Ross
olaf flebbe wrote: As a side note: The gcc does not enforce const-correctness very much. Sigh, and the flames continue... Your basis for that statement is what, exactly? Of course gcc enforces const correctness. I suspect what's happening here is that plib, which is using string.h and not

Re: [Flightgear-devel] The Release

2007-09-04 Thread olaf flebbe
Hi, thanks John! --- Returning to the higher-level discussion, it is not necessary to do a strdup in this situation, as the following constructive suggestion illustrates. ... Johns nice example ... int main(){ char aa[100]; const char* xx(aa);

Re: [Flightgear-devel] The Release

2007-09-04 Thread Andy Ross
olaf flebbe wrote: Please do not mix the terms compiles o.k. and works for me with the code is correct. I did no such thing. The issue here is whether or not the code is the *same* as the one we are shipping on other platforms. Yours is not, and therefore really shouldn't be packaged up into

Re: [Flightgear-devel] The Release

2007-09-04 Thread olaf flebbe
Hi, If my memory serves, VC8 shipped with a new runtime that won't work on XP without an update, right? Wrong. Regardless, you need to fix that patch if you want to see it used. Yes, I would have to update to current SVN. But I am getting tired of fixing non-gcc bugs. Olaf

Re: [Flightgear-devel] The Release

2007-09-04 Thread Andy Ross
olaf flebbe wrote: If my memory serves, VC8 shipped with a new runtime that won't work on XP without an update, right? Wrong. Can you elaborate? I'm all but certain that default builds want to link against MSVCR80.DLL (or whatever) at runtime, no? Are we set up to install that in our

Re: [Flightgear-devel] The Release

2007-09-04 Thread olaf flebbe
Hi, If my memory serves, VC8 shipped with a new runtime that won't work on XP without an update, right? Wrong. Can you elaborate? I'm all but certain that default builds want to link against MSVCR80.DLL (or whatever) at runtime, no? One possibility: link statically. Are we set up to