Re: [Flightgear-devel] Patch to fix a crash on sound manager when a sound file is not found, etc.
Tatsuhiro Nishioka wrote: > Hi, > > Thanks for committing my patch, Erik. > >> Could you file a bug report at Apple? >> Returning an error number when calling alGetError that is not supported >> by alGetString() is a no-go. > > I filed a bug report, but I don't think Apple will change their code. > > Fortunately or unfortunately, alGetString works as OpenAL specification > claims. Sure but alGetError doesn't, it is only supposed to return OpenAL error codes which it clearly doesn't at this time. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Patch to fix a crash on sound manager when a sound file is not found, etc.
Hi, Thanks for committing my patch, Erik. > Could you file a bug report at Apple? > Returning an error number when calling alGetError that is not supported > by alGetString() is a no-go. I filed a bug report, but I don't think Apple will change their code. Fortunately or unfortunately, alGetString works as OpenAL specification claims. It returns 0 (NULL) when Invalid enum value is passed. So, application side must check the return value of alGetString since it does return NULL even though passing a non-enum error to alSetError is a No-Go. On Jan 5, 2010, at 1:26 AM, James Turner wrote: > Ah, I just noticed your (Erik's) commit, never mind. > > I also note the error code on Mac is -43 which I have a horrible feeling > might be the original File Manager 'file not found' code, from 1983. I wonder > if someone is passing an OSStatus directly out of a system call to the OpenAL > wrapper. As you wonder, OpenAL-MacOSX sometimes passes OSStatus value to alSetError, so not only -43 but many others can also be returned. Very bad! -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Copyrights
I've been doing research into copyrights and am shocked to see there is no (C) (years)-2010 FlightGear anywhere in FGRun or in the main flight simulation program. However, it appears looking through a sample of the source code the code is indeed (C) (year) by the authors who wrote it. This makes sense, considering the contributors to the project hold the copyright, unless the contributors agree to assign their copyright to an entity (FlightGear). I don't think this has happened, but it should. By assigning the copyright to FlightGear instead of the contributor who contributed a part of the work, this helps FlightGear move forward to help defend the software legally - and the original developer still has the right to use that part of the code they contributed elsewhere, as long as you don't grant anyone an exclusive license to use the code. We should also revise the fgrun and fgfs components to include (C) 2001-2010 FlightGear in visible areas. I'd add something to the menus - probably the file menu - in fgfs called "About" with the following text, if the copyright is unified: -- This software (C) 2001-2010 FlightGear Licensed under the GPLv2. Contribute to FlightGear! Visit our website at http://www.flightgear.org/ for more information. -- On fgrun, and if there are any installation programs we currently use, there should be a similar copyright notice. If I've completely missed where these notices are, please let me know, but this is important to help protect our software. Cheers John -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [bug fix] Re: bug with taxiway signs
> Hi all, > > Can we please not make a release with most (if not all) runway signs > broken? > > Csaba has the solution here: > > http://gitorious.org/~jester/fg/jesters-sg-clone/commit/34f1d5cda72e754e8f9 > 92e06c3f1ba66ffee9ab3 > > Can somebody commit this? Done! > > Short answer: Torsten has broken it in rev 1.23 of apt_signs.cxx :) Oups - sorry... Please check if it's fixed now. Torsten -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] [bug fix] Re: bug with taxiway signs
Hi all, Can we please not make a release with most (if not all) runway signs broken? Csaba has the solution here: http://gitorious.org/~jester/fg/jesters-sg-clone/commit/34f1d5cda72e754e8f992e06c3f1ba66ffee9ab3 Can somebody commit this? Cheers, Anders On Tue, 8 Dec 2009, Csaba Halász wrote: On Tue, Dec 8, 2009 at 12:55 PM, Jacob Burbach wrote: For example, excuse the crude ascii drawings if you will ;) Taxiing up Bravo towards Alpha and Juliet (KLVK) with 1.9.1 you will see these signs...correct. | <-- A[B] | [ <-- J[B] | But in cvs letters for Alpha and Bravo will be missing, and you will see these signsnot so correct. | <--[B] | | <--[B] | This effects all signs, at all airports I tried, release or terrasync scenery Thanks for the detailed report. Short answer: Torsten has broken it in rev 1.23 of apt_signs.cxx :) Longer answer: we need to keep the previous material and reuse it for subsequent glyphs that don't specify a new material. Thus, the material/effects variables should be put back at the top, but initialized to 0. -- --- Anders Gidenstam WWW: http://www.gidenstam.org/FlightGear/-- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows Build Problems
Hi Geoff, Good to hear from you and thanks for the Windows build web site. I can see you have put a lot of time and effort into your posts. I'll be sure to send any build questions but for now we need to run a bunch of assessment tests to verify that FG can provide the tools needed for FAA / AATD Certification with the C172. Initial observation looks good, except for no Instructor Station. I'm investigating what kind of effort it will take for us to develop an IOS and writing some drivers for our hardware. If you have any build updates for Windows please let us know. Thanks! Christian FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: christ...@freedomworks.ca www.FreedomWorks.ca -Original Message- From: Geoff McLane [mailto:ubu...@geoffair.info] Sent: Monday, January 04, 2010 1:16 PM To: FlightGear developers discussions Cc: Vivian Meazza Subject: Re: [Flightgear-devel] Windows Build Problems Hi Christian, Yes, sorry my 'Build Center' is so out of date. I hope to add an update over the coming days... and will blip you when I do. And, as part of that will include updated - \project\VC90 build files, plus new config.h.msvc files, as well as my own all-in-one 'system' build... and binaries are included... We have recently had a few major 'systems' overhauls in CVS, but are hopefully headed towards a new release this month... and my last WIN32 build felt pretty 'stable' As Vivian points out, 'It’s not entirely straightforward for the first build,' nice understatement ;=()... due to the fact that, except perhaps for OpenAL SDK, you must download and compile ALL the prerequisites sources in WIN32. But as also pointed out, if you have any specific problems, errors, then either contacts us directly, or through this board, and we will try to help... Regards, Geoff. SITE: http://geoffair.net/fg/fgfs-047.htm On Mon, 2010-01-04 at 11:29 -0500, Christian Menge wrote: > Vivian, > Thanks for responding to my note. > > We have only have this week possibly next to review FG and make a > decision about moving forward or not with AATD certification. If you > could send us a current build that would help with the immediate > requirements. > > If we decide to use FG with our flight simulation hardware I will do > what I can to help with updating the Windows build Wiki as this will > be out development platform. > > Cheers! > > Christian > > FreedomWorks Inc. > > US: 609-858-2290 > Canada: 905-228-0285 > Fax: 347-296-3666 > Email: christ...@freedomworks.ca > www.FreedomWorks.ca > > From: Vivian Meazza [mailto:vivian.mea...@lineone.net] > Sent: Monday, January 04, 2010 11:09 AM > To: 'FlightGear developers discussions' > Subject: Re: [Flightgear-devel] Windows Build Problems > > Christian, > > FG-cvs build on MSVC9 is indeed broken atm – I have forward a patch to > Tim Moore, but it seems to have gone down a black hole in hyperspace. > > Geoff McLane’s instructions more or less work, the ones on the wiki > have definitely been overtaken by events. > > That said, I can let you have a binary of the latest cvs-head (after > my patch), or the solution/project files which I currently use. Or you > might like to paste the errors that you are getting somewhere. > > It’s not entirely straightforward for the first build, but thereafter > it’s a piece of cake (until some Linux dev pulls it all apart again J) > > HTH > > Vivian > > -Original Message- > From: Christian Menge [mailto:christ...@freedomworks.ca] > Sent: 04 January 2010 15:57 > To: flightgear-devel@lists.sourceforge.net > Subject: [Flightgear-devel] Windows Build Problems > > Dear Dev, > > I hope this is the proper place to post this question. If not please > direct to the appropriate list / forum. > > We are currently looking into AATD certification (C172) of FlightGear. > Certification requires use of the GPS system and I have been told that > means we must use Windows. I have spent the better part of a day using > the Wiki instructions at FG web site and Geoff McLane’s on how to > build on Windows but neither works. > > Is there anyone that can give us some direction as to building for > Windows? > > Cheers! > > Christian Menge > > FreedomWorks Inc. > > US: 609-858-2290 > Canada: 905-228-0285 > Fax: 347-296-3666 > Email: christ...@freedomworks.ca > www.FreedomWorks.ca > -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows Build Problems
Hi Christian, Yes, sorry my 'Build Center' is so out of date. I hope to add an update over the coming days... and will blip you when I do. And, as part of that will include updated - \project\VC90 build files, plus new config.h.msvc files, as well as my own all-in-one 'system' build... and binaries are included... We have recently had a few major 'systems' overhauls in CVS, but are hopefully headed towards a new release this month... and my last WIN32 build felt pretty 'stable' As Vivian points out, 'It’s not entirely straightforward for the first build,' nice understatement ;=()... due to the fact that, except perhaps for OpenAL SDK, you must download and compile ALL the prerequisites sources in WIN32. But as also pointed out, if you have any specific problems, errors, then either contacts us directly, or through this board, and we will try to help... Regards, Geoff. SITE: http://geoffair.net/fg/fgfs-047.htm On Mon, 2010-01-04 at 11:29 -0500, Christian Menge wrote: > Vivian, > Thanks for responding to my note. > > We have only have this week possibly next to review FG and make a > decision about moving forward or not with AATD certification. If you > could send us a current build that would help with the immediate > requirements. > > If we decide to use FG with our flight simulation hardware I will do > what I can to help with updating the Windows build Wiki as this will > be out development platform. > > Cheers! > > Christian > > FreedomWorks Inc. > > US: 609-858-2290 > Canada: 905-228-0285 > Fax: 347-296-3666 > Email: christ...@freedomworks.ca > www.FreedomWorks.ca > > From: Vivian Meazza [mailto:vivian.mea...@lineone.net] > Sent: Monday, January 04, 2010 11:09 AM > To: 'FlightGear developers discussions' > Subject: Re: [Flightgear-devel] Windows Build Problems > > Christian, > > FG-cvs build on MSVC9 is indeed broken atm – I have forward a patch to > Tim Moore, but it seems to have gone down a black hole in hyperspace. > > Geoff McLane’s instructions more or less work, the ones on the wiki > have definitely been overtaken by events. > > That said, I can let you have a binary of the latest cvs-head (after > my patch), or the solution/project files which I currently use. Or you > might like to paste the errors that you are getting somewhere. > > It’s not entirely straightforward for the first build, but thereafter > it’s a piece of cake (until some Linux dev pulls it all apart again J) > > HTH > > Vivian > > -Original Message- > From: Christian Menge [mailto:christ...@freedomworks.ca] > Sent: 04 January 2010 15:57 > To: flightgear-devel@lists.sourceforge.net > Subject: [Flightgear-devel] Windows Build Problems > > Dear Dev, > > I hope this is the proper place to post this question. If not please > direct to the appropriate list / forum. > > We are currently looking into AATD certification (C172) of FlightGear. > Certification requires use of the GPS system and I have been told that > means we must use Windows. I have spent the better part of a day using > the Wiki instructions at FG web site and Geoff McLane’s on how to > build on Windows but neither works. > > Is there anyone that can give us some direction as to building for > Windows? > > Cheers! > > Christian Menge > > FreedomWorks Inc. > > US: 609-858-2290 > Canada: 905-228-0285 > Fax: 347-296-3666 > Email: christ...@freedomworks.ca > www.FreedomWorks.ca > -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows Build Problems
Vivian, Thanks for responding to my note. We have only have this week possibly next to review FG and make a decision about moving forward or not with AATD certification. If you could send us a current build that would help with the immediate requirements. If we decide to use FG with our flight simulation hardware I will do what I can to help with updating the Windows build Wiki as this will be out development platform. Cheers! Christian FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: christ...@freedomworks.ca www.FreedomWorks.ca From: Vivian Meazza [mailto:vivian.mea...@lineone.net] Sent: Monday, January 04, 2010 11:09 AM To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] Windows Build Problems Christian, FG-cvs build on MSVC9 is indeed broken atm - I have forward a patch to Tim Moore, but it seems to have gone down a black hole in hyperspace. Geoff McLane's instructions more or less work, the ones on the wiki have definitely been overtaken by events. That said, I can let you have a binary of the latest cvs-head (after my patch), or the solution/project files which I currently use. Or you might like to paste the errors that you are getting somewhere. It's not entirely straightforward for the first build, but thereafter it's a piece of cake (until some Linux dev pulls it all apart again J) HTH Vivian -Original Message- From: Christian Menge [mailto:christ...@freedomworks.ca] Sent: 04 January 2010 15:57 To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Windows Build Problems Dear Dev, I hope this is the proper place to post this question. If not please direct to the appropriate list / forum. We are currently looking into AATD certification (C172) of FlightGear. Certification requires use of the GPS system and I have been told that means we must use Windows. I have spent the better part of a day using the Wiki instructions at FG web site and Geoff McLane's on how to build on Windows but neither works. Is there anyone that can give us some direction as to building for Windows? Cheers! Christian Menge FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: christ...@freedomworks.ca www.FreedomWorks.ca -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Patch to fix a crash on sound manager when a sound file is not found, etc.
On 4 Jan 2010, at 16:08, James Turner wrote: > So while it's definitely worth reporting the bug, we still need to work > around the issue, using Tat's patch Ah, I just noticed your (Erik's) commit, never mind. I also note the error code on Mac is -43 which I have a horrible feeling might be the original File Manager 'file not found' code, from 1983. I wonder if someone is passing an OSStatus directly out of a system call to the OpenAL wrapper. Regards, James -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Windows Build Problems
Christian, FG-cvs build on MSVC9 is indeed broken atm - I have forward a patch to Tim Moore, but it seems to have gone down a black hole in hyperspace. Geoff McLane's instructions more or less work, the ones on the wiki have definitely been overtaken by events. That said, I can let you have a binary of the latest cvs-head (after my patch), or the solution/project files which I currently use. Or you might like to paste the errors that you are getting somewhere. It's not entirely straightforward for the first build, but thereafter it's a piece of cake (until some Linux dev pulls it all apart again :-)) HTH Vivian -Original Message- From: Christian Menge [mailto:christ...@freedomworks.ca] Sent: 04 January 2010 15:57 To: flightgear-devel@lists.sourceforge.net Subject: [Flightgear-devel] Windows Build Problems Dear Dev, I hope this is the proper place to post this question. If not please direct to the appropriate list / forum. We are currently looking into AATD certification (C172) of FlightGear. Certification requires use of the GPS system and I have been told that means we must use Windows. I have spent the better part of a day using the Wiki instructions at FG web site and Geoff McLane's on how to build on Windows but neither works. Is there anyone that can give us some direction as to building for Windows? Cheers! Christian Menge FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: christ...@freedomworks.ca www.FreedomWorks.ca -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Patch to fix a crash on sound manager when a sound file is not found, etc.
On 4 Jan 2010, at 14:55, Erik Hofman wrote: > Could you file a bug report at Apple? > Returning an error number when calling alGetError that is not supported > by alGetString() is a no-go. As has been noted by other folks, the Apple OpenAL is open-source, but unfortunately Apple are (very) bad at accepting patches, based on my reading of the default device bug. So while it's definitely worth reporting the bug, we still need to work around the issue, using Tat's patch. James -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Windows Build Problems
Dear Dev, I hope this is the proper place to post this question. If not please direct to the appropriate list / forum. We are currently looking into AATD certification (C172) of FlightGear. Certification requires use of the GPS system and I have been told that means we must use Windows. I have spent the better part of a day using the Wiki instructions at FG web site and Geoff McLane's on how to build on Windows but neither works. Is there anyone that can give us some direction as to building for Windows? Cheers! Christian Menge FreedomWorks Inc. US: 609-858-2290 Canada: 905-228-0285 Fax: 347-296-3666 Email: christ...@freedomworks.ca www.FreedomWorks.ca -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Patch to fix a crash on sound manager when a sound file is not found, etc.
Tatsuhiro Nishioka wrote: > Hi there, > > I found a bug in sound manager that crashes fgfs. > > The crash occurs when a designated wav file is not found. Could you file a bug report at Apple? Returning an error number when calling alGetError that is not supported by alGetString() is a no-go. Erik -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] adding CenturyIIB and CenturyIII to AP list in gui.nas
> On Wed, Dec 30, 2009 at 2:21 PM, dave perry wrote: > > Hi, > > > > Does anyone object to graying out the autopilot menu for tw additional > > autopilots used by several aircraft? > > I would suggest introducing an enable switch for the generic > autopilot, the state of which would be reflected in the menu status as > well. Specific autopilots could then disable the generic one. Ideally, > the generic autopilot shouldn't even get loaded - I'd exile it from > preferences.xml to the aircraft files. If an aircraft doesn't have a > custom autopilot it should load the generic one explicitly. > > I'd even consider simply moving the menu disable call itself into the > specific autopilot nasal files a better solution than listing special > cases in gui.nas. > Dave, I have just commited a modified version of your patch. Autopilot names are still hardcoded into gui.nas but probably easier to maintain. And I added a property /autopilot/hide-menu that, if set at startup, hides the autopilot menu item. I have tested several aircraft with success but not all. As ever: please complain if I broke anything. @Csaba: as far as I discovered, the generic autopilot is not loaded, if an aircraft specific autopilot is configured in the -set.xml file? This still does not disable the autopilot menu, however. I did not dare to disable the menu item, if the autopilot is not the generic one because individual autopilots might want to see the menu item. Maybe the current solution is a good compromise. Happy new Year! Torsten -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
