Re: [Flightgear-devel] Code Typo?
From: Patrick Quirk Hopefully I'm not too out of date with this since I'm looking at 0.9.8 code and am not an active CVS watcher. In file Main/viewer.cxx, in function MakeVIEW_OFFSET(...), on line ~118 where the third matrix is being made, there is the following line: tmp = t * axis2[1]; Since this is making the third matrix from the third angle, shouldn't this line be: tmp = t * axis3[1]; I'd assume this has been fixed on CVS but don't have the time to set it up and look, hopefully someone more involved in the dev process could check on this one real quick. Also is there an archive of this list or a bug database that allows searching through it? Hi Patrick, Good catch. The Offset angles are generated by the mouse and keyboard panning functions. The heading-offset-deg and pitch-offset-deg angles are modified when you use the mouse to rotate the view left and right or up and down, respecitvely (i.e. when the pilot looks around). The roll axis angle (matrix 3) is just in there for completeness, but it actually isn't used anywhere. That is why the fix doesn't appear to have any effect. And it does waste a few cycles. But then so does the whole function most of the time. We could probably just fill with identity values if there are no offsets, but then considering all the multiplications currently done per frame, that would not amount to much. e.g. 1 0 0 0 0 1 0 0 0 0 1 0 0 0 0 1 Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Code Typo?
Hopefully I'm not too out of date with this since I'm looking at 0.9.8 code and am not an active CVS watcher. In file Main/viewer.cxx, in function MakeVIEW_OFFSET(...), on line ~118 where the third matrix is being made, there is the following line: tmp = t * axis2[1]; Since this is making the third matrix from the third angle, shouldn't this line be: tmp = t * axis3[1]; I'd assume this has been fixed on CVS but don't have the time to set it up and look, hopefully someone more involved in the dev process could check on this one real quick. Also is there an archive of this list or a bug database that allows searching through it? begin:vcard fn:Patrick Quirk n:Quirk;Patrick email;internet:[EMAIL PROTECTED] tel;work:919-962-1715 x-mozilla-html:FALSE version:2.1 end:vcard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Code Typo?
Citeren Patrick Quirk [EMAIL PROTECTED]: I'd assume this has been fixed on CVS but don't have the time to set it up and look, hopefully someone more involved in the dev process could check on this one real quick. Also is there an archive of this list or a bug database that allows searching through it? The archives can be searched at the bottom of this page: http://www.flightgear.org/mail.html. Greets, Steven ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Code Typo?
On Wednesday 06 Jul 2005 20:50, Patrick Quirk wrote: In file Main/viewer.cxx, in function MakeVIEW_OFFSET(...), on line ~118 where the third matrix is being made, there is the following line: tmp = t * axis2[1]; It's still in there... You don't have to do a cvs checkout to view the current state of any file, by the way, there's an interactive browser at http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/?cvsroot=FlightGear-0.9 Cheers, AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Code Typo?
Ah, nifty tool that CVS browser, thanks :) So am I correct in thinking that's a typo? I haven't had time to change it and test it myself, thats for tomorrow, though I can't imagine too many bad things could happen (its amazing it works with that typo to begin with). AJ MacLeod (email lists) wrote: On Wednesday 06 Jul 2005 20:50, Patrick Quirk wrote: In file Main/viewer.cxx, in function MakeVIEW_OFFSET(...), on line ~118 where the third matrix is being made, there is the following line: tmp = t * axis2[1]; It's still in there... You don't have to do a cvs checkout to view the current state of any file, by the way, there's an interactive browser at http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/FlightGear/?cvsroot=FlightGear-0.9 Cheers, AJ ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d begin:vcard fn:Patrick Quirk n:Quirk;Patrick email;internet:[EMAIL PROTECTED] tel;cell:919-260-9918 x-mozilla-html:FALSE version:2.1 end:vcard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Code Walkthrough
John Pitz wrote: Hello, I have decided to try something simpler than attacking the problem of the plane flipping over, so I thaught I would try adding functionality to quickly change the latitude/longitude and optionally altitude. I realize all of these things are simple to change through the property browser, but it may be a bit more user friendly to change them from a menue. I have that basic functionality working but I would like to send the contents of the altitude box to a function that would determine whether the box is empty or not. If the box is blank, then the intent is that the plane would be warped to that lat/lon at ground level for that lat/lon. I'm not sure this is a trivial task because after positioning you need to retrim the aircraft to the new position ... It appears that if the above were possable, then I would have to write a command and put it in fg_commands in the Main source dir, is this correct? Or you could add a command later int the code, but for this I would have chosen to add it there indeed. By the way, thank you Jim for answering my previous posting. The next feature that I think would be nice is the ability to change aircraft while the program is running, if that is possable. Would either of these simple features warrent including in the Flightgear distro? This is definitely not a trivial task. I've started working on it some time ago but let it rest (for now) because of the difficulties (again) with resetting the various subsystems. The other day I was thinking of something that could be nice for starters but I don't seem to remember it anymore :-( Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Code Walkthrough
Please excuse my ignorance here, I actually know very little about aircraft, other than they are quite expensive, both to buy and to learn to fly, but what entails re-trimming the aircraft to the new position? John Pitz On Fri, 2003-08-29 at 05:28, Erik Hofman wrote: John Pitz wrote: Hello, I have decided to try something simpler than attacking the problem of the plane flipping over, so I thaught I would try adding functionality to quickly change the latitude/longitude and optionally altitude. I realize all of these things are simple to change through the property browser, but it may be a bit more user friendly to change them from a menue. I have that basic functionality working but I would like to send the contents of the altitude box to a function that would determine whether the box is empty or not. If the box is blank, then the intent is that the plane would be warped to that lat/lon at ground level for that lat/lon. I'm not sure this is a trivial task because after positioning you need to retrim the aircraft to the new position ... It appears that if the above were possable, then I would have to write a command and put it in fg_commands in the Main source dir, is this correct? Or you could add a command later int the code, but for this I would have chosen to add it there indeed. By the way, thank you Jim for answering my previous posting. The next feature that I think would be nice is the ability to change aircraft while the program is running, if that is possable. Would either of these simple features warrent including in the Flightgear distro? This is definitely not a trivial task. I've started working on it some time ago but let it rest (for now) because of the difficulties (again) with resetting the various subsystems. The other day I was thinking of something that could be nice for starters but I don't seem to remember it anymore :-( Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Code Walkthrough
David Megginson writes: John Pitz writes: Please excuse my ignorance here, I actually know very little about aircraft, other than they are quite expensive, both to buy and to learn to fly, but what entails re-trimming the aircraft to the new position? Trim tabs are control surfaces on control surfaces -- they change the default position of the surface when you release the controls. Most airplanes have elevator trim; most twins have aileron and rudder trim as well (as do some singles). There is also the concept of ground and air trimming which refers to a procedure that runs the flight dynamics without actually moving the aircraft and then adjusting the control inputs to balance out the forces. That way when you free the dynamics to actually move you start out in a steady state. This is kind of complicated magic that the aero people know how to do, but most of the rest of us don't. If the plane flips over or does other wierd things on reset, then there is probably something failing in the trim routine, or something on the flightgear side is telling the trim routine to do the wrong thing ... i.e. trim for flight when we want to be on the ground, trim for the ground, but giving the wrong ground elevation, etc. etc. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Code Walkthrough
Hello, I have decided to try something simpler than attacking the problem of the plane flipping over, so I thaught I would try adding functionality to quickly change the latitude/longitude and optionally altitude. I realize all of these things are simple to change through the property browser, but it may be a bit more user friendly to change them from a menue. I have that basic functionality working but I would like to send the contents of the altitude box to a function that would determine whether the box is empty or not. If the box is blank, then the intent is that the plane would be warped to that lat/lon at ground level for that lat/lon. It appears that if the above were possable, then I would have to write a command and put it in fg_commands in the Main source dir, is this correct? By the way, thank you Jim for answering my previous posting. The next feature that I think would be nice is the ability to change aircraft while the program is running, if that is possable. Would either of these simple features warrent including in the Flightgear distro? John Pitz ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Code Walkthrough
Hello everyone, I am a bit new to FlightGear. I am hoping to contribute to the coding, and was told to fly around and work on things that I think would be beneficial to add. Well, I have quite a few ideas, and they don't seem like they would be terribly difficult but the problem is I am not used to looking at other people's code. I am having a lot of trouble getting an idea as to the program flow of FlightGear. For example, one of the first things I noticed was that when you choose file|reset with the default plane the plane is deposited at the end of the runway upside down making it difficult to take off normally ;). Seemed that this would be a good place to start. Anyway, I am having trouble tracing the program flow from where the user clicks reset to what is done to the plane. I have played around with the menubar.xml file, but am unable to locate any reference to old-reinit-dialog. I have 2 versions of FlightGear installed, one is 0.9.2 that I use regularly fly in, and a fairly recent CVS version- from last Sunday, I believe, that I am trying to use for developement. I am using Red Hat Linux 8.0. If anyone has a little bit of extra time could they email me any kind of tutorial as to how the program works? I would be very grateful and hopefully a helpful contributer to this project. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Code
Jon Berndt wrote: Is there a way to determine which methods/attributes in a class are unused by anybody? I'm thinking maybe there's a utility out there somewhere or a link directive. This would assist in code streamlining/cleanup. Other than grep :-) You can browse through lists of references, looking for empty lists, in a source browser like the ones in MS Visual C++ and Source Navigator (formerly by Red Hat, now a SourceForge project). In MSVC you can only browse, as far as I know, but Source Navigator is open-source and uses Perl or Python scripts to do much of its user interface, so it's probably not hard to get it to output the list of unreferenced symbols. Others IDEs like KDevelop list definitions and declarations but not references. Getting the linker to tell you is an interesting idea that I haven't looked into. Perhaps you could do this manually by listing the public symbols in each library first, and then in the linked application, and comparing the two lists. Or perhaps you can make one list of all the exported symbols from the application and its libraries, and another list of all the imported symbols, and compare those. The unix utilities nm and objdump can list symbols in object files and libraries. I haven't come across a utility specifically for doing this, but I'd be interested. - Julian ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Code
Julian Foad writes: Jon Berndt wrote: Is there a way to determine which methods/attributes in a class are unused by anybody? I'm thinking maybe there's a utility out there somewhere or a link directive. This would assist in code streamlining/cleanup. Getting the linker to tell you is an interesting idea that I haven't looked into. Perhaps you could do this manually by listing the public symbols in each library first, and then in the linked application, and comparing the two lists. Or perhaps you can make one list of all the exported symbols from the application and its libraries, and another list of all the imported symbols, and compare those. The unix utilities nm and objdump can list symbols in object files and libraries. I haven't come across a utility specifically for doing this, but I'd be interested. This one got me thinking to :-) I am not familiar enough with the internals of the ld to know how todo this but this is EXACTLY the kind of thing that libbfd is for % info bfd ld can create a cross reference file that may be a good starting point for doing this by hand. The resulting cxref file lists all the functions sorted alphabetically and all of the object files that they are referenced from FGFCS::GetComponentName(int) ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) FGFCS::GetComponentOutput(int) ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) FGFCS::GetComponentStrings() ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) ../../src/FDM/JSBSim/libJSBSim.a(FGOutput.o) FGFCS::GetComponentValues() ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) ../../src/FDM/JSBSim/libJSBSim.a(FGOutput.o) FGFCS::GetDaCmd() const ../../src/FDM/JSBSim/libJSBSim.a(FGFCS.o) add -Wl,--cref to $LDFLAGS in the src/Main/Makefile if you want to experiment be warned this results in a large cxref file ~5 meg Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Code
Is there a way to determine which methods/attributes in a class are unused by anybody? I'm thinking maybe there's a utility out there somewhere or a link directive. This would assist in code streamlining/cleanup. Jon smime.p7s Description: application/pkcs7-signature
