Re: [Flightgear-devel] c172-dpm.ac
Dave Culp wrote: The message: WARNING: ssgLoadAC: Failed to open '/home/dave/FlightGear-0.9.9-pre2/data/Aircraft/c172r/Models/c172-dpm.ac' for reading I've already fixed this by referencing the default c172p instead. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] PropertyList over network
Jeff McBride wrote: Hello All, I am considering using a property tree similar to that in Flightgear for a UAV ground control application, and I have a question for the developers on the list. Has anyone ever looked into creating a system to share a common property tree between two computers over a network connection? E.g. when a property is changed at one end it is updated at the other end as well. Do you think that this could be done efficiently? Has anyone written code to do it? Yes, I have been working on it but didn't find enough time to finish it. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] [PATCH] Re: SEGV with ATIS
Pigeon wrote: Figured out the problem with ATIS voice. It's in SimGear with the code for OpenAL/Alut 1.1, whereby with in sample_openal.cxx, alutCreateBufferFromFile() does not give us the raw sound data, and ATCVoice depends on it, which leaves the data and the data size uninitialized. Good catch (and bad practice). The patch used alutLoadMemoryFromFile() instead, pretty much the new version of the old deprecated alutLoadWAVFile(). I've made a much clearer separation between loading the data and sending it to the sound driver. This prevents data to be loaded into main/sound-card memory when it's not needed. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problem report related to strange splash screens and crashes with certain aircraft
Arthur Wiebe wrote: I think this report basically pins down two of my problems. First, where spash screens on startup showed up as strange color stipes. And second, where certain aircraft which define their own spash screen crash fgfs. I got this report when trying to load the c310 (pre3). Hopefully either one of you will find what's wrong or I'll look into it some more tomorrow. Looking at the code I don't see anything abvious. You might want to add a fw printf() statements in SGTexture::ImageGetRow to see whether the sizes are correct and the pointers are valid. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Possible bug in yasim (not sure though?)
On Fri, 2005-11-11 at 22:43 -0500, Josh Babcock wrote: Curtis L. Olson wrote: George Patterson wrote: Thanks Andy. I just completed a nice flight from KSFO to KLAX with 3D clouds turned on. Mistakenly misread 25L as being 24L. George Ooops, stop by the FAA office, do not pass Go, do not collet $200 ... Curt. Or, into the office next door to the FAA, wonder where everyone is, wander back out, blame it on the weather :) Okay... I deserved that. :-P However I tried again this evening (though directed by ATC to use a different runway (07L) ) and got it right :-) George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] OT: FYI, mac os x developers, xcode 2.2 has been released
Installing the new xcode 2.2 software on mac os 10.4.3 took about 50 minutes. (During which I did a make clean 8-) of plib, simgear and flightgear) Rebuilding plib, simgear and flightgear (latest cvs around 1pm gmt) took about one hour. Running fgfs, I get an abend: OpenAL error (AL_INVALID_VALUE): constructor (alutLoadWAVFile) terminate called after throwing an instance of 'sg_exception' Abort gcc --version powerpc-apple-darwin8-gcc-4.0.1 (GCC) 4.0.1 (Apple Computer, Inc. build 5247) Copyright (C) 2005 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. the old gcc version was: gcc --version powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 (Apple Computer, Inc. build 5026) Copyright (C) 2005 Free Software Foundation, Inc. Best regards, Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runtime error 0.9.9 on Debian/Testing
$ fgfs opening file: /usr/local/share/FlightGear/Navaids/carrier_nav.dat /usr/local/share/FlightGear/Navaids/TACAN_freq.dat RenderTexture Error: glXCreateGLXPbufferPtr() failed. Initialising callsign using 'Aircraft/c172p/Models/c172p.xml' freeglut (fgfs): Failed to create cursor freeglut ERROR: Function glutSetCursor called \ without first calling 'glutInit'. Hey Alex, this has been a 'common' issue that has bit a lot of people. There appears to be a problem with freeglut 2.4. The solution has been to downgrade to freeglut 2.2 or run freeglut-cvs. You could also build with sdl (configure --enable-sdl) and that might side step the issue altogether. Regards, Curt. It looks to me that this will be a recurrent issue following 0.9.9 release as well. Can an autoconf guru please add a relevant check into the configuration scripts? V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] diff for browser change for mac os x to use safari
On things like Debian, this is also wrong because sensible-browser should be used instead. Is there some autoconf library function to discover the most likely browser on a system? Also the WIN32 section in src/GUI/gui_funcs.cxx with the 1024-long hardcoded buffers can be a crash trigger when the buffer overflows for somebody with a long enough path... V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Review (was: Which aircraft to include in v0.9.9?)
Maybe some German-speaking user could point the reporters to Atlas for the moving map solution they describe as absent (and to the new Pigeon's map!) V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] cygwin FG build break latest CVS + run time error
To fix the build break you need to patch: Index: FlightGear/src/Time/sunsolver.cxx===RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Time/sunsolver.cxx,vretrieving revision 1.6diff -u -r1.6 sunsolver.cxx--- FlightGear/src/Time/sunsolver.cxx 11 Nov 2005 14:46:15 - 1.6+++ FlightGear/src/Time/sunsolver.cxx 12 Nov 2005 14:06:20 -@@ -23,6 +23,11 @@ * $Id: sunsolver.cxx,v 1.6 2005/11/11 14:46:15 ehofman Exp $ */ ++#ifdef HAVE_CONFIG_H+# include config.h+#endif+#ifdef SG_HAVE_STD_INCLUDES# include cmath// # include cstdio I am using the openal_cyg.tgz from http://www.mail-archive.com/flightgear-users@flightgear.org/msg10995.html The run time error I get is: Russian: (âÞçÚÐ ÒåÞÔÐ Ò ßàÞæÕÔãàã alutLoadWAVFile ÝÕ ÝÐÙÔÕÝÐ Ò ÑØÑÛØÞâÕÚÕ DLL openal32.dll) English: Entry point into procedure alutLoadWAVFile not found in dll library openal32.dll $ which openal32.dll/usr/local/bin/openal32.dll [EMAIL PROTECTED] /cygdrive/s/flightgear/fgdev9.9$ ls -l /usr/local/bin/openal32.dll-rwxr-xr-x 1 °ÔÜØÝØáâàÐâÞà ¾âáãâáâÒãÕâ 480468 Apr 30 2004 /usr/local/bin/openal32.dll [EMAIL PROTECTED] /cygdrive/s/flightgear/fgdev9.9$ Thank you! Ima ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [BUG] environemnt_ctrl.cxx: exception triggers SGThread assert()
I've just implemented the check for stale METAR reports (to stop
fetching after 10 stale reports). This triggers an assert in
SGThread:
fgfs: /usr/local/include/simgear/threads/SGThread.hxx:155:
void SGThread::join(): Assertion `status == 0' failed.
I don't know much about threads. Could someone check (Erik, Curt? :-)
Apply this patch to reproduce (my changes aren't committed yet):
diff -u -p -r1.37 environment_ctrl.cxx
--- environment_ctrl.cxx26 Oct 2005 09:03:49 - 1.37
+++ environment_ctrl.cxx12 Nov 2005 14:14:55 -
@@ -558,6 +558,7 @@ FGMetarEnvironmentCtrl::fetch_data( cons
// fetch current metar data
try {
+_error_count = 1000;throw sg_io_exception(Boo!);
string host = proxy_host-getStringValue();
string auth = proxy_auth-getStringValue();
string port = proxy_port-getStringValue();
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] diff for browser change for mac os x to use safari
In the macflightgear binary I've been passing --browser-app=open to fgfs. This opens the url in the default browser. For me that's Firefox.Your patch could be changed to something like this:Index: FlightGear/src/Main/options .cxx===RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,vretrieving revision 1.73diff -u -r1.73 options.cxx --- FlightGear/src/Main/options.cxx 12 Oct 2005 08:55:58- 1.73+++ FlightGear/src/Main/options.cxx 12 Nov 2005 02:41:34 -@@ -172,7 +172,11 @@ fgSetString(/sim/control-mode, joystick); fgSetBool(/sim/auto-coordination, false);#if !defined(WIN32)+#ifdef __APPLE__+ fgSetString(/sim/startup/browser-app, open);+#else fgSetString(/sim/startup/browser-app, netscape); +#endif#else fgSetString(/sim/startup/browser-app, webrun.bat);#endifOn 11/12/05, Ima Sudonim [EMAIL PROTECTED] wrote:Arthur and James,Yes, I agree it's silly, but currently help was broken on my two mac systems (giving a log message that netscape couldn't be found),followed by a dialog that my browser was started.It's reallyimportant to me to have browser-based help work on 0.9.9... I forgotthat it was broken until now. (I know I had this working at one point, and thought I still did as I was building with a modifiedoptions.cxx. I was wrong). I promise to pay much more attention nexttime or at least be conscious when I try these thingsUnfortunately, my fix doesn't work. I think it should have been the following diff, but as neither diffis working, don't apply them to cvs please.I can't get this options.cxx change working on Mac OS X, I have touse the option --browser-app=open /Applications/Safari.app when starting flightgear.Any idea where else /sim/startup/browser-app is set or what (ifanything) is overwriting it?Never mind about the cvs update. It wouldn't break anything even ifapplied, because it didn't work anyway. 8-( It looks like the mac browser exec actually belongs in gui/gui_funcs.cxx. If I modify void helpCb (puObject *) (line 238) to read: string help_app = open /Applications/Safari.app ;//fgGetString (/sim/startup/browser-app);Safari starts up fine and opens help so this is the spot Arthur wouldneed to pop his code into, I guess.It would be nice if the returncode from the system call or ShellExecute could be checked before mkDialog is called.It's adding insult to injury when your browserhasn't started, but the dialog says it has 8-(I'm still a little confused as to where /sim/startup/browser-app isbeing set, as it doesn't seem to be in main/options.cxx as I expected. I will leave this to much wiser heads than my own.Sorry for thetrouble. Some days it doesn't pay to get out of bed in the morning...8-(I'll happily wait for arthur to fix it.Thanks to Arthur and James and all the rest... ImaIndex: FlightGear/src/Main/options.cxx===RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/options.cxx,vretrieving revision 1.73diff -u -r1.73 options.cxx--- FlightGear/src/Main/options.cxx 12 Oct 2005 08:55:58-1.73+++ FlightGear/src/Main/options.cxx 12 Nov 2005 02:41:34 -@@ -172,7 +172,11 @@fgSetString(/sim/control-mode, joystick); fgSetBool(/sim/auto-coordination, false);#if !defined(WIN32)+#ifdef __APPLE__+fgSetString(/sim/startup/browser-app, open /Applications/Safari.app);+#else fgSetString(/sim/startup/browser-app, netscape);+#endif#elsefgSetString(/sim/startup/browser-app, webrun.bat);#endif___ Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: FYI, mac os x developers, xcode 2.2 has been released
I've been using Xcode 2.2 for some time now building Flightgear and everything else. Preview builds until now of course.By the way Xcode projects you can use to build PLIB, Simgear, and FlightGear are available now. I've polished them up so they should be ready. If you're interested I'll commit them to the macflightgear cvs.On 11/12/05, Ima Sudonim [EMAIL PROTECTED] wrote:According to apple developer connection (ADC) news, Apple's xcode 2.2 has been released.It would be nice to know that the new fixes haven't brokenFlightGear... It is an 834 MB disk image update for mac os x 10.4.x. Download Newly Released Xcode 2.2 Today Latest tools make building universal binaries even easier. All Apple Developer Connection members can download the newlyreleased Xcode 2.2 at no cost from the ADC Member Site.Basic ADC memberships are free, and permit downloading developmenttools and updates. ADC members can download from http://insideapple.apple.com/redir/303569/452_100/1ef0a2707706d7cd11214f98ad642f06Best regards,Ima ___Flightgear-devel mailing listFlightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] try ... catch ... throw (up)
Here's what I'm doing:
In the Table class:
In FGTable constructor:
if (operation_types.find(parent_type) == string::npos) {
internal = true;
} else {
throw(string(An internal table cannot be ...));
}
Now, this seems to work OK - I throw an exception if a situation
occurs that is invalid.
[snip]
I'm probably missing something fundamental here. Anyone have any suggestions?
Jon
I am unsure it is OK to through a temporary object like this.
It's created on the stack right there at the same frame where it's thrown,
but IIRC, as throw unwinds the stack, it is auto-destructed. You should
be throwing an object that has lifetime encompassing the outer catch
handler.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] try ... catch ... throw (up)
Vassilii Khachaturov wrote: I am unsure it is OK to through a temporary object like this. It's created on the stack right there at the same frame where it's thrown, but IIRC, as throw unwinds the stack, it is auto-destructed. You should be throwing an object that has lifetime encompassing the outer catch handler. Ah! Yes, that sounds correct. I'll have to go back and change my throws. Thanks, Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runtime error 0.9.9 on Debian/Testing
Vassilii Khachaturov wrote: It looks to me that this will be a recurrent issue following 0.9.9 release as well. Can an autoconf guru please add a relevant check into the configuration scripts? I see that freeglut-2.2 defines FREEGLUT_VERSION_2_0 = 1 Can anyonen with freeglut-2.4 look and see if it leaves any differentiable defines that are different from freeglut-2.2 and different from freeglut-cvs? It's probably possible to craft some sort of ugliness into the configure script, but I'd be a little nervous about doing something this close to the v0.9.9 release. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] diff for browser change for mac os x to use safari
Arthur and Vassilii, Even though I couldn't fix it, I'm glad I got smarter minds to think about it! 8-) OK, is there a way to get sensible-browser at compile time? Is this a link know to the OS or something? is it callable or does it need to be read on Debian somewhere? this is also wrong because "sensible-browser" should be used instead. Nice catch, not sure how to fix it though. Is there a standard path length limit? Is it queryable from some C call? Also the WIN32 section in src/GUI/gui_funcs.cxx with the 1024-long hardcoded buffers can be a crash trigger when the buffer overflows for somebody with a long enough path... OK, now I understand what you meant by just using open by itself. I didn't know you could do that, thanks! In the macflightgear binary I've been passing "--browser-app=open" to fgfs. This opens the url in the default browser. For me that's Firefox. Yes, even though I don't use xcode much (too complicated for my tiny brain 8-)), I'd like to have the projects for reference. I use the command line to make fg and run a graphical x window front end (DDD) to gdb. I don't do either very often or very well. 8-( Macflightgear is hosted on sourceforge? By the way Xcode projects you can use to build PLIB, Simgear, and FlightGear are available now. I've polished them up so they should be ready. If you're interested I'll commit them to the macflightgear cvs Actually, I can't test this (my wife is using the Mac as a telephone 8-( ), but your fix would need to go in two places: src/Main/options.cxx and src/GUI/gui_funcs.cxx (in void helpCb). I think that one might be the actual OS Application Help menu Help menu item and one the flightgear gui menu Help menu Help menu item (but I can't test this right now and could be wrong). Could you possibly do this additional patch also? I'm not sure when I'll get use of the Mac again. Then again, with arthritis I don't sleep much! 8-) Also, is it a problem that the rc to the call to start the browser isn't checked before the mkDialog call (leading to possibly inaccurate messages that the browser has been started when in fact it failed to do so) as mentioned in my previous message? Thanks for all your help and suggestions! Ima . ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] [BUG] environemnt_ctrl.cxx: exception triggers SGThread assert()
Melchior FRANZ wrote:
I've just implemented the check for stale METAR reports (to stop
fetching after 10 stale reports). This triggers an assert in
SGThread:
fgfs: /usr/local/include/simgear/threads/SGThread.hxx:155:
void SGThread::join(): Assertion `status == 0' failed.
I don't know much about threads. Could someone check (Erik, Curt? :-)
Apply this patch to reproduce (my changes aren't committed yet):
diff -u -p -r1.37 environment_ctrl.cxx
--- environment_ctrl.cxx26 Oct 2005 09:03:49 - 1.37
+++ environment_ctrl.cxx12 Nov 2005 14:14:55 -
@@ -558,6 +558,7 @@ FGMetarEnvironmentCtrl::fetch_data( cons
// fetch current metar data
try {
+_error_count = 1000;throw sg_io_exception(Boo!);
string host = proxy_host-getStringValue();
string auth = proxy_auth-getStringValue();
string port = proxy_port-getStringValue();
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
It's perhaps because of the PTHREAD_CREATE_DETACHED attribute of the thread.
Harald.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
On another note, this was taken in Singapore recently: http://www.airliners.net/open.file/957790/L/ Compare to what we have in FlightGear now: http://www.students.yorku.ca/~ampere/fgfs-screen-005.jpg Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problem report related to strange splash screens and crashes with certain aircraft
Hey Erik, I may sound like I know what I'm doing sometimes but I really don't. :)Nevertheless I'll add some printf statements and see what happens. I suppose it should be done in the ImageGetRow implementation. On 11/12/05, Erik Hofman [EMAIL PROTECTED] wrote: Arthur Wiebe wrote: I think this report basically pins down two of my problems. First, where spash screens on startup showed up as strange color stipes. And second, where certain aircraft which define their own spash screen crash fgfs. I got this report when trying to load the c310 (pre3). Hopefully either one of you will find what's wrong or I'll look into it some more tomorrow.Looking at the code I don't see anything abvious. You might want to add a fw printf() statements in SGTexture::ImageGetRowto see whether the sizes are correct and the pointers are valid.Erik___Flightgear-devel mailing list Flightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] pre3 bugs
I've noticed a few bugs to report, 1. when running flightgear, press [ESC] , then [TAB] (intending to move the cursor to the cancel button) instead the instrument settings dialog comes up. ok. But: I can not press the Close button or click in the text fields, instead I can only click on the exit window underneath. It looks like the who's on top also occurs elsewhere, but not the can't click close, or press [ESC]. Neither can I drag the instrument window away from covering the exit window. 2. Select Aircraft from list: looks like the list box is one line too large and overruns the top of it's border window. It's a pleasure to have the scroll bar work. :) 3. If I start fgfs with --aircraft=T38 I get the error: Fatal error: Failed to open file at /usr/local/share/FlightGear/data/Data/AI/refueling_demo.xml (received from SimGear XML Parser) I note this file (and directory) was removed from fgfs-base-pre3 but is still referenced in: src/AIModel/AIScenario.cxxlines 46-48 and the nonexistant directory is mentioned in: src/AIModel/AIFlightPlan.cxx lines 51, 113 4. In a list box (like in Select Aircraft), when single clicking on an entry, the text becomes unreadable. Perhaps the background was supposed to darken? Otherwise, very nice flight. I see several improvements were made over the summer. :) Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: pre3 bugs
* Stewart Andreason -- Saturday 12 November 2005 18:00: 1. when running flightgear, press [ESC] , then [TAB] (intending to move the cursor to the cancel button) Cycling widget focus with TAB is not implemented, and never was. instead the instrument settings dialog comes up. ok. But: I can not press the Close button or click in the text fields, instead I can only click on the exit window underneath. It looks like the who's on top also occurs elsewhere, but not the can't click close, or press [ESC]. That's because the exit dialog ($FG_ROOT/gui/dialogs/exit.xml) is modal, This means that it blocks the gui and (because it's derived from a different plib dialog than almost all other dialogs) doesn't allow accelerator keys. Neither can I drag the instrument window away from covering the exit window. You can set modaltrue/modal in said file to false. Then it's at least movable, and the other dialog can be moved in front. Maybe this should be done in CVS? This is a usability bug, but intentional. ;-) 2. Select Aircraft from list: looks like the list box is one line too large and overruns the top of it's border window. It's a pleasure to have the scroll bar work. :) FWIW: This will probably be thrown out after the 0.9.0 release. (Which doesn't mean that there won't be someone who fixes it before. :-) 4. In a list box (like in Select Aircraft), when single clicking on an entry, the text becomes unreadable. Perhaps the background was supposed to darken? Well, you clicked it. Just remember the name before it becomes unreadable. ;-) FYI: you can also switch to a different GUI them (Shift-F10). Maybe it's better readable then ... or worse ... m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] diff for browser change for mac os x to use safari
OK, is there a way to get sensible-browser at compile time? Is this a link know to the OS or something? is it callable or does it need to be read on Debian somewhere? It's a callable standard script on debian. It tries various intelligent decisions to guess what browser to run. It is pretty debian-dependent though (e.g., it relies on the fact that the browser packages register themselves via the alternatives mechanism available on debian). On Debian, however, it is the preferred thing to call in order to be user-friendly. My point is that fgfs doesn't have the means to know the target system defaults and thus the hardwired default is probably best left as a toplevel configure option. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runtime error 0.9.9 on Debian/Testing
From: Curtis L. Olson [EMAIL PROTECTED] Alex Perry wrote: freeglut ERROR: Function glutSetCursor called \ without first calling 'glutInit'. Hey Alex, this has been a 'common' issue that has bit a lot of people. There appears to be a problem with freeglut 2.4. The solution has been to downgrade to freeglut 2.2 or run freeglut-cvs. You could also build with sdl (configure --enable-sdl) and that might side step the issue altogether. Debian is packaging 2.4.0 under the name freeglut3. Is there a specific upstream release that contains the fix, so that I can file a bug against the existing package ? Otherwise, Debian will be unable to build a current FGFS release. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runtime error 0.9.9 on Debian/Testing
Alex Perry wrote: From: Curtis L. Olson [EMAIL PROTECTED] Alex Perry wrote: freeglut ERROR: Function glutSetCursor called \ without first calling 'glutInit'. Hey Alex, this has been a 'common' issue that has bit a lot of people. There appears to be a problem with freeglut 2.4. The solution has been to downgrade to freeglut 2.2 or run freeglut-cvs. You could also build with sdl (configure --enable-sdl) and that might side step the issue altogether. Debian is packaging 2.4.0 under the name freeglut3. Is there a specific upstream release that contains the fix, so that I can file a bug against the existing package ? Otherwise, Debian will be unable to build a current FGFS release. From what I've heard, freeglut-2.2.0 works and freeglut-CVS It's a shame that this bug crept into Freeglut, because it kind of hurts us on a *lot* of platforms. :-( Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runtime error 0.9.9 on Debian/Testing
On November 12, 2005 01:10 pm, Alex Perry wrote: Debian is packaging 2.4.0 under the name freeglut3. Is there a specific upstream release that contains the fix, so that I can file a bug against the existing package ? Otherwise, Debian will be unable to build a current FGFS release. You can get SDL and use the --enable-sdl flag when running configure for FlightGear. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Runtime error 0.9.9 on Debian/Testing
* Ampere K. Hardraade -- Saturday 12 November 2005 19:31: You can get SDL and use the --enable-sdl flag when running configure for FlightGear. Which also fixes repeatable keys. freeglut is neither compatible with SDL nor with legacy glut. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
Martin Spott wrote: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Devel/BaseObjects.tgz O.k., there is a new file, please check it out - and put it into the base package if you think it is correct :-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Ampere K. Hardraade wrote: On another note, this was taken in Singapore recently: http://www.airliners.net/open.file/957790/L/ Compare to what we have in FlightGear now: http://www.students.yorku.ca/~ampere/fgfs-screen-005.jpg You might want to ignore the two Windows PeeCees for your model ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] diff for browser change for mac os x to use
Arthur Wiebe wrote: [...] SSBhZ3JlZSB3aXRoIEphbWVzLiBJJ3ZlIGJlZW4gdXNpbmcgdGhlIC0tb3Blbi13aXRoIG9wdGlv As Arthur obviously decided to ignore private mail on this topic I think I'd post my comment on the list: Could we please agree not to post encoded EMail on this list !?! Thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 repost
Dave Culp wrote: Dent: .Dent: ..Dent: EHAMopening [...] I don't know what the Dent stuff is. I think tis is Directory ENTry. There is a . in this subdir, there is a .. and there is EHAM :-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Martin Spott wrote: Ampere K. Hardraade wrote: On another note, this was taken in Singapore recently: http://www.airliners.net/open.file/957790/L/ Compare to what we have in FlightGear now: http://www.students.yorku.ca/~ampere/fgfs-screen-005.jpg You might want to ignore the two Windows PeeCees for your model ;-) Are they even Windows? Didn't see an answer in the comments. Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
On November 12, 2005 01:50 pm, Martin Spott wrote: You might want to ignore the two Windows PeeCees for your model ;-) Martin. Yes, I notice that, too. Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] diff for browser change for mac os x to use
Sorry Martin. I never received an email from you. It may have gone into spam.But sure. No encoded email from me anymore.On 11/12/05, Martin Spott [EMAIL PROTECTED] wrote:Arthur Wiebe wrote: [...] SSBhZ3JlZSB3aXRoIEphbWVzLiBJJ3ZlIGJlZW4gdXNpbmcgdGhlIC0tb3Blbi13aXRoIG9wdGlvAs Arthur obviously decided to ignore private mail on this topic Ithink I'd post my comment on the list:Could we please agree not to post encoded EMail on this list !?! Thanks,Martin.-- Unix _IS_ user friendly - it's just selective about who its friends are !--___ Flightgear-devel mailing listFlightgear-devel@flightgear.orghttp://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d-- Arthur/- http://sourceforge.net/users/artooro/- http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Stefan Seifert wrote: Martin Spott wrote: Ampere K. Hardraade wrote: On another note, this was taken in Singapore recently: http://www.airliners.net/open.file/957790/L/ Compare to what we have in FlightGear now: http://www.students.yorku.ca/~ampere/fgfs-screen-005.jpg You might want to ignore the two Windows PeeCees for your model ;-) Are they even Windows? Didn't see an answer in the comments. Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d I wouldn't ignore them, just texture them with this for extra realty: http://www.sirgalahad.org/paul/sw/winlock/img/bsod.png Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Josh Babcock wrote: Stefan Seifert wrote: Martin Spott wrote: Ampere K. Hardraade wrote: On another note, this was taken in Singapore recently: http://www.airliners.net/open.file/957790/L/ Compare to what we have in FlightGear now: http://www.students.yorku.ca/~ampere/fgfs-screen-005.jpg You might want to ignore the two Windows PeeCees for your model ;-) Are they even Windows? Didn't see an answer in the comments. Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d I wouldn't ignore them, just texture them with this for extra realty: http://www.sirgalahad.org/paul/sw/winlock/img/bsod.png Josh How about a spyware popup ... Oh I see you just typed the word Paris, here are some great hotel + airfare combinations you might be interested in, and would you like me to search ebay for berets? Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Curtis L. Olson wrote: How about a spyware popup ... Oh I see you just typed the word Paris, here are some great hotel + airfare combinations you might be interested in, and would you like me to search ebay for berets? No, not spyware - clippy :-) Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: FYI, mac os x developers,
Arthur, can you read _this_ ? Arthur Wiebe wrote: [...] SSd2ZSBiZWVuIHVzaW5nIFhjb2RlIDIuMiBmb3Igc29tZSB0aW1lIG5vdyBidWlsZGluZyBGbGln aHRnZWFyIGFuZApldmVyeXRoaW5nIGVsc2UuIFByZXZpZXcgYnVpbGRzIHVudGlsIG5vdyBvZiBj b3Vyc2UuCgpCeSB0aGUgd2F5IFhjb2RlIHByb2plY3RzIHlvdSBjYW4gdXNlIHRvIGJ1aWxkIFBM SUIsIFNpbWdlYXIsIGFuZCBGbGlnaHRHZWFyCmFyZSBhdmFpbGFibGUgbm93LiBJJ3ZlIHBvbGlz aGVkIHRoZW0gdXAgc28gdGhleSBzaG91bGQgYmUgcmVhZHkuCklmIHlvdSdyZSBpbnRlcmVzdGVk IEknbGwgY29tbWl0IHRoZW0gdG8gdGhlIG1hY2ZsaWdodGdlYXIgY3ZzLgoKT24gMTEvMTIvMDUs IEltYSBTdWRvbmltIDxpbWEuc3Vkb25pbUBjb21jYXN0Lm5ldD4gd3JvdGU6Cj4KPiBBY2NvcmRp bmcgdG8gYXBwbGUgZGV2ZWxvcGVyIGNvbm5lY3Rpb24gKEFEQykgbmV3cywgQXBwbGUncyB4Y29k ZSAyLjIKPiBoYXMgYmVlbiByZWxlYXNlZC4KPiBJdCB3b3VsZCBiZSBuaWNlIHRvIGtub3cgdGhh dCB0aGUgbmV3IGZpeGVzIGhhdmVuJ3QgYnJva2VuCj4gRmxpZ2h0R2Vhci4uLiBJdCBpcyBhbiA4 MzQgTUIgZGlzayBpbWFnZSB1cGRhdGUgZm9yIG1hYyBvcyB4IDEwLjQueC4KPgo+ID5Eb3dubG9h ZCBOZXdseSBSZWxlYXNlZCBYY29kZSAyLjIgVG9kYXkKPiA+TGF0ZXN0IHRvb2xzIG1ha2UgYnVp bGRpbmcgdW5pdmVyc2FsIGJpbmFyaWVzIGV2ZW4gZWFzaWVyLgo+Cj4gPkFsbCBBcHBsZSBEZXZl bG9wZXIgQ29ubmVjdGlvbiBtZW1iZXJzIGNhbiBkb3dubG9hZCB0aGUgbmV3bHkKPiByZWxlYXNl ZCBYY29kZSAyLjIgYXQgbm8gY29zdCBmcm9tIHRoZSBBREMgTWVtYmVyIFNpdGUuCj4KPiBCYXNp YyBBREMgbWVtYmVyc2hpcHMgYXJlIGZyZWUsIGFuZCBwZXJtaXQgZG93bmxvYWRpbmcgZGV2ZWxv cG1lbnQKPiB0b29scyBhbmQgdXBkYXRlcy4KPgo+IEFEQyBtZW1iZXJzIGNhbiBkb3dubG9hZCBm cm9tIDxodHRwOi8vaW5zaWRlYXBwbGUuYXBwbGUuY29tL3JlZGlyLwo+IDMwMzU2OS80NTJfMTAw LzFlZjBhMjcwNzcwNmQ3Y2QxMTIxNGY5OGFkNjQyZjA2Pgo+Cj4gQmVzdCByZWdhcmRzLAo+Cj4g SW1hCj4KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+ IEZsaWdodGdlYXItZGV2ZWwgbWFpbGluZyBsaXN0Cj4gRmxpZ2h0Z2Vhci1kZXZlbEBmbGlnaHRn ZWFyLm9yZwo+IGh0dHA6Ly9tYWlsLmZsaWdodGdlYXIub3JnL21haWxtYW4vbGlzdGluZm8vZmxp Z2h0Z2Vhci1kZXZlbAo+IDJmNTg1ZWVlYTAyZTJjNzlkN2IxZDhjNDk2M2JhZTJkCj4KCgoKLS0K PEFydGh1ci8+Ci0gaHR0cDovL3NvdXJjZWZvcmdlLm5ldC91c2Vycy9hcnRvb3JvLwotIGh0dHA6 Ly9hcnRvb3JvLmJsb2dzcG90LmNvbQo= So, why are you posting this crap ? Please stop it, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: OT: FYI, mac os x developers,
* Martin Spott -- Saturday 12 November 2005 20:43: Z2h0Z2Vhci1kZXZlbAo+IDJmNTg1ZWVlYTAyZTJjNzlkN2IxZDhjNDk2M2JhZTJkCj4KCgoKLS0K PEFydGh1ci8+Ci0gaHR0cDovL3NvdXJjZWZvcmdlLm5ldC91c2Vycy9hcnRvb3JvLwotIGh0dHA6 Ly9hcnRvb3JvLmJsb2dzcG90LmNvbQo= So, why are you posting this crap ? Please stop it, This is very standard base64 encoding. Every semi-decent mailer should be able to display this. Of course, it would be better in readable ASCII, but I wouldn't say it's crap. Your mailer *is* crap! :-P m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
Melchior FRANZ wrote: * Martin Spott -- Saturday 12 November 2005 20:43: Z2h0Z2Vhci1kZXZlbAo+IDJmNTg1ZWVlYTAyZTJjNzlkN2IxZDhjNDk2M2JhZTJkCj4KCgoKLS0K PEFydGh1ci8+Ci0gaHR0cDovL3NvdXJjZWZvcmdlLm5ldC91c2Vycy9hcnRvb3JvLwotIGh0dHA6 Ly9hcnRvb3JvLmJsb2dzcG90LmNvbQo= So, why are you posting this crap ? Please stop it, This is very standard base64 encoding. Every semi-decent mailer should be able to display this. Of course, it would be better in readable ASCII, but I wouldn't say it's crap. Your mailer *is* crap! :-P Hey, what's wrong with ed /var/mail/curt ... Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
On 11/12/05, Curtis L. Olson [EMAIL PROTECTED] wrote: Melchior FRANZ wrote: * Martin Spott -- Saturday 12 November 2005 20:43: Z2h0Z2Vhci1kZXZlbAo+IDJmNTg1ZWVlYTAyZTJjNzlkN2IxZDhjNDk2M2JhZTJkCj4KCgoKLS0K PEFydGh1ci8+Ci0gaHR0cDovL3NvdXJjZWZvcmdlLm5ldC91c2Vycy9hcnRvb3JvLwotIGh0dHA6 Ly9hcnRvb3JvLmJsb2dzcG90LmNvbQo= So, why are you posting this crap ? Please stop it, This is very standard base64 encoding. Every semi-decent mailer should be able to display this. Of course, it would be better in readable ASCII, but I wouldn't say it's crap. Your mailer *is* crap! :-P Hey, what's wrong with ed /var/mail/curt ... Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Hey Martin. Complain to Gmail maybe. I actually just figured out now how to send ASCII. Plain Text. Before all it did was remove formatting. So if it makes you happier I'll do so from now on. -- Arthur/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
Jon Stockill wrote: Curtis L. Olson wrote: How about a spyware popup ... Oh I see you just typed the word Paris, here are some great hotel + airfare combinations you might be interested in, and would you like me to search ebay for berets? No, not spyware - clippy :-) Jon ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Hi! I've just noticed that you are in a flat spin. Would you like me to open the help browser for you? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
Hello Melchior, Melchior FRANZ wrote: This is very standard base64 encoding. Every semi-decent mailer should be able to display this. Of course, it would be better in readable ASCII, but I wouldn't say it's crap. Your mailer *is* crap! :-P You know as good as I do that by common practice encoded emails don't belong into mailing lists - unless explicitly stated. Today we have base64 encoded mails, maybe tomorrow sombody thinks he'd post uuencoded mails he and tells us that every semi-decent mailer should be able to display this - which is to the same grade correct as your statement is. But all this doesn't change the fact that encoded emails in a mailing list are a nuisance. I wrote Arthur privately before and he simply didn't respond at all. Every semi-decent list member should do this, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: OT: FYI, mac os x developers,
* Curtis L. Olson -- Saturday 12 November 2005 21:03: Hey, what's wrong with ed /var/mail/curt ... Hey, and what's wrong with mimencode -u and recode utf8:latin1? As I said: it would be nicer in ASCII, but base64 isn't an offense, unlike HTML, fullquoting, topposting, which are the real annoyances on the net. :-P m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
On 11/12/05, Martin Spott [EMAIL PROTECTED] wrote: Hello Melchior, Melchior FRANZ wrote: This is very standard base64 encoding. Every semi-decent mailer should be able to display this. Of course, it would be better in readable ASCII, but I wouldn't say it's crap. Your mailer *is* crap! :-P You know as good as I do that by common practice encoded emails don't belong into mailing lists - unless explicitly stated. Today we have base64 encoded mails, maybe tomorrow sombody thinks he'd post uuencoded mails he and tells us that every semi-decent mailer should be able to display this - which is to the same grade correct as your statement is. But all this doesn't change the fact that encoded emails in a mailing list are a nuisance. I wrote Arthur privately before and he simply didn't respond at all. Every semi-decent list member should do this, Martin, like I said in the other thread, I never received a private email from you. Unless it's in the spam folder. Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Arthur/ - http://sourceforge.net/users/artooro/ - http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
Yeah, oops what's wrong with topposting? ;) On 11/12/05, Melchior FRANZ [EMAIL PROTECTED] wrote: * Curtis L. Olson -- Saturday 12 November 2005 21:03: Hey, what's wrong with ed /var/mail/curt ... Hey, and what's wrong with mimencode -u and recode utf8:latin1? As I said: it would be nicer in ASCII, but base64 isn't an offense, unlike HTML, fullquoting, topposting, which are the real annoyances on the net. :-P The fact is most people do whatever is default for their mailer. For me it's encoding and replies are top posted. These settings make sense for most people although some choose to live in the stone age. For GMail users not replying at the top and just cutting into the body like this is a real annoyance :) m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Arthur/ - http://sourceforge.net/users/artooro/ - http://artooro.blogspot.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: OT: FYI, mac os x developers,
* Martin Spott -- Saturday 12 November 2005 21:33: You know as good as I do that by common practice encoded emails don't belong into mailing lists - Sure, just like HTML, top-posting, full-quoting, Yet it happens. I tell people once to follow the rules, but if they don't and don't have anything relevant to say, either, they simply end up in my killfile. I'm not overly worried to miss an important message. And as long as even core developers send top-posted fullquoted messages, it's hard to throw stones anyway. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
Martin Spott wrote: Hello Melchior, Melchior FRANZ wrote: This is very standard base64 encoding. Every semi-decent mailer should be able to display this. Of course, it would be better in readable ASCII, but I wouldn't say it's crap. Your mailer *is* crap! :-P You know as good as I do that by common practice encoded emails don't belong into mailing lists - unless explicitly stated. Today we have base64 encoded mails, maybe tomorrow sombody thinks he'd post uuencoded mails he and tells us that every semi-decent mailer should be able to display this - which is to the same grade correct as your statement is. But all this doesn't change the fact that encoded emails in a mailing list are a nuisance. I wrote Arthur privately before and he simply didn't respond at all. Every semi-decent list member should do this, Martin. Ok, Ok. Enough of this. Clearly we need to send out all of our e-mails rot13 encoded. It's the only way that nobody has objected to, so it must be the only sane solution :) Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Review
I probably would do, but I don't have any experience with Atlas at all, so I'm unable to give appropriate response to the questions that I suppose will follow It's pretty straightforward, just give it a try following the WWW instructions. Be sure to use the CVS version and not the last released one, please --- much more stable and less autoconf problems. http://atlas.sourceforge.net/ On a low-end 3D card you probably want either to use a very small window for atlas, or even split atlas over to another computer from the FGFS. Be sure to use the lowres tiles, too --- see the Installing and Running page there. HTH, Vassilii ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] openAL compilation problem
Hi, I'm trying to compile pre-rel-3 in MSVC 7 but i'm running into a linking problem again. It looks to me like simgear is unable to read the openAL header files while trying to link. I have put them in the sound_mngr directory and modified the include statements to read it directly from there, but with no luck. Am I doing something wrong? Thanks! Linker Output == Generating non-SAFESEH image. main.obj : error LNK2019: unresolved external symbol __imp__alListenerf referenced in function public: void __thiscall SGSoundMgr::set_volume(float) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) fg_fx.obj : error LNK2001: unresolved external symbol __imp__alListenerf SimGear.lib(soundmgr_openal.obj) : error LNK2001: unresolved external symbol __imp__alListenerf main.obj : error LNK2019: unresolved external symbol __imp__alListenerfv referenced in function public: void __thiscall SGSoundMgr::set_listener_pos(float *) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alListenerfv referenced in function public: static char * __cdecl std::char_traits::move(char *,char const *,unsigned int) ([EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alDopplerVelocity referenced in function public: __thiscall SGSoundMgr::SGSoundMgr(void) (??0SGSoundMgr@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alDopplerFactor referenced in function public: __thiscall SGSoundMgr::SGSoundMgr(void) (??0SGSoundMgr@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alGetError referenced in function public: __thiscall SGSoundMgr::SGSoundMgr(void) (??0SGSoundMgr@@[EMAIL PROTECTED]) SimGear.lib(sample_openal.obj) : error LNK2001: unresolved external symbol __imp__alGetError SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alcMakeContextCurrent referenced in function public: __thiscall SGSoundMgr::SGSoundMgr(void) (??0SGSoundMgr@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alcCreateContext referenced in function public: __thiscall SGSoundMgr::SGSoundMgr(void) (??0SGSoundMgr@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alcOpenDevice referenced in function public: __thiscall SGSoundMgr::SGSoundMgr(void) (??0SGSoundMgr@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alcDestroyContext referenced in function public: __thiscall SGSoundMgr::~SGSoundMgr(void) (??1SGSoundMgr@@[EMAIL PROTECTED]) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alcSuspendContext referenced in function public: void __thiscall SGSoundMgr::pause(void) ([EMAIL PROTECTED]@@QAEXXZ) SimGear.lib(soundmgr_openal.obj) : error LNK2019: unresolved external symbol __imp__alcProcessContext referenced in function public: void __thiscall SGSoundMgr::resume(void) ([EMAIL PROTECTED]@@QAEXXZ) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol _alutUnloadWAV referenced in function public: __thiscall SGSoundSample::SGSoundSample(char const *,char const *,bool) (??0SGSoundSample@@[EMAIL PROTECTED]@Z) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol __imp__alBufferData referenced in function public: __thiscall SGSoundSample::SGSoundSample(char const *,char const *,bool) (??0SGSoundSample@@[EMAIL PROTECTED]@Z) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol _alutLoadWAVFile referenced in function public: __thiscall SGSoundSample::SGSoundSample(char const *,char const *,bool) (??0SGSoundSample@@[EMAIL PROTECTED]@Z) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol __imp__alGenBuffers referenced in function public: __thiscall SGSoundSample::SGSoundSample(char const *,char const *,bool) (??0SGSoundSample@@[EMAIL PROTECTED]@Z) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol __imp__alDeleteBuffers referenced in function public: __thiscall SGSoundSample::~SGSoundSample(void) (??1SGSoundSample@@[EMAIL PROTECTED]) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol __imp__alSourcePlay referenced in function public: void __thiscall SGSoundSample::play(bool) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol __imp__alSourcei referenced in function public: void __thiscall SGSoundSample::play(bool) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) SimGear.lib(sample_openal.obj) : error LNK2019: unresolved external symbol __imp__alSourceStop referenced in function public: void __thiscall SGSoundSample::play(bool) ([EMAIL PROTECTED]@@[EMAIL PROTECTED]) SimGear.lib(sample_openal.obj) : error LNK2019:
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
On 11/12/05, Arthur Wiebe [EMAIL PROTECTED] wrote: Yeah, oops what's wrong with topposting? ;) Ok, I'm sorry to extend a very off-topic discussion, but here I go anyway... This one is a little lost on me. I understand why quoting whole messages, and using HTML or various encoding schemes can be a nuisance, but to me it is easier to write and read replies at the top of the old message. I suppose if you are looking back in an archive, it might make more sense to read oldest to newest from top to bottom. But that seems like a pretty easy adjustment. So what is the argument here against topposting? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: OT: FYI, mac os x developers,
Jeff McBride [EMAIL PROTECTED] writes: On 11/12/05, Arthur Wiebe [EMAIL PROTECTED] wrote: adjustment. So what is the argument here against topposting? http://www.caliburn.nl/topposting.html --alex-- -- | I believe the moment is at hand when, by a paranoiac and active | | advance of the mind, it will be possible (simultaneously with | | automatism and other passive states) to systematize confusion | | and thus to help to discredit completely the world of reality. | ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
Jeff McBride wrote: This one is a little lost on me. I understand why quoting whole messages, and using HTML or various encoding schemes can be a nuisance, but to me it is easier to write and read replies at the top of the old message. I suppose if you are looking back in an archive, it might make more sense to read oldest to newest from top to bottom. But that seems like a pretty easy adjustment. So what is the argument here against topposting? Topposting makes only more sense, when you are too lazy to quote selectively instead of just quoting the whole mail (probably including signatures and ads...). And to have some context is not only nice when reading through an archive, but also when reading a lot of mail each day. So it's the easies if you can just open a mail, read a few lines to know what the topic is and then read the answer to that and not to open a mail, read a sentence, have no clue what it's talking about, scrolling to below and start searching for some this vital info. Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Review
From: Martin Spott Vassilii Khachaturov wrote: Maybe some German-speaking user could point the reporters to Atlas for the moving map solution they describe as absent [...] I probably would do, but I don't have any experience with Atlas at all, so I'm unable to give appropriate response to the questions that I suppose will follow Martin, you're welcome to respond and mention me for further questions. I'd rather have someone whose German grammar is less rusty than mine respond ... initially at least. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
On Sat, 2005-11-12 at 19:31 +, Jon Stockill wrote: Curtis L. Olson wrote: How about a spyware popup ... Oh I see you just typed the word Paris, here are some great hotel + airfare combinations you might be interested in, and would you like me to search ebay for berets? No, not spyware - clippy :-) Jon Hehe Hi, It looks like you are trying to pilot a plane. Would you like to... or Restart all systems a few seconds later.. Okay... restarting all systems.. George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] 0.9.9 scenery?
Martin Spott wrote: ftp://ftp.ihg.uni-duisburg.de/FlightGear/Devel/BaseObjects.tgz Acccording to my tests this package is indeed ready for inclusion, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] no 3d clouds?
I am unable to get 3d clouds with todays CVS for FlightGear and data and SimGear. I am running via fgrun and 3D clouds is checked and --enable-clouds3d is in the list under the show command line window. I also ran fgfs from the command line with --enable-clouds3d and still no 3D clouds. In the Render menu, it looks like the 3D Clouds is grayed out. Is this now a hard wired default in CVS? ... Dave Perry ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] OT: A380 arrived in EDHI (Hamburg-Finkenwerder)
George Patterson wrote: Hi, It looks like you are trying to pilot a plane. Would you like to... or Restart all systems a few seconds later.. Okay... restarting all systems.. You know that something similar _really _happened to one V-22 Osprey !? They have hydraulics for every single propeller blade which results in a very narrow structure in the propeller hubs. By accident one hydraulic tube was rubbing against an electrical cable and started leaking. The resulting loss of hydraulic pressure was accidentally misinterpreted !! by some computer on board which indicated an error to the pilots where the reboot of a certain computer system is listed as the required procedure. After restart this computer, which apparently is tied to the FCM, accidentally misinterpreted !! the current flight attitude and lead to actuator controls which crashed the plane :-(( Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] FlightGear Review
Alex Perry wrote: From: Martin Spott Vassilii Khachaturov wrote: Maybe some German-speaking user could point the reporters to Atlas for the moving map solution they describe as absent [...] I probably would do, but I don't have any experience with Atlas at all, so I'm unable to give appropriate response to the questions that I suppose will follow Martin, you're welcome to respond and mention me for further questions. I'd rather have someone whose German grammar is less rusty than mine respond ... initially at least. I'll write them. As a native speaker my German should be sufficient and before I learned to use VOR and ILS I used Atlas for navigation and still for lookup of frequencies. Nine ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] no 3d clouds?
I am unable to get 3d clouds with todays CVS for FlightGear and data and SimGear. I am running via fgrun and 3D clouds is checked and --enable-clouds3d is in the list under the show command line window. I also ran fgfs from the command line with --enable-clouds3d and still no 3D clouds. In the Render menu, it looks like the 3D Clouds is grayed out. Is this now a hard wired default in CVS? Surely not, because render/enable 3d clouds and the cmdline option do work here for me on Linux. I would love to help you with the fgrun setup, but I was unable to compile it here --- see my lament at http://sourceforge.net/mailarchive/forum.php?thread_id=8954364forum_id=39103 Vassilii ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
Stefan Seifert wrote: Topposting makes only more sense, when you are too lazy to quote selectively instead of just quoting the whole mail (probably including signatures and ads...). And to have some context is not only nice when reading through an archive, but also when reading a lot of mail each day. So it's the easies if you can just open a mail, read a few lines to know what the topic is and then read the answer to that and not to open a mail, read a sentence, have no clue what it's talking about, scrolling to below and start searching for some this vital info. I can share one little story. At a company I used to work for, there was a long thread of discussion about something between a bunch of managers. In the course of the conversation the messages and replies were top posted, bottom posted, multiple comments inserted in the middle in some of the quoted messages ... stacked up layer upon layer since this conversation had gone on quite a while. It's hard to even explain but one person top posted, then next person bottom posts quoting everything from before, and on and on about 15 levels deep. So at the end of the day, my manager forwards me this huge mish mash of nonsense and says, Please fix, see attached. I spent the next whole day trying to disassemble the message and the various layers to try to reconstruct the original conversation. Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] error:Unknown exception in the main loop
hi everyone i compiled flightgear with studio net 2003 . But when i execute the program says Unknown exception in the main loop. Aborting... Possible Cause: No error after i compiled fg ,it gaves me freeglut error then i switch to vers 2.2 from 2.4. Then it says i am using 9.8 base data version but i use fgfs-base-.9.9-pre3.tar.bz2. I didnt really understand where fg looks so in the code i make a shortcut with static char required_version[] = 0.9.8; then i get the unknown excdption error. any idea? _ Don't just search. Find. Check out the new MSN Search! http://search.msn.click-url.com/go/onm00200636ave/direct/01/ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database
On Thu, 10 Nov 2005 14:11:00 -0600, Curtis wrote in message [EMAIL PROTECTED]: I should also point out that the next scenery build (which is happening concurrent to the v0.9.9 release and causing my head to spin 3x faster than normal (not factoring in beer)) will be based on this data export. ..how much size growth, compared to the (0.9.7?) last scenery? (url to the new?) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] LibGL error
On November 11, 2005 07:26 pm, Ampere K. Hardraade wrote: I am also getting GLXUnsupportedPrivateRequest error. This is so darn annoying! I used to be able to get around this problem by migrating back to XFree, or failing that, start XServer under 16-bit depth. Now, I can't go with either option: Debian has moved onto Xorg, and SDL doesn't allow me to run OpenGL application under 16-bit depth. I am also using ATI card -- ATI 9200 SE to be precise. Ampere Okay. So far, I have tried: Using the CVS version of Xorg -- no luck. Using the CVS version of Mesa -- no luck. Other OpenGL applications seem to run fine. It's only FlightGear that crashed with the GLXUnsupportedPrivateRequest error during launch. Any idea how I can get around the problem? Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] error:Unknown exception in the main loop
Unknown exception in the main loop. Aborting... Possible Cause: No error This makes me report the following seemingly related sighting that I had today in the middle of something else, w/o exploring it until the end (I did mention it on the IRC earlier today). I've seen a couple of Failed to open file messages w/o a file, and decided to hunt for that one. It looks like this is only thrown from within simgear, but always with a path. Closer examination reveals that easyxml.cxx throws it, and uses the same pattern as JSB and I had recently agreed to be problematic --- dynamically creating things on the stack and throwing them! Either I managed to persuade JSB in a wrong C++ fact (I'm not 100% sure about it), or each and every throw throughout simgear and flightgear must be reviewed and such usages rewritten. One might argue that this is smth that only aids in error recovery in already screwed up situations, but some exceptions might be thrown to indicate non-globally-fatal situations --- i.e., without looking at every such place we can't be sure. Vassilii ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Pending v0.9.9 release
On Thu, 10 Nov 2005 10:32:22 + (UTC), Martin wrote in message [EMAIL PROTECTED]: Erik Hofman wrote: Martin Spott wrote: RANTWe know exactly this phenomenon for several years now and to my [...] supporters for this idea./RANT Guess why the next release is 0.9.9 and not 1.0 and why 1.0 is released early next year? ...some time after 0.9.10, 0.9.11, 0.9.12, 0.9.13... Yep, but sipmly _delaying_ the next release doesn't cure anything. This only makes sense if the developers agree on a feature freeze and announce a bugfix-only phase. ..or if it can be enforced somehow. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Pending v0.9.9 release
Yep, but sipmly _delaying_ the next release doesn't cure anything. This only makes sense if the developers agree on a feature freeze and announce a bugfix-only phase. ..or if it can be enforced somehow. ;o) or that a separate branch is created for the feature freeze while the development continues at the trunk, with only hand-picked patches getting into the release branch... ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
On Saturday 12 November 2005 21:48, Melchior FRANZ wrote: * Martin Spott -- Saturday 12 November 2005 21:33: You know as good as I do that by common practice encoded emails don't belong into mailing lists - Sure, just like HTML, top-posting, full-quoting, Yet it happens. I tell people once to follow the rules, but if they don't and don't have anything relevant to say, either, they simply end up in my killfile. Just a suggestion: Maybe it is a good idea to put some of the important rules on the http://www.flightgear.org/mail.html webpage so people can read them, before they subscribe to the mailinglists. Best Regards, Oliver C. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database
Arnt Karlsen wrote: On Thu, 10 Nov 2005 14:11:00 -0600, Curtis wrote in message [EMAIL PROTECTED]: I should also point out that the next scenery build (which is happening concurrent to the v0.9.9 release and causing my head to spin 3x faster than normal (not factoring in beer)) will be based on this data export. ..how much size growth, compared to the (0.9.7?) last scenery? (url to the new?) I haven't really started building a lot of tiles yet. I'm still hung up on a shapefile processing issue. Might be shade bigger, but I'm not expecting a huge difference ... Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
Just a suggestion: Maybe it is a good idea to put some of the important rules on the http://www.flightgear.org/mail.html webpage so people can read them, before they subscribe to the mailinglists. Good idea, in case someone really is annoyed with top-posts/encodes etc. Such folks are welcome to check-out the www module from the flightgear CVS, change the appropriate HTML, validate it, and send the patch over to Curt. Curt also likes the web pages' modified full text sent over as well, along with the patch, due to the way the website is now managed. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: OT: FYI, mac os x developers,
On Sun, 2005-11-13 at 03:51 +0200, Vassilii Khachaturov wrote: Just a suggestion: Maybe it is a good idea to put some of the important rules on the http://www.flightgear.org/mail.html webpage so people can read them, before they subscribe to the mailinglists. Good idea, in case someone really is annoyed with top-posts/encodes etc. Such folks are welcome to check-out the www module from the flightgear CVS, change the appropriate HTML, validate it, and send the patch over to Curt. Curt also likes the web pages' modified full text sent over as well, along with the patch, due to the way the website is now managed. This is the first time that someone gave me some insight about how to fg.org web page is managed, not that I asked explicitly on this list. Thanks Vassilii :-) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Pending v0.9.9 release
On Sun, 13 Nov 2005 03:24:21 +0200 (IST), Vassilii wrote in message [EMAIL PROTECTED]: Yep, but sipmly _delaying_ the next release doesn't cure anything. This only makes sense if the developers agree on a feature freeze and announce a bugfix-only phase. ..or if it can be enforced somehow. ;o) or that a separate branch is created for the feature freeze while the development continues at the trunk, with only hand-picked patches getting into the release branch... ...with some release dictator growling Test this! ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Announcement: First TerraGear landcover database
On Sat, 12 Nov 2005 19:48:37 -0600, Curtis wrote in message [EMAIL PROTECTED]: Arnt Karlsen wrote: ..how much size growth, compared to the (0.9.7?) last scenery? (url to the new?) I haven't really started building a lot of tiles yet. I'm still hung up on a shapefile processing issue. Might be shade bigger, but I'm not expecting a huge difference ... ..thanks. :o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
