Vivian Meazza wrote:
Harald JOHNSEN wrote:
I have another probleme with wincvs.
In the list of files in the explorer nearly all files have an 'unknown'
state. So i don't have the diff choice when I right click on them.
I've tried an update with the command line but that does not chance
Drew wrote
I'm trying this now with wincvs. I click Admin-Command Line, and
then enter the following string:
cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login
CVS passwd: guest
When I hit 'ok', it comes back with Unable to initialize the CVS
process. The system cannot
Thanks for the reply.
To login use Admin Login then ... at the bottom right of the login screen
to access the editing facility. Select:
Protocol - pserver
Repository Path - cvs.flightgear.org:/var/cvs/FlightGear-0.9
Keywords - Username - use 'Edit' to enter cvsguest
- Password -
Drew wrote
To login use Admin Login then ... at the bottom right of the login
screen
to access the editing facility. Select:
Protocol - pserver
Repository Path - cvs.flightgear.org:/var/cvs/FlightGear-0.9
Keywords - Username - use 'Edit' to enter cvsguest
- Password -
It prompted me to install python when I first ran it, so I did install
python. Not Pearl, though. Yes, I have version 2.0.0.2 build 2.
On 4/25/05, Vivian Meazza [EMAIL PROTECTED] wrote:
Drew wrote
To login use Admin Login then ... at the bottom right of the login
screen
to access
Drew wrote
-Original Message-
From: [EMAIL PROTECTED] [mailto:flightgear-devel-
[EMAIL PROTECTED] On Behalf Of
Sent: 25 April 2005 09:20
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Re: Blank screen implementation
It prompted me to install python when I
Have you set the home directory in Admin preferences?
I hadn't, but I just did...I assume this is the directory in which the
source trees get saved? It says to read the documentation, but I
can't find the documentation.
Anyway, adding a home directory didn't change anything. I still get
the
-Original Message-
From: [EMAIL PROTECTED] [mailto:flightgear-devel-
[EMAIL PROTECTED] On Behalf Of Drew
Sent: 25 April 2005 16:57
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Re: Blank screen implementation
Have you set the home directory in Admin
Ah...that's alright, I'll just stick with what I have. I was told it
was a few mouse clicks, and it's already taken more of my time that
it's worth. All I'm really trying to do is draw a black rectangle.
Thanks for your help.
Drew
___
Vivian Meazza wrote:
Drew wrote
Ah...that's alright, I'll just stick with what I have. I was told it
was a few mouse clicks, and it's already taken more of my time that
it's worth. All I'm really trying to do is draw a black rectangle.
Thanks for your help.
No problem, pity you can't
Harald JOHNSEN wrote:
I have another probleme with wincvs.
In the list of files in the explorer nearly all files have an 'unknown'
state. So i don't have the diff choice when I right click on them.
I've tried an update with the command line but that does not chance
anything. Its a fresh
I'm trying this now with wincvs. I click Admin-Command Line, and
then enter the following string:
cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login
CVS passwd: guest
When I hit 'ok', it comes back with Unable to initialize the CVS
process. The system cannot find the file
Drew wrote
And a red one for -ve G. With a bit of texture.
I never liked the 'red-out' in simulators...do pilot's really see red?
I thought it was just called red-out because of excess blood to the
brain.
In any case, I thought of the same thing, myself (using this for GLOC).
I don't buy that argument. It's easier to grow with fgfs in small
steps than to adapt everything after major releases. Following the
cvslogs mailing list is usually enough, and there isn't such a fast
progress anyway.
Ok, I'm trying to take your advice, and get a later version of the source.
Drew a écrit :
I don't buy that argument. It's easier to grow with fgfs in small
steps than to adapt everything after major releases. Following the
cvslogs mailing list is usually enough, and there isn't such a fast
progress anyway.
Ok, I'm trying to take your advice, and get a later version
Drew wrote:
I tried downloading the tar archive of the latest CVS flightear, but
it doesn't compile with the latest release of SimGear. Is there an
archive somewhere of a development SimGear version, or will I have
to install a CVS client to get this code? I'm using Windows, and
have never
This isn't wasted time. Learning to use CVS to synch to open source
projects will be a skill you use for the rest of your life (or at
least until everyone moves onto subversion or darcs or arch or
whatever). Like it or not, limiting yourself to released versions of
software kinda makes you
It is very easy with this tool : http://www.wincvs.org/download.html
When using CVS, you have to keep SimGear, FlightGear and the data in
sync, but it is just a few click with Wincvs.
-Fred
Thanks for the help. I think I'll put this on hold right now, and try
it during the weekend when I
Frederic Bouvier wrote
Drew a écrit :
I don't buy that argument. It's easier to grow with fgfs in small
steps than to adapt everything after major releases. Following the
cvslogs mailing list is usually enough, and there isn't such a fast
progress anyway.
Ok, I'm trying to take
* Drew -- Wednesday 20 April 2005 21:56:
I'm trying to find an easy way to make the screen go black in the
FlightGear window...sort of like a camera failure for a UAV.
You can show a black and opaque dialog. Save the attached file to
$FG_ROOT/Nasal/ and call it from any Nasal context, for
* Drew -- Wednesday 20 April 2005 22:32:
I'm not very familiar with this code, though, so I don't know what a Nazel
context is, yet.
You can add this to the black.nas file, after which you can switch the blackout
state via property /sim/rendering/blackout. No need to dive into Nasal then.
Improved dialog nasal file attached. Just drop it into $FG_ROOT/Nasal/ again.
It does monitor the property /sim/rendering/blackout and turns the screen
black accordingly. And it offers three commands for Nasal context:
black.open();
black.close();
black.toggle();
m.
dialog = nil;
state =
Thank you very much for your help...I'll try it out and let you know
how it goes.
Drew
On 4/20/05, Melchior FRANZ [EMAIL PROTECTED] wrote:
Improved dialog nasal file attached. Just drop it into $FG_ROOT/Nasal/ again.
It does monitor the property /sim/rendering/blackout and turns the screen
Melchior FRANZ wrote:
Improved dialog nasal file attached. Just drop it into
$FG_ROOT/Nasal/ again. It does monitor the property
/sim/rendering/blackout and turns the screen black accordingly. And
it offers three commands for Nasal context:
Cool, now animate the alpha value and tie it to the
Andy Ross wrote
Melchior FRANZ wrote:
Improved dialog nasal file attached. Just drop it into
$FG_ROOT/Nasal/ again. It does monitor the property
/sim/rendering/blackout and turns the screen black accordingly. And
it offers three commands for Nasal context:
Cool, now animate the
* Drew -- Wednesday 20 April 2005 23:26:
Thank you very much for your help...I'll try it out and let you know
how it goes.
Whoops. There was an embarrassing bug in it. Better take this here:
http://members.aon.at/mfranz/black.nas
m.
___
And a red one for -ve G. With a bit of texture.
I never liked the 'red-out' in simulators...do pilot's really see red?
I thought it was just called red-out because of excess blood to the
brain.
In any case, I thought of the same thing, myself (using this for GLOC).
Drew
Whoops. There was an embarrassing bug in it. Better take this here:
I still get that same error on this line:
switch = props.globals.getNode(/sim/rendering/blackout, 1);
Does this property need to be declared somewhere?
___
Flightgear-devel mailing
* Drew -- Wednesday 20 April 2005 23:42:
Nasal runtime error: no such member at ./data/Nasal/black.nas, line 4
In which version? The last one, for which I sent the URL?
http://members.aon.at/mfranz/black.nas
m.
___
Flightgear-devel mailing list
Both. That line is identical in both versions, so I wouldn't expect
any differences.
BTW, I know I don't have the latest and greatest Nasal, as Andy's been
discussing. For instance, it didn't recognize the if ? then : else
syntax, but I knew how to fix that.
Drew
On 4/20/05, Melchior FRANZ
* Drew -- Thursday 21 April 2005 00:12:
I still get that same error on this line:
switch = props.globals.getNode(/sim/rendering/blackout, 1);
Does this property need to be declared somewhere?
No. The line is OK. But maybe your version of fgfs isn't? The Nasal code
is for fgfs CVS/HEAD. It
(Not that it had to. But it was fun. :-)
Not so fun for me, though. I suppose I need to get the new Nasal
code, now, or is there a way to do this with the old version? I'm
running the 0.9.8 release. I'm making too many custom mods to be
chasing a moving target.
Drew
* Drew -- Thursday 21 April 2005 00:24:
BTW, I know I don't have the latest and greatest Nasal, as Andy's been
discussing. For instance, it didn't recognize the if ? then : else
syntax, but I knew how to fix that.
The possibility to set the dialog color is also very new, only a few
days old.
Melchior FRANZ wrote:
Drew wrote:
switch = props.globals.getNode(/sim/rendering/blackout, 1);
Does this property need to be declared somewhere?
No. The line is OK. But maybe your version of fgfs isn't? The Nasal code
is for fgfs CVS/HEAD. It uses Nasal syntax that was added to CVS
* Drew -- Thursday 21 April 2005 00:29:
Not so fun for me, though. I suppose I need to get the new Nasal
code, now,
No. The ternary operation was the only thing that I was using and
that was added after 0.9.8. I've removed it now. Same URL.
I'm running the 0.9.8 release.
That won't work
35 matches
Mail list logo
