Re: [Flightgear-devel] Blender UV mapping ( Inkscape)

2008-07-22 Thread Melchior FRANZ
* Heiko Schulz -- Tuesday 22 July 2008: [http://sourceforge.net/project/showfiles.php?group_id=6473] Yes- for python 2.2 - Blender 2.46 uses Python 2.5 If you look closely, then you see a version for 2.4 on that page. And because there's none for 2.5 I assume that the 2.4 one works for it as

Re: [Flightgear-devel] Blender UV mapping ( Inkscape)

2008-07-22 Thread Melchior FRANZ
* Melchior FRANZ -- Tuesday 22 July 2008: I assume that the 2.4 one works for it as well. OK, probably not. But the source is there, so you can build it yourself. Or you can change line 45 from from xml.sax import saxexts to from lxml.sax import saxexts ^ and try with lxml. Looks

Re: [Flightgear-devel] Blender UV mapping ( Inkscape)

2008-07-22 Thread Melchior FRANZ
* Heiko Schulz -- Tuesday 22 July 2008: Downloaded the matching lxm-package for python, changed like you proposed it here, but failed: cannot import name saxexts Argh. Sorry. I had tried before I suggested it, but I goofed and modified the wrong version. In which poor state is Python?! PyXML

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-07-13 Thread Melchior FRANZ
I've now closed two more security holes: 1. By setting an evil browser-app property and opening the browser help aircraft from questionable sources could execute arbitrary code in the calling shell under Unix: setprop(/sim/startup/browser-app, rm -rf ~ getprop(/sim/fg-home));

Re: [Flightgear-devel] particles: planned XML changes

2008-07-13 Thread Melchior FRANZ
This is now committed (simgear/scene/models/particles.[ch]xx) and all aircraft in CVS are adapted. Please report any problems. It's easily possible that I made a mistake somewhere, though I tried all concerned aircraft. Also note that I fixed some wrong tag names and suddenly parameters will be

[Flightgear-devel] particles: planned XML changes

2008-07-04 Thread Melchior FRANZ
Unfortunately, Tiago's particle system was committed with an IMHO suboptimal XML interface. I suggested some changes and Tiago agreed, but he then dropped off the list without implementing them. I'd like to do that myself now, and I'll adjust all uses of particle systems afterwards (later today

Re: [Flightgear-devel] icons

2008-06-28 Thread Melchior FRANZ
* Arnt Karlsen -- Thursday 26 June 2008: Shouldn't these icons be in our cvs|svn|git etc repositories? They do IMHO belong to the src package -- to the executable. Adding a top-level dir in the data package only for a few (not so pretty) icons wasn't a good idea, and the inconsistent

Re: [Flightgear-devel] CVS log : last post is 2008-06-09 07:57

2008-06-22 Thread Melchior FRANZ
* gerard robin -- Sunday 22 June 2008: In flightgear-cvslogs (http://sourceforge.net/mailarchive) I don't see any recent CVS update the last one is 2008-06-09 07:57 from Tim Moore. Are CVS data and source frozen ? No, but Curt had to set up a new server due to hardware problems. Since then

[Flightgear-devel] US: Digital Models Not Subject To Copyright

2008-06-22 Thread Melchior FRANZ
The US Court of Appeals for the Tenth Circuit has affirmed (PDF) a ruling that a plain, unadorned wireframe model of a Toyota vehicle is not a creative expression protected under copyright law. [...] companies that produce goods may not be able to stop modelers from imaging those products, but

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
I've locked the system further down. If people desire, then we can disable any file access by default. At the moment writing should only be possible with pattern ~/.fgfs/Export/* and ~/.fgfs/Scenery/*.stg. m. - Check out the

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 16 June 2008: I've locked the system further down. var read_rules = [ [root ~ /*, 1], [home ~ /*, 1], ]; var write_rules = [ [home ~ /Scenery/*.stg, 1], [home ~ /Export/*, 1], ]; The 1 means ALLOW, whereas 0 would mean

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
The rules are now read from $FG_ROOT/Nasal/IOrules or, if available, $FG_HOME/Nasal/IOrules. That way people who don't have write permission for $FG_HOME/Nasal/io.nas can still extend and modify the rules. The default is: READ ALLOW $FG_ROOT/* READ ALLOW $FG_HOME/* WRITE ALLOW

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
* Sven Almgren -- Monday 16 June 2008: Can't you just restrict the io to the $FG_HOME dir or something? Sure: READ ALLOW $FG_HOME/* WRITE ALLOW $FG_HOME/* like --io-read=/myDir --io-read=/tmp --io-write=/etc/passwd ? Any of the options overwrites a previous one with the same name, so

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 16 June 2008: At least for now we should be reasonably safe from evil people and have time to find better solutions. BTW: Why the sudden paranoia? Not that we should have waited much longer for some security enhancements in any case, but the fact that there seem now

Re: [Flightgear-devel] Bug in Livery handling

2008-06-16 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 16 June 2008: I know that bo105/plib are only correctly shown in fg/plib, and bo105/osg only in fg/osg. bo105/plib should now show up correctly in fg/osg (with random variant and special emblem). bo105/osg are not shown correctly in fg/plib, and probably never

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
It's funny that nobody cared a year long, and now that the danger is supposed to be banned, people get scared and nervous. :-} * Erik Hofman -- Monday 16 June 2008: (What are the reasons to write to a file anyway?) Writing non-PropertyList XML files, like they are used in the traffic manager

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 16 June 2008: Writing non-PropertyList XML files, like they are used in the traffic manager and for flight plans. Correction: not for flight plans -- these are PropertyLists. But for the other stuff like parking files etc. The power of a system isn't defined by what

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
* Erik Hofman -- Monday 16 June 2008: Maybe making sure the file ends with .xml could also help a lot. io.nas:113: writexml() if(substr(path, -4) != .xml) path ~= .xml; fg_commands.cxx:1365: do_save_xml_from_proptree() if (file.extension() != xml)

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-16 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 16 June 2008: * Erik Hofman -- Monday 16 June 2008: (What are the reasons to write to a file anyway?) Writing non-PropertyList XML files, like they are used in the traffic manager and for flight plans. Writing *.stg files (adding models or adjusting elevations

Re: [Flightgear-devel] Bug in Livery handling

2008-06-15 Thread Melchior FRANZ
Hi, now that it went to the list, I'll also reply here. :-) * Heiko Schulz -- Monday 16 June 2008: www.hoerbird.net/liveryhandling_mp_bug.png I know that bo105/plib are only correctly shown in fg/plib, and bo105/osg only in fg/osg. I didn't bother to make livery changing backwards compatible,

[Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-13 Thread Melchior FRANZ
It's well known that Nasal has an io module with wrappers around fopen(), fclose(), etc. An aircraft that you install, or even scenery objects with embedded Nasal could in the past use this to delete the contents of your whole home directory, or to append commands to ~/.bashrc, and thus execute

Re: [Flightgear-devel] [SECURITY] Nasal: io.open() restricted

2008-06-13 Thread Melchior FRANZ
* Csaba Halász -- Friday 13 June 2008: On Fri, Jun 13, 2008 at 2:01 PM, Melchior FRANZ [EMAIL PROTECTED] wrote: [A-Za-z]:TMP/, [A-Za-z]:TEMP/, [A-Za-z]:/TMP/, [A-Za-z]:/TEMP/, You might consider the TEMP and TMPDIR environment variables too. On Unix I'd even suggest to let

Re: [Flightgear-devel] last cvs getting error during FG build

2008-06-09 Thread Melchior FRANZ
* gerard robin -- Saturday 07 June 2008: AirportList.cxx:(.text+0xb40): undefined reference to `puaList::puaList(int, int, int, int, int)' Looks like you aren't using plib 1.8.5, which is now required. m. - Check out the

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4

2008-06-06 Thread Melchior FRANZ
* Frederic Bouvier -- Friday 06 June 2008: Moreover, you can't include a statement like using std::cerr; if std::cerr is not already defined. Just for the record: I had to modify a few files in fg/JSBSim as well to make it compile. On Linux! This may be because I'm using a different build

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4

2008-06-06 Thread Melchior FRANZ
* Tim Moore -- Friday 06 June 2008: [...] then I'd prefer that we'd say get JSBSim from the JSBSim CVS server like we do with plib. At the very least it should have imported on a vendor branch into our CVS so that local changes could be easily maintained. Solution in search of a problem? We

Re: [Flightgear-devel] FG menu bar small and no text?

2008-06-06 Thread Melchior FRANZ
* Simon Fowler -- Friday 06 June 2008: Is there a way to configure the use of alternate fonts from the command line (or .fgfsrc)? Yes. Try --prop:sim/gui/style[1]/fonts/gui/name=TIMES_24 (assuming that you are using style[1], which is the dark one). $FG_ROOT/gui/styles/*.xml tells you which

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4

2008-06-06 Thread Melchior FRANZ
* Tim Moore -- Friday 06 June 2008: Let me know what changes you have made and I'll resubmit my patch to JSBSim. The reason was: in the past the JSBSim in fgfs had to be compiled with -DFGFS, and there are #ifdef FGFS blocks in several of the JSBSim files. But these blocks are now obsolete and

Re: [Flightgear-devel] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp ...

2008-06-06 Thread Melchior FRANZ
* Jon S. Berndt -- Friday 06 June 2008: Are we saying that whacko constructs like this are no longer needed: #ifdef FGFS [...] I can only say that defining FGFS breaks compilation for me. Because I also noticed that fgfs doesn't use that anymore, because it's no longer in the Makefile.am

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4

2008-06-05 Thread Melchior FRANZ
* gerard robin -- Thursday 05 June 2008: Does this will be compatible with actual JSBSim development ? No, it will get overwritten with the next JSBSim update. There's a reason why commits to externally maintained parts of fgfs (nasal, jsbsim) used to be taboo, just like commits to parts which

Re: [Flightgear-devel] [Flightgear-cvslogs] CVS: source/src/FDM/JSBSim/models/flight_control FGActuator.cpp, 1.2, 1.3 FGFCSComponent.h, 1.3, 1.4

2008-06-05 Thread Melchior FRANZ
* Tim Moore -- Thursday 05 June 2008: I never got the memo that large parts of the tree were off limits. In the old days one didn't need memos for that. One had to be around long enough before one even got CVS access. Enough time to learn the rules. Not your fault, of course, that this has

Re: [Flightgear-devel] Patch to perform airport searches case-insensitively

2008-06-03 Thread Melchior FRANZ
* Stuart Buchanan -- Monday 02 June 2008: ... and here's the patch, based on Fred's original patch. Assuming it passes muster, could someone review and commit please? I fixed the bug[1] and committed it, thanks Fred Stuart! Though Fred's way to display the entries in upper case hides the

Re: [Flightgear-devel] Patch to perform airport searches case-insensitively

2008-06-02 Thread Melchior FRANZ
* Torsten Dreyer -- Tuesday 03 June 2008: Maybe a litte checkbox named Case sensitive search might give the user the freedom of choice? This adds one option without dropping the other. Widgets are associated with one single property, and they read from it after getting a dialog-update and

Re: [Flightgear-devel] Patch to perform airport searches case-insensitively

2008-06-02 Thread Melchior FRANZ
* Stuart Buchanan -- Monday 02 June 2008: Assuming it passes muster, [...] It doesn't. You are adding 2-space spaghetti code indentation to a file that uses 4 spaces. m. - This SF.net email is sponsored by: Microsoft Defy

Re: [Flightgear-devel] Patch to perform airport searches case-insensitively

2008-06-02 Thread Melchior FRANZ
* Curtis Olson -- Monday 02 June 2008: I may be completely misunderstanding this whole thread, but could we add another widget to the search dialog window that is tied to a boolean property. We could, but it would IMHO also be a bit unclean, as it would influence all airport-search widgets.

Re: [Flightgear-devel] Patch to perform airport searches case-insensitively

2008-06-02 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 02 June 2008: And before we do anything like that we should first decide if we *really* want and need the case sensitivity configurable. ... especially considering that we are having the discussion exactly because case-sensitivity turned out to be useless given

Re: [Flightgear-devel] Patch to perform airport searches case-insensitively

2008-06-02 Thread Melchior FRANZ
* Curtis Olson -- Tuesday 03 June 2008: Well assuming that we have agreed to switch over to a case insensitive search, I think we have. Takes another hour until I have compiled OSG 2.5.1 and the newest sg/fg changes, but then I'll commit Stuart's patch (after having fixed indendation and

Re: [Flightgear-devel] Patch to perform airport searches case-insensitively

2008-06-01 Thread Melchior FRANZ
* Stuart Buchanan -- Saturday 31 May 2008: +if (!_filter.empty() (strcasestr(entry.c_str(), _filter.c_str()) == NULL)) quote from 'man strcasestr': The strcasestr() function is a non-standard extension. I doubt that it's available on all supported platforms. m.

Re: [Flightgear-devel] Weekly CVS Changelog Summary: FlightGear data

2008-06-01 Thread Melchior FRANZ
* Curtis L. Olson -- Sunday 01 June 2008: 2f585eeea02e2c79d7b1d8c4963bae2d These summaries are often empty since a while, although several commits had been made. Looks like the mechanism is broken. m. - This SF.net email

Re: [Flightgear-devel] wxradar text

2008-06-01 Thread Melchior FRANZ
* SydSandy -- Saturday 17 May 2008: font properties are now under instrumentation/radar/font committed with some adjustments ( cosmetic changes, as always ;-) ... can be initialized in the set file like so ... instrumentation radar font

Re: [Flightgear-devel] Issue with texture-path tags.

2008-05-31 Thread Melchior FRANZ
* alexis bory -- Tuesday 27 May 2008: there is an issue with texture-path tags which can not be assigned on the fly. [...] The best would be to make the existing and very efficient aircraft.livery() able to work with a texture-path tag OR with with the currently available texture tag.

Re: [Flightgear-devel] FG menu bar small and no text?

2008-05-31 Thread Melchior FRANZ
* Holger Wirtz -- Saturday 31 May 2008: I will have a look at the transpareny fonts. Perhaps such a font is simply missing... It doesn't have anything to do with transparency as such, but only with texture fonts (*.txf) versus (built-in) bitmap fonts. The former are now apparently broken since

[Flightgear-devel] xmlsound: delay-sec

2008-05-21 Thread Melchior FRANZ
Often sounds consist of three parts: a preamble (e.g. turbine spool up sound), a looped sound (turbine sound), and a postable (turbine shutdown sound). In the past this had to be done with extra state properties written from Nasal, which would tell the loop when to start. Now there's a delay-sec

Re: [Flightgear-devel] new: live property display

2008-05-15 Thread Melchior FRANZ
All of the above is still true, but now I turned the property display dialog into a regular class, so you can also create your own temporary displays for development purposes. For example, to show a list of live-updated properties (separate from the global one described before), this is all you

Re: [Flightgear-devel] new: live property display

2008-05-15 Thread Melchior FRANZ
Here's a small screenshot: http://members.aon.at/mfranz/screen-display.jpg [18.2 kB] var display = screen.display.new(500, -100); display.setcolor(1, 0, 1); display.add(/position/latitude-deg, /position/longitude-deg); You can also select a different font, if you find the default

[Flightgear-devel] new: live property display

2008-05-14 Thread Melchior FRANZ
I've just added a developer feature that I've missed for a long time: a display where properties are shown and continuously updated. There are three ways to use it: (1) property browser: - Shift-click on a property to add the property to the display list - Shift-Ctrl-click on any

Re: [Flightgear-devel] CVS: source/src/Cockpit hud_rwy.cxx, 1.15, 1.16

2008-05-12 Thread Melchior FRANZ
* Durk Talsma -- Monday 12 May 2008: - Move Dave's original code to a new directory (ATCDCL) so we can recycle the original ATC directory for generic ATC functions. ARGHHH! Don't do that! You are basically thowing away the cvs history of the ATC/ files. Let Curt move the files on the

Re: [Flightgear-devel] CVS: source/src/Cockpit hud_rwy.cxx, 1.15, 1.16

2008-05-12 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 12 May 2008: You are basically thowing away the cvs history of the ATC/ files. Let Curt move the files on the server! Oh, well. Never mind. It's a pain in either case, and the history is preserved in the plib branch. :-) m

Re: [Flightgear-devel] CVS: source/src/Cockpit hud_rwy.cxx, 1.15, 1.16

2008-05-12 Thread Melchior FRANZ
* Curtis Olson -- Monday 12 May 2008: Isn't the history preserved in the attic for the files that are removed from one location and recreated in the next? Yes, but the copies don't have a history. But as the files in ATCDCL will be removed soon anyway, this isn't much of a problem. If we

Re: [Flightgear-devel] CVS: source/src/Cockpit hud_rwy.cxx, 1.15, 1.16

2008-05-12 Thread Melchior FRANZ
* Durk Talsma -- Monday 12 May 2008: One way or the other, I had a gut feeling you'd respond to my latest commit. ;-) Hehe ... was waiting all day long for something to shout at. ;-) And besides, apart from a nice to have, I have a gut feeling we won't be consulting the history on these

Re: [Flightgear-devel] CVS: source/src/Cockpit hud_rwy.cxx, 1.15, 1.16

2008-05-12 Thread Melchior FRANZ
* Curtis Olson -- Monday 12 May 2008: I'm not arguing that what we've done in the past is the best policy, but we do have NetworkOLK and WeatherCM. Yeah, and most people today don't know what OLK and CM mean. That's exactly the problem. m.

[Flightgear-devel] UFO object editing

2008-05-10 Thread Melchior FRANZ
I've in the last days added a new feature to the UFO. You are probably aware of the mouse walk thingy -- a way to navigate the UFO quickly with the MMB-dragging (Middle Mouse Button) in pointer mode. Now it's also possible to move and adjust objects that way, so that the adjust dialog isn't

Re: [Flightgear-devel] FG OSG 2.4 crashes

2008-05-10 Thread Melchior FRANZ
* Georg Vollnhals -- Saturday 10 May 2008: Due to changing my OS from OpenSUSE 10.2 to OpenSUSE 10.3 I built all components from CVS/SVN - they compiled without any problem! I run everything from CVS/SVN/HEAD on OpenSuSE 10.3 on an x86/32bit. Except: I use OpenAL from SuSE, because the SVN

Re: [Flightgear-devel] CVS: FlightGear/src/Main fg_commands.cxx, 1.99, 1.100

2008-05-08 Thread Melchior FRANZ
* Melchior Franz -- Wednesday 07 May 2008: Modified Files: fg_commands.cxx Log Message: revert accidental commit Of course this log message is nonsense, and it's fixed in CVS. The only accident here was with the git gateway, sorry. :-) + + /** + * Set mouse coordinates

Re: [Flightgear-devel] CVS: FlightGear/src/Main fg_commands.cxx, 1.100, 1.101

2008-05-08 Thread Melchior FRANZ
Sheesh ... another messed up log message: Merge branch 'master' of ../.fg.osg Of course, I fix such botched log messages in CVS, so you'll get the right thing with $ cvs log fg_commands.cxx. It's just hard to revoke the cvslogs mails. (I also fix bugs in the git gateway that cause such

Re: [Flightgear-devel] UFO Mouse Walk

2008-05-07 Thread Melchior FRANZ
* Melchior FRANZ -- Monday 05 May 2008: Ctrl+MMB: move up/down move left/right Ctl+MMB is no more. It's now: vertical horizontal MMB: walk forward/backward turn left/right MMB

[Flightgear-devel] UFO Mouse Walk

2008-05-05 Thread Melchior FRANZ
I've today added a walk mode to the UFO, which allows quick UFO repositioning with the mouse. That's much more convenient for scenery work. In normal mouse mode (arrow/pointer mode) press the middle mouse button (MMB) and drag (= move the mouse while keeping the button down).

Re: [Flightgear-devel] UFO Mouse Walk

2008-05-05 Thread Melchior FRANZ
* Christian Schmitt -- Monday 05 May 2008: Is there a way to manipulate positions of objects that are already positioned in the scenery via an stg file? No. stg models are handled by the scenery thread in a more efficient manner, while UFO edited objects are handled by the model manager.

Re: [Flightgear-devel] startup position

2008-05-02 Thread Melchior FRANZ
* Syd -- Friday 02 May 2008: I see some commited from Melchior that suggest he might be working on a solution, just not sure what that is yet :) Sorry, no. I'm not working on anything like that. Just fixed the missing-unit-suffix bug. (Though the distance should really be in meters internally,

Re: [Flightgear-devel] startup position

2008-05-02 Thread Melchior FRANZ
* LeeE -- Friday 02 May 2008: I am curious about why using the tail location as the visual reference point is abusing the FDM's internal reference system but using the nose is not. That's a misunderstanding. I didn't mean that one place is OK, and another is an abuse. What I meant to say is

Re: [Flightgear-devel] [Flightgear-users] Proved and maintainable methods

2008-05-02 Thread Melchior FRANZ
* Durk Talsma -- Friday 02 May 2008: You make it seem as if I deliberately refused to comply with a standard. However, that has never been an issue, because the groundnet parser predates most of the more advanced UFO based editing facilities. No, I didn't make it seem like you intentionally

Re: [Flightgear-devel] [PATCH] fix fixes ;)

2008-04-28 Thread Melchior FRANZ
* Csaba Halász -- Saturday 26 April 2008: Please review, test (especially that std::multimap works on all our supported platforms) [...] Thanks, committed. I didn't test on all supported platforms, but I guess we'll hear about problems. :-) I only made a very simple test on Linux. m.

Re: [Flightgear-devel] Screenshot improves

2008-04-27 Thread Melchior FRANZ
* Thomas Förster -- Sunday 27 April 2008: I overlooked the simgear patch. Next time, please put a note into the commit messages that a simgear update is required. No. It's basic knowledge that fg and sg are developed in parallel. It has been that way since *years*, and I don't think we'll

Re: [Flightgear-devel] Screenshot improves

2008-04-27 Thread Melchior FRANZ
* Thomas Förster -- Sunday 27 April 2008: According to sg_path.hxx 'create_dir' returns nothing (void), thus giving a conversion to bool error. Please fix. I suggest that you update your sg instead. $ cvs log -r1.12 sg_path.hxx [...] revision 1.12 date: 2008-04-26 17:25:31 +0200;

Re: [Flightgear-devel] fgrun can now reports fgfs failures

2008-04-27 Thread Melchior FRANZ
* Frederic Bouvier -- Sunday 27 April 2008: Of course, if someone knows how to do it in Linux, I will be more than happy to integrate it. In case you mean a stack-trace, there's a backtrace() function in GNU/libc. See man backtrace (includes example), or this file in the dftd repository:

Re: [Flightgear-devel] fgrun can now reports fgfs failures

2008-04-27 Thread Melchior FRANZ
* Frederic Bouvier -- Sunday 27 April 2008: It looks like your link is about the failed process prints its stack trace at the time of failure right ? Yes. No idea if it can also be used for cases like yours. I have not the least experience with it. m.

Re: [Flightgear-devel] osg 2.4 released today

2008-04-26 Thread Melchior FRANZ
* Melchior FRANZ -- Saturday 26 April 2008: I've removed a workaround for a modifier key handling bug in OSG 2.0, but I've only commented out one for a numlock key bug. OK. The numpad workaround wasn't a workaround, but really necessary. It's doesn't fix a bug in OSG. I uncommented that code

Re: [Flightgear-devel] Screenshot improves

2008-04-26 Thread Melchior FRANZ
* Nicolas -- Tuesday 08 April 2008: After precipitation patchs, I post a new patch about screenshot management. With this patch, you can choose the directory destination for the screenshots. Committed, thanks. Example: --prop:sim/paths/screenshot-dir=/tmp I moved it into a property dir

Re: [Flightgear-devel] [patch] database pager calm-down

2008-04-25 Thread Melchior FRANZ
* till busch -- Friday 25 April 2008: tim recently noticed the database pager was repeatedly loading and unloading the same objects. Yeah, I noticed as well. I had some not-so-pretty stuttering in the last time. I already feared that we'd have a new hesitation problem that would again be hard

Re: [Flightgear-devel] B-1B update

2008-04-25 Thread Melchior FRANZ
* Markus Zojer -- Friday 25 April 2008: Could someone apply that? Done, thanks. For me to commit updates there should be an archive with only updates and diffs (not *everything* again, every time!), and there should be no annoying top-level directory that prevents easy unpacking (see

[Flightgear-devel] osg 2.4 released today

2008-04-25 Thread Melchior FRANZ
And according to a past agreement, this means that everyone should from now on expect commits that require OSG 2.4 -- to add new features, and to remove old workarounds. Please don't send bug reports about sg/fg not compiling, if you haven't updated. m.

Re: [Flightgear-devel] view limiter...

2008-04-24 Thread Melchior FRANZ
* Syd -- Wednesday 23 April 2008: I'm enjoying this new view-limiter , but you realize now I have to do cabins for my aircraft ... :-P Just a thought , but what about a small forward / backward movement , too ... in case one needs to lean forward a bit (wing inspection), or would that

Re: [Flightgear-devel] helipad lighting (loxl)

2008-04-24 Thread Melchior FRANZ
* Csaba Halász -- Thursday 24 April 2008: [sophisticated lighting based on wind direction] Don't think it works that way. Damn. But maybe I should sell the idea, then?! :-) http://www.dot.ca.gov/hq/planning/aeronaut/documents/5390-2b.pdf That's interesting, thanks. I've for now only

[Flightgear-devel] helipad lighting (loxl)

2008-04-23 Thread Melchior FRANZ
Does anyone here know how helipad lighting typically works in a case like this? http://doris.ooe.gv.at/viewer/%28S%28lzssrqnmskruqee2yda3lcus%29%29/init.aspx?ks=alkkarte=gkkoord=62803.89;343426.49massstab=15000 It's sized 25x25m with 7x7 edge lights and 4 corner lights. I assume that,

Re: [Flightgear-devel] RFC: Unifying AIModels and ATC

2008-04-22 Thread Melchior FRANZ
* Durk Talsma -- Tuesday 22 April 2008: What I would like to do is phase out the existing ATC code, and adopt the good parts into the AIModels based ATC code. IIRC, David Luff, the original author of the ATC/AI code has expressed his approval to integrating his code into the AIModels

Re: [Flightgear-devel] Flash with altitude change

2008-04-21 Thread Melchior FRANZ
* Adam Dershowitz -- Monday 21 April 2008: I did make the minor change that Alex suggested in this discussion: [...] and then rebuilt and it seems to be working. Is that essentially the change that you were referring to? It's the correct thread. The fix isn't and will probably cause other

Re: [Flightgear-devel] foo-set.xml - foo-yasim-set.xml

2008-04-20 Thread Melchior FRANZ
* Syd -- Saturday 19 April 2008: can you name an example so I can see what you mean ? My vote would be to do something about it , so if mine are like this [...] I haven't looked closely, but I didn't refer to your aircraft. You get a good impression if you try this: $ ls

[Flightgear-devel] foo-set.xml - foo-yasim-set.xml

2008-04-19 Thread Melchior FRANZ
There are more and more aircraft in CVS with two *-set.xml files, where one is basically empty and only referring to a second one. This is understandable in cases where actually more than one FDM is used or very likely to be used in the next time. But it's becoming a problem if this redundant

Re: [Flightgear-devel] Flash with altitude change

2008-04-19 Thread Melchior FRANZ
* Curtis Olson -- Saturday 19 April 2008: I think Melchior is the expert on this subject. Hehe ... yes, kind of. It's probably the bug that I introduced shortly before and fixed again shortly after the 1.0 release. I don't think there's a way to fix it without recompiling. Smoothing will

Re: [Flightgear-devel] make osgviewer the default choice inconfigure

2008-04-18 Thread Melchior FRANZ
* Vivian Meazza -- Friday 18 April 2008: Tim Moore wrote: I'm inclined to commit this; are there any objections? Melchior, are you happy with the state of your patches in current OSG? Yes, I'm happy with the state and I'm not aware of remaining bugs. From my part: please go ahead! (I only

Re: [Flightgear-devel] make osgviewer the default choice in configure

2008-04-18 Thread Melchior FRANZ
* Tim Moore -- Friday 18 April 2008: are you happy with the state of your patches in current OSG? Err ... all my statements about the current state were based on OSG/SVN/*HEAD*, not the last stable release, which we officially require. But nowadays we should require OSG/HEAD for our development

[Flightgear-devel] pilot view restrictions

2008-04-15 Thread Melchior FRANZ
Pilot view is now restricted by default. You can no longer turn your head around like the obsessed girl in Exorcist, unless you disable the view limitation (/sim/view/config/limits/enabled). Additionally, if you turn the head farther than some configurable threshold, then a configurable sideways

Re: [Flightgear-devel] GPS update rate

2008-04-14 Thread Melchior FRANZ
* Curtis Olson -- Monday 14 April 2008: Let's say I want to do a simple moving average ... so the new value is (let's say) 9 parts the previous filtered value + 1 part of the latest sensor reading. Doing that as a simple average though will glitch if your values are coming in around 0/360.

Re: [Flightgear-devel] GPS update rate

2008-04-14 Thread Melchior FRANZ
* LeeE -- Monday 14 April 2008: I'm running a nasal loop at 1/(frame-rate/2), which typically works out to between 10-20 Hz, but because the gps update rate is much slower (0.45 sec if I'm interpreting the code correctly) the results aren't very smooth - the effect is that the results

Re: [Flightgear-devel] AI Aircraft Models

2008-04-13 Thread Melchior FRANZ
* till busch -- Thursday 10 April 2008: Currently Aircraft/ is ~1200 MB on cvs. So yes. I think we can easily afford 100 or 200 MB for cheap ai models. I don't mind spending 200MB for something useful. But I think that 200MB for a mere duplication of existing files is a waste. I'd opt for

[Flightgear-devel] FYI: EFF fights for the rights of 3D modellers against bogus trademark claims

2008-04-10 Thread Melchior FRANZ
http://www.johnmacneill.com/WWII_Bomber.html http://www.eff.org/deeplinks/2008/04/liberate-b-24-liberator m. - This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's

Re: [Flightgear-devel] FYI: EFF fights for the rights of 3D modellers against bogus trademark claims

2008-04-10 Thread Melchior FRANZ
* LeeE -- Thursday 10 April 2008: Thanks for posting that. BTW: the discussion about the first link is also interesting: http://www.boingboing.net/2008/03/21/wwii-bomber-trademar.html m. - This SF.net email is sponsored

Re: [Flightgear-devel] AI Aircraft Models

2008-04-09 Thread Melchior FRANZ
* Stuart Buchanan -- Wednesday 09 April 2008: - Use ImageMagick to convert any .rgb textures to png. We certainly don't want redundant texture duplicates in $FG_ROOT/AI/. Did you scale them down or do anything else that justifies this step? If not, then just refer to the original textures

Re: [Flightgear-devel] AI Aircraft Models

2008-04-09 Thread Melchior FRANZ
* Stuart Buchanan -- Wednesday 09 April 2008: As I mentioned in my reply to Vivian, I don't want any dependency on the Aircraft tree, You don't want that, fine. And *I* don't want a parallel structure of aircraft with megabytes of duplicated files. So, please let's discuss that first, before

Re: [Flightgear-devel] AI Aircraft Models

2008-04-09 Thread Melchior FRANZ
make my enemies ridiculous. And God granted it. -- Voltaire * Stuart Buchanan -- Wednesday 09 April 2008: --- On Wed, 9/4/08, Melchior FRANZ wrote: So, please let's discuss that first, before anyone dumps more of that stuff into $FG_ROOT/AI/! Hence my original post - discussion is good

Re: [Flightgear-devel] CVS - Data Re-organisation

2008-03-20 Thread Melchior FRANZ
* Vivian Meazza -- Wednesday 19 March 2008: A few days ago the data in cvs was reorganised with several directories being moved from Models to AI/Aircraft. As I said already in a direct reply to the cvslogs message, I also consider that a bad and uninformed move. The AI/ dir was created as a

Re: [Flightgear-devel] Multiple graphics card and displays on one machine

2008-03-15 Thread Melchior FRANZ
* Vikas N Kumar -- Saturday 15 March 2008: I was able to get the 3 screen thing working but the performance was quite bad. The load scenery objects took more than 2-3 minutes to load [...] You said that you were using everything from CVS/SVN. But this sounds a bit like you aren't using

[Flightgear-devel] $ fgfs --version

2008-03-15 Thread Melchior FRANZ
I've now committed a first stab at a --version option. In my copy it works like this: $ fgfs --version 2.0pre-20080314 FG_ROOT=/usr/local/share/FlightGear FG_HOME=/home/me/.fgfs .. but only because my build system sets VERSION in config.h to 2.0pre-build-date. For others this will

Re: [Flightgear-devel] Follow Me / Livery over MP

2008-03-15 Thread Melchior FRANZ
* Gijs de Rooy -- Friday 14 March 2008: I've used the livery selection system for that. But the problem is that I don't see the changes someone else made when multiplaying. So the livery isn't sended to the MP-servers I think. A vague description deserves a vague response: the livery system

Re: [Flightgear-devel] FG build fails with plib 1.8.5 and SLD

2008-03-15 Thread Melchior FRANZ
* Alasdair Campbell -- Saturday 15 March 2008: /usr/include/plib/puSDL.h:32:17: error: SDL.h: No such file or directory No sdl-devel installed, apparently. But using SDL is depreciated. Dump the --enable-sdl and use --enable-osgviewer instead and *only*. You can't have both. m.

[Flightgear-devel] [RFC] making plib 1.8.5 a requirement

2008-03-11 Thread Melchior FRANZ
Now that plib 1.8.5 has been released, I suggest to make it a requirement in fgfs/configure.ac. This doesn't only force people to use a version with fixed networking and joystick handling ... * Fixed netSocket. * Handle linux joysticks with a lot of axes. * several fixes and improvements to

Re: [Flightgear-devel] [RFC] making plib 1.8.5 a requirement

2008-03-11 Thread Melchior FRANZ
* LeeE -- Tuesday 11 March 2008: Or have I misunderstood the eventual intention? Yes. My intention is to go that smaller step first, and not the big one already. I can do the small one immediately, and *someone* can do the big one whenever s/he pleases. Could be you! :-} m.

Re: [Flightgear-devel] CVS: data/Models/Geometry/Nimitz catapult.rgb, 1.1, NONE crew_1.rgb, [...]

2008-03-11 Thread Melchior FRANZ
* Martin Spott -- Tuesday 11 March 2008: Removed Files: catapult.rgb crew_1.rgb crew_2.rgb crew_3.rgb deck-stripe.rgb [...] Log Message: Move AI ships into the AI department as well, adjust AI scenarios and docs (where appropriate). Err ... wasn't $FG_ROOT/AI/Aircraft/ meant to

Re: [Flightgear-devel] [RFC] making plib 1.8.5 a requirement

2008-03-11 Thread Melchior FRANZ
* Curtis Olson -- Tuesday 11 March 2008: I'm happy to see plib do another official release that includes many bug fixes. Yes lets definitely move forward and make our official dependency on plib-1.8.5 Thanks. For those who don't have it yet: http://plib.sourceforge.net/download.html or

Re: [Flightgear-devel] [RFC] making plib 1.8.5 a requirement

2008-03-11 Thread Melchior FRANZ
* LeeE -- Tuesday 11 March 2008: It'll just be a bit of a nuisance pulling out the standard version for my distro (luckily I have nothing else installed that depends upon it) on all my systems (7) and then installing from the tarball. No, you can leave that. Just install plib somewhere

Re: [Flightgear-devel] [RFC] making plib 1.8.5 a requirement

2008-03-11 Thread Melchior FRANZ
* Durk Talsma -- Tuesday 11 March 2008: From Steve's original message, I'm under the impression that something significant has happened that will allow him a lot more time for plib. Yes, for PLIB2. He's working on the successor already, and the description sounds a bit like OSG. But I don't

<    1   2   3   4   5   6   7   8   9   10   >