I also know that quoting white-space paths works well in "command.com"
Windows shells. But apparently it didn't work when terrasync called the
"system" function to call "svn". Unfortunately I have no means to test
any of this on Windows.
The following patch seem to do the trick for me, it allow
On 23.06.2011 19:16, Vivian Meazza wrote:
> This works:
> D:\New Git>svn info "C:/Program Files/FlightGear/terrasync/Models"
> This does not work:
> D:\New Git>svn info "C:/Program Files/FlightGear/terrasync"
> Is this any help?
Unfortunately this differnece is unrelated. Terrasync creates separ
ThorstenB wrote
> On 23.06.2011 00:32, Vivian Meazza wrote:
> Looks like a white space issue to me.
> >
> > When svn.exe is in the path I get:
> >
> > Starting automatic scenery download/synchronization. Using external SVN
> > utility
> > 'svn'. Directory: 'D:/Git_New/terrasync'.
> > The filenam
On Thu, 23 Jun 2011, ThorstenB wrote:
> On 23.06.2011 00:32, Vivian Meazza wrote:
> Looks like a white space issue to me.
>>
>> When svn.exe is in the path I get:
>>
>> Starting automatic scenery download/synchronization. Using external SVN
>> utility
>> 'svn'. Directory: 'D:/Git_New/terrasync'.
On 23.06.2011 00:32, Vivian Meazza wrote:
Looks like a white space issue to me.
>
> When svn.exe is in the path I get:
>
> Starting automatic scenery download/synchronization. Using external SVN
> utility
> 'svn'. Directory: 'D:/Git_New/terrasync'.
> The filename, directory name, or volume label
Hello all,
Which part of the property tree holds the value(node) if i enabled the
following in the FGRUN
Advanced->Network->proxy
and
is there a tree diagram image file of the property tree floating some
where in the internet domain?
Thank you all
> The way I understand this, the issues are to some degree separate (?).
>
> I believe (correct me if I'm wrong) that what Jon is largely talking about
> is the altitude extrapolation of atmosphere conditions, i.e. given that I
> specify pressure, temperature and dew point at sea level, how will t
Arghh, yes, I am talking about issue #295 and not #294, sorry for that.
-Yves
Am 23.06.11 14:17, schrieb HB-GRAL:
> Hi all
>
> For upcoming debugging weeks: Please note that issue #294 and #335 are
> still valid here with OSX 10.6, ATI 5750, OSG2.9.7. I still get
>
> Warning: detected OpenGL error
Hi all
For upcoming debugging weeks: Please note that issue #294 and #335 are
still valid here with OSX 10.6, ATI 5750, OSG2.9.7. I still get
Warning: detected OpenGL error 'invalid operation' at after
RenderBin::draw(..)
with every plane (i.e. 737-100) where reflect shaders are active.
I don
--
From: "Vivian Meazza"
Sent: Thursday, June 23, 2011 8:44 AM
To: "'FlightGear developers discussions'"
Subject: Re: [Flightgear-devel] Heads up: scenery download
/built-interrasync
> Alan wrote
>
>>
Alan wrote
> --
> From: "Vivian Meazza"
> Sent: Wednesday, June 22, 2011 11:32 PM
> To: "'FlightGear developers discussions'"
>
> Subject: Re: [Flightgear-devel] Heads up: scenery download
> /built-interrasync
>
> > ThorstenB wrote:
> >
> >>
> >>
--
From: "Vivian Meazza"
Sent: Wednesday, June 22, 2011 11:32 PM
To: "'FlightGear developers discussions'"
Subject: Re: [Flightgear-devel] Heads up: scenery download
/built-interrasync
> ThorstenB wrote:
>
>>
>> You need to provide a target dire
> Well, FlighGear has its own atmosphere model that is also used by the
> other subsystems (e.g. instruments, weather reports, visual system, AI
> traffic and whatnot). So far there has been few reasons not use that
> model also for the FDM.
>
> I think the FDM only needs to know the atmospheric pr
13 matches
Mail list logo
