Re: [Flightgear-devel] Minor menu renaming
For newcomers I'd say it is essential that there are close buttons. When new users try out software they won't browse any documentation. And I'd say that many (most?) users would get confused without close buttons. This seems to be an important non-issue. Maybe there already is an expert option in fg, if not why not add one, and then use this option to generate different dialogues? Cheers, Jari Stuart Buchanan skrev 2010-12-28 01.44: On Mon, Dec 27, 2010 at 8:51 PM, Gijs de Rooy wrote: (Why) do we need two buttons to close a dialog? I recently removed the ones that say Close on most dialogs, replacing them with small buttons in the top right corner. There are quite some dialogs that don't have a normal close button (like Route manager, Aircraft help, Common keys, Property Browser). I personally very much prefer those. You are an expert user, who already knows that the unlabeled box in the top right corner is a button, and what it does. Don't over-estimate the computing knowledge of a new user - they have none of that knowledge, and simply won't know how to dismiss the dialog. Remember - the FG Plib-based FG UI is going to be quite alien to them, as it's not got the same look and feel to the window systems they might be used to. They aren't going to guess that the object in to the top right corner is a button that acts like the X button in the top right of their Windows box, assuming that they even use that. Putting this another way, I'm not aware of any other GUI targetted at non-expert users (i.e. people specifically trained to use that software) that does not provide a clearly labeled button (OK/Cancel/Close) to dismiss every single dialog box within the UI. Frankly, if I'd been aware that you'd removed all the Close buttons, I'd have complained very loudly. I consider that to be a serious usability regression. The reason I've left the top-right button in place is partly for consistency with some of the expert and long-lifed dialogs, and partly so that the top of the dialog box looks like a title bar, with the title of the dialog, the small close button, and a horizontal line. The Close buttons just take up space and block my view on the instruments and environment even more... The dialogs I have added it to are ones which a user will use and then dismiss. I have not added it to dialogs such as the MP Pilot List and Stopwatch, nor do I intend to add it to expert dialogs such as the Property Browser. What other dialogs do you leave open for prolonged periods while flying? IMO, much worse is cluttering up a new users display with dialogs that they cannot dismiss! :) We should teach our users to use the small button in topright corner, else they will have a problem in those dialogs that only have such small button. Besides that, less buttons make things look easier, something that FlightGear lacks accordint to a lot of users. How would you teach our new users? They don't read our documentation. We cannot teach our users to use a small unlabeled button in the top right corner. There simply has to be a clearly labeled button to close the dialog, which is what I'm attempting to ensure it present on all dialogs. On Mon, Dec 27, 2010 at 9:07 PM, Gary Neely wrote: I'd like to back Gijs up here. I've worked in usability studies, and these things make a difference in the user's experience. Minimizing clicking and placing buttons in consistent locations makes for a considerably more pleasant experience. I've also worked on usability studies. One consistent result from them is not to over-estimate the competance of the average user. The change I've made has improved consistency and usability by ensuring that there are clearly labeled buttons to dismiss the dialog on (almost) all the dialogs. I think I've covered all the XML dialogs. In my next pass, I'll go through and modify the C- and Nasal generated ones, with the exception of the dialogs that are clearly intended to remain active for a long time (pilot list, stopwatch), and dialogs targeted specifically at expert users, like the Property Browser. -Stuart -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise,
Re: [Flightgear-devel] Re-enabling ATCDCL
On Tue, Dec 28, 2010 at 3:18 AM, John Denker ... wrote: On 12/27/2010 03:59 PM, Dave L wrote: I can't see any downside to removing the conditional compilation completely now, but I'll leave it 24 hours to let anyone object. FWIW I have been using the non-default --enable-atcdcl option for a lot more than 24 hours, and I have no objections to making this the default. Just to be clear for everyone else, I'm proposing removing the conditional compilation and running *both* the ATIS and Durk's new traffic manager code, not just switching the default. There are a couple of trivial patches to make compiler warnings go away ... and a few almost-trivial enhancements at http://gitorious.org/~jsd/fg/sport-model/commits/atishttp://gitorious.org/%7Ejsd/fg/sport-model/commits/atis ... which has been recently rebased, so it should apply cleanly to the current next branch. Thanks, I'll apply them barring any unforeseen problems. Cheers - Dave -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Minor menu renaming
How about adding legendX/legend to the small close button? Torsten -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Problem with first build (again!!!)
Hey guys, I seem to be stuck at this forever. I know I previously said I've completed the first build but there was a missing .dll file prompt so I figured maybe something went wrong somewhere and tried to do the whole process again and lo and behold, this time my first built had failed even worse than before 1-- Build started: Project: SimGear, Configuration: Release Win32 -- 1Generation of simgear_config.h 1The system cannot find the file specified. 1Project : error PRJ0019: A tool returned an error code from Generation of simgear_config.h 1Build log was saved at file://h:\My Documents\FGFSDevel\SimGear\projects\VC90\Win32\Release\BuildLog.htm 1SimGear - 1 error(s), 0 warning(s) 2-- Build started: Project: yasim, Configuration: Release Win32 -- 3-- Build started: Project: UGsmooth, Configuration: Release Win32 -- 4-- Build started: Project: terrasync, Configuration: Release Win32 -- 5-- Build started: Project: MIDGsmooth, Configuration: Release Win32 -- 3Linking... 5Linking... 2Linking... 4Linking... 2LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 3LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 5LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 4LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 5Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\MIDGsmooth\Win32\Release\BuildLog.htm 5MIDGsmooth - 1 error(s), 0 warning(s) 3Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\UGsmooth\Win32\Release\BuildLog.htm 3UGsmooth - 1 error(s), 0 warning(s) 4Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\terrasync\Win32\Release\BuildLog.htm 2Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\yasim\Win32\Release\BuildLog.htm 2yasim - 1 error(s), 0 warning(s) 4terrasync - 1 error(s), 0 warning(s) 6-- Build started: Project: metar, Configuration: Release Win32 -- 7-- Build started: Project: GPSsmooth, Configuration: Release Win32 -- 6Linking... 7Linking... 7LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 6LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 6Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\metar\Win32\Release\BuildLog.htm 6metar - 1 error(s), 0 warning(s) 7Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\GPSsmooth\Win32\Release\BuildLog.htm 8-- Build started: Project: FlightGear, Configuration: Release Win32 -- 7GPSsmooth - 1 error(s), 0 warning(s) 9-- Build started: Project: fgviewer, Configuration: Release Win32 -- 10-- Build started: Project: fgjs, Configuration: Release Win32 -- 8Generation of config.h 9Linking... 10Linking... 10LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 9LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 8The system cannot find the file specified. 8Project : error PRJ0019: A tool returned an error code from Generation of config.h 8Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\FlightGear\Win32\Release\BuildLog.htm 8FlightGear - 1 error(s), 0 warning(s) 10Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\fgjs\Win32\Release\BuildLog.htm 9Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\fgviewer\Win32\Release\BuildLog.htm 10fgjs - 1 error(s), 0 warning(s) 9fgviewer - 1 error(s), 0 warning(s) 11-- Build started: Project: fgadmin, Configuration: Release Win32 -- 11Linking... 11LINK : fatal error LNK1181: cannot open input file '..\..\..\..\simgear\projects\vc90\win32\release\simgear.lib' 11Build log was saved at file://h:\My Documents\FGFSDevel\FlightGear\projects\VC90\fgadmin\Win32\Release\BuildLog.htm 11fgadmin - 1 error(s), 0 warning(s) == Build: 0 succeeded, 11 failed, 1 up-to-date, 0 skipped == I don't get it, I did what I did last time but I can't even get a single build to succeed :( Any suggestions? Anyway, just to introduce myself again. I'm a current aerospace undergraduate who is trying to complete her final year project which is to simulate wind shear on Flight Gear. Sadly, my progress is really slow due to my lack of experience software development. Here are the links of the mathematical models I'm suppose to model (especially the one on the downburst winds): Downburst wind: http://i739.photobucket.com/albums/xx38/debboo/CCF10202010_3.jpg Aircraft characteristics:
[Flightgear-devel] IAR-80 merge/update request
Hello everyone, I'm the developer of the IAR-80, and before this holidays season I've managed to get it to a state that I consider as production. I would like the latest version commited to GIT, if and when anyone has the time (hopefuly before the new release deadline :) ). zip package here: http://sag.ath.cx:6980/flightgear/IAR80-v1.0.zip or if the above doesn't work, here: http://sag.ath.cx:6980/flightgear/IAR80-v1.0.zip Latest cockpit shots here: http://www.flightgear.org/forums/viewtopic.php?p=107293#p107293 Thank you in advance, and A Happy New Year to everyone involved in FlightGear. Emilian -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Bug in model collision detection?
I'm having some trouble with collision detection not working properly on some models I'm working on. The models are made of a few different objects and while everything else works normally collision detection is not working on all the objects. I've attached a test model that illustrates the problem for me. Place the model somewhere (with ufo or whatever) and then try to fly aircraft through the different objects of the model. Here only the large box in the middle actually collides, and either of the smaller upper and lower objects I can simply pass through. Am I missing something obvious, is this a bug somewhere? cheers test.ac Description: Binary data ?xml version=1.0? PropertyList pathtest.ac/path !-- animation typerange/type object-nameupper/object-name min-m0/min-m max-m100/max-m /animation animation typerange/type object-namelower/object-name min-m0/min-m max-m100/max-m /animation animation typerange/type object-namemiddle/object-name min-m0/min-m max-m600/max-m /animation -- /PropertyList -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] IAR-80 merge/update request
woops: wrong alternate download link in the first mai, it should be this: http://rapidshare.com/files/438740862/IAR80-v1.0.zip On 12/28/10, Emilian Huminiuc emili...@gmail.com wrote: Hello everyone, I'm the developer of the IAR-80, and before this holidays season I've managed to get it to a state that I consider as production. I would like the latest version commited to GIT, if and when anyone has the time (hopefuly before the new release deadline :) ). zip package here: http://sag.ath.cx:6980/flightgear/IAR80-v1.0.zip or if the above doesn't work, here: http://sag.ath.cx:6980/flightgear/IAR80-v1.0.zip Latest cockpit shots here: http://www.flightgear.org/forums/viewtopic.php?p=107293#p107293 Thank you in advance, and A Happy New Year to everyone involved in FlightGear. Emilian -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bug in model collision detection?
Jacob Burbach wrote: I'm having some trouble with collision detection not working properly on some models I'm working on. The models are made of a few different objects and while everything else works normally collision detection is not working on all the objects. I've attached a test model that illustrates the problem for me. Place the model somewhere (with ufo or whatever) and then try to fly aircraft through the different objects of the model. Here only the large box in the middle actually collides, and either of the smaller upper and lower objects I can simply pass through. Am I missing something obvious, is this a bug somewhere? Collision detection? Er - we don't really have that. There is Height Over Terrain (HOT), which is on for scenery and AI objects by default, but not for Aircraft models. This will enable you to land on a building, but usually lets you fly through the walls, although you might also appear to collide with it. In any case the ufo can fly through anything: land - sea - buildings ... For objects placed one above the other as in your test case the results will be very uncertain. Hth Vivian -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Bug in model collision detection?
On Tue, Dec 28, 2010 at 1:32 PM, Vivian Meazza vivian.mea...@lineone.net wrote: Collision detection? Er - we don't really have that. There is Height Over Terrain (HOT), which is on for scenery and AI objects by default, but not for Aircraft models. This will enable you to land on a building, but usually lets you fly through the walls, although you might also appear to collide with it. By collision detection I was indeed referring to HOT functionality. I was not referring to aircraft models as I'm aware there is no collision or anything with those. I usually have no problems with being able to fly through walls or any other solid object. Usually causes a collision and aircraft to crash unless the geometry is very small. Does depend on aircraft, some work better than others of course. In this case the geometries above and below the central geometry have no collision whatsoever, while the central geometry itself does collide and cause a crash. In any case the ufo can fly through anything: land - sea - buildings ... I'm quite aware the ufo can fly through anything...which is why I said to place the model and then try flying an aircraft through it. ;) cheers -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Gitorious down?
On Wed, Dec 29, 2010 at 11:39 AM, Hal V. Engel hven...@gmail.com wrote: It appears that Gitorious is off-line. I can't get to the home page or any other pages (I get 503 Service Unavailable errors) and I can't do any updates to my repository. But I can ping both git.gitorious.org and gitorious.org. Anyone have any ideas what is going on or how long the outage will last? Hal Perhaps this is the background. http://blog.gitorious.org/2010/12/23/dns-fail/ Regards George -- Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
