>> LaTeX is not a word processor, it is a professional typesetting tool.
>
> I see all the reasons to keep the docs in LaTex (like keeping the
> process efficient at the moment), but this sentence here about
> "professional tools" is probably not that serious as I read it, right ?
I don't know how
Hi all,
It always used to be that if no runway or parking ID is specified, a
runway facing into the wind will be chosen for takeoff. This no longer
happening. Tonight, with
METAR KSFO 140056Z 29010KT 10SM FEW006 18/12 A2997 RMK AO2 SLP149
T01830122, I am always started on rwy 10L.
And yes, I have
On Sep 13, 2011, at 4:17 PM, Csaba Halász wrote:
> On Wed, Sep 14, 2011 at 12:37 AM, Adam Dershowitz, Ph.D., P.E.
> wrote:
>>
>> I have a script that is giving me permission errors when it runs. The scrip
>> is in data/Nasal. It contains this line:
>>var file=io.open("data/latlong.c
Am 12.09.11 00:39, schrieb Martin Spott:
> HB-GRAL wrote:
>
> Exactly, that's a default in Robin's collection.
>
Hi Martin
Yes, sorry, you answered me this one some months before and I just
forgot about. It is part of the collection and this probably makes sense.
Cheers, Yves
-
Am 11.09.11 03:20, schrieb Curtis Olson:
>
> Asking a cartographer "where is it?" is just about as difficult a question
> as asking an astronomer "what time is it?"
>
> Curt.
Hi Curt
These are very good questions. I will ask some cartographers and
astronomers.
Cheers, Yves
---
On Wed, Sep 14, 2011 at 12:37 AM, Adam Dershowitz, Ph.D., P.E.
wrote:
>
> I have a script that is giving me permission errors when it runs. The scrip
> is in data/Nasal. It contains this line:
> var file=io.open("data/latlong.csv",mode="r");
Try this:
var file=io.open(getprop("/sim/fg-r
I seem to have run into a problem with NASAL permissions.
I have a script that is giving me permission errors when it runs. The scrip is
in data/Nasal. It contains this line:
var file=io.open("data/latlong.csv",mode="r");
and gives this error:
Nasal runtime error: io.open(): op
No crash report. What shows in console is pretty minimal:
9/13/11 3:03:56 PM FlightGear[28537] *** __NSAutoreleaseNoPool():
Object 0x208a10 of class NSThread autoreleased with no pool in place - just
leaking
9/13/11 3:03:59 PM [0x0-0x532532].net.sourceforge.macflightgear[28537]
On 13 Sep 2011, at 19:53, Adam Dershowitz, Ph.D., P.E. wrote:
> I just downloaded the new 2.4 release for Mac. If I try to launch the app,
> it just immediately quits.
> I can successfully run this version of FlightGear from the command line, so
> the problem must be with the launcher. I am
I just downloaded the new 2.4 release for Mac. If I try to launch the app, it
just immediately quits.
I can successfully run this version of FlightGear from the command line, so the
problem must be with the launcher. I am not sure the best way to report this,
so I am starting here.
Running
I am trying to integrate a moving map display into my TSR2 project cockpit and
decided that a stripped down version of the ZKV1000 code would be a starting
point.
ZK1000 derives its maps from the Atlas maps using the above perl script.
After a fight I got it to run using the command line perl bui
Am 13.09.11 10:46, schrieb thorsten.i.r...@jyu.fi:
>
> LaTeX is not a word processor, it is a professional typesetting tool.
I see all the reasons to keep the docs in LaTex (like keeping the
process efficient at the moment), but this sentence here about
"professional tools" is probably not that
Hi Fred,
Thanks for the svn repo update of
...
G src/wizard_funcs.cxx
...
Updated to revision 629.
FGRUN now compiles fine...
However, on running it, using my ./run_fgrun.sh I
had to use [Prev] button to get back to the setting
of the exe and fg-root paths, since I had previously
run it usi
> Thanks for the info - that confirms what I noticed: After Installing and
> doing some tests with LaTex and LyX I did not find a feasible way to
> import the newly designed appearance - seems you really have to just
> extract everything except the plain text and and build it up new -
> without the
14 matches
Mail list logo