On Monday 08 October 2012 02:20:25 James Turner wrote: > On 8 Oct 2012, at 07:47, ThorstenB wrote: > > On 7 Oct 2012, at 15:19, Stuart Buchanan wrote: > >> The use-case is to enable or disable particular views if you don't want > >> to have to spend ages cycling through them. > > > > I also quite like this option. Some a/c also provide many additional > > custom views. It's handy to just enable the personal favourites. > > Okay - I guess since my yoke has a button bound to 'cycle views' I've got > used to rapidly clicking through.
I have a button bound, but still frequently turn off a few views... > > Personal taste: I'd keep the views named as "views" and just merge the > > dialogs. > > Yep, definitely gets my vote. One issue might be, since aircraft can define > custom views, making the dialog a sensible proportion. But I don't believe > many aircraft define more than an extra 4-5? I'm against merging views and rendering dialogs. They perform two distinctly different functions. Views simply select which views are cycled through and rendering options gets into much detailed and global changes to the way the flightgear world looks. Please don't overload grandpa! Thanks, Ron ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
