Re: [Flightgear-devel] Update FG Short Reference

2010-01-02 Thread YOSHIMATSU Toshihide
Hi all, From: Stuart Buchanan Subject: [Flightgear-devel] Update FG Short Reference Date: Sun, 13 Dec 2009 20:55:00 + (GMT) > I've spent an hour or so making the key assignments accurate and improving > the mouse mode description. An updated version is available here: > > http://www.nanjika

Re: [Flightgear-devel] intersection of two radials

2010-01-02 Thread Martin Spott
James Turner wrote: > My current implementation isn't working. At least one reason is the > note on sign conventions in the linked page - the Aviation Formulary > page uses west-is-positive, [...] Ouch ! Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are

[Flightgear-devel] intersection of two radials

2010-01-02 Thread James Turner
For some procedures work, I need to implement the following formula: http://williams.best.vwh.net/avform.htm#Intersection (Various other SGGeoc / SGGeodesy functions are taken from the same source) My current implementation isn't working. At least one reason is the note on sign conventi

Re: [Flightgear-devel] FlightGear Mac OS X 2.0.0-pre1 has been released.

2010-01-02 Thread Tatsuhiro Nishioka
Hi Peter, On 2010/01/02, at 1:46, Peter Brown wrote: Oops, sorry guys, didn't notice that was fg-devel list mail. embarrassed peter. It's OK. As you assume, a numbered version is given to an official stable release, and a dated cvs version is a snapshot release that has the latest and e

Re: [Flightgear-devel] Windows CVS update warnings

2010-01-02 Thread George Patterson
On Sun, Jan 3, 2010 at 12:40 AM, Csaba Halász wrote: > On Sat, Jan 2, 2010 at 2:23 PM, Alan Teeder > wrote: > > > > >From here I see the same as you with both A380.rgb and a380.rgb at > > http://cvs.flightgear.org/viewvc/data/Aircraft/A380/Models/ > > > > I deleted the A380 directory and re-ran C

Re: [Flightgear-devel] Windows CVS update warnings

2010-01-02 Thread Csaba Halász
On Sat, Jan 2, 2010 at 2:23 PM, Alan Teeder wrote: > > >From here I see the same as you with both A380.rgb and a380.rgb at > http://cvs.flightgear.org/viewvc/data/Aircraft/A380/Models/ > > I deleted the A380 directory and re-ran CVS, but no conflicts and A380.rgb > and not a380.rgb appeared in A38

Re: [Flightgear-devel] Windows CVS update warnings

2010-01-02 Thread Vivian Meazza
Alan Teeder wrote > > I am using TortoiseCVS > > >From here I see the same as you with both A380.rgb and a380.rgb at > http://cvs.flightgear.org/viewvc/data/Aircraft/A380/Models/ > > I deleted the A380 directory and re-ran CVS, but no conflicts and A380.rgb > and not a380.rgb appeared in A380/m

Re: [Flightgear-devel] Windows CVS update warnings

2010-01-02 Thread Alan Teeder
Geoff I am using TortoiseCVS >From here I see the same as you with both A380.rgb and a380.rgb at http://cvs.flightgear.org/viewvc/data/Aircraft/A380/Models/ I deleted the A380 directory and re-ran CVS, but no conflicts and A380.rgb and not a380.rgb appeared in A380/models. In the past I have

Re: [Flightgear-devel] Windows CVS update warnings

2010-01-02 Thread Geoff McLane
On Sat, 2010-01-02 at 10:45 +0100, Erik Hofman wrote: > Ubuntu Air wrote: > > Hi FG data cvs maintainers, > > > > When updating FG data in Windows, I continually, for > > quite some time now, get the following CVS warnings :- > > > > cvs update: move away Aircraft/A380/Models/a380.rgb; it is in t

Re: [Flightgear-devel] Windows CVS update warnings

2010-01-02 Thread Alan Teeder
I am not getting this so it seems that your CVS is confused, as Eric suggests. My CVS gets screwed up from time to time and I find the quickest and safest solution is to delete everything and start again. Don´t forget to keep your modified files before the delete. In this instance you only nee

Re: [Flightgear-devel] Windows CVS update warnings

2010-01-02 Thread Erik Hofman
Ubuntu Air wrote: > Hi FG data cvs maintainers, > > When updating FG data in Windows, I continually, for > quite some time now, get the following CVS warnings :- > > cvs update: move away Aircraft/A380/Models/a380.rgb; it is in the way It looks like you have local updates that have never been in