On 01/03/2007 04:00 PM, Curtis Olson wrote: > we do want this to work intuitively so I would welcome > any changes to improve the in-air reposition dialog box.
:-) > I think it makes a lot > more sense to focus on the gui dialog box. Agreed. I'm coming at this from the perspective of an instrument flying lesson. Being able to reposition the aircraft a few miles from the initial approach fix saves a lot of time. > The reposition dialog box doesn't do any nasal, it just sets a bunch of > property values and calls the reset function. Yeah, I noticed that. The reset function is brutal. It trashes the pilot's trim settings and who-knows-what-all else. Also, currently location-in-air.xml trashes the throttle settings. The code doesn't explain why. Does anybody have an explanation? Is it to prevent the reset function from doing something even worse? > So in this case I think what needs to be done is to modify the reset > function (in a backwards compatible way) to understand the property > values that are set from the dialog box and do the right thing with them. I'm not sure thinking in terms of "reset" is the right approach. How about implementing a nice _relocate_ function, splitting it out as a function unto itself ... just changing location without resetting other stuff. The reset function can then make a structured reference to this relocate function. > I think there will need to be some support in the code for this. It's > easy to compute the local magnetic variation for some lon/lat, Doesn't it suffice to look at the /environment/magnetic-variation-deg node? That's what I did in my attempt, i.e. http://www.av8n.com/fly/fgfs/location-in-air.xml I suspect that if <offset>...</offset> were working at all, the magnetic-variation-deg part would have been OK. Or am I overlooking something else? > but the > dialog boxes just set property values and trigger internal function > calls (and maybe a bit of nasal here or there.) I still don't understand why <offset>...</offset> didn't work. I would have thought the property-setting that goes on in dialog boxes would be handled the same way as property-setting everywhere else. Is there some fundamental limitation here, or just an easy "opportunity for improvement"? > Our font has a very limited number of characters available so I don't > think [the degree] symbol is available. I can live without it. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
