Re: [Flightgear-devel] Re: Blank screen implementation
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 anything. Its a fresh install of wincvs 2.x but I had the same with the 1.3. Harald. I'm absolutely not a WinCVS guru. What I know about it has been learned mostly by trial and error (some of the former and lots of the latter). The documentation, shall we say, leaves a lot to be desired. So here goes. What are the extensions of the unknown status files? Many files in the source code are generated by the compiler, and are therefore not in the repository (sorry, BGOTO) extensions .a, .o .exe fall into this category. Files which you have generated and are not in the repository also have the status unknown. Some editors spew these like crazy; they are hidden in windows explorer, but not in WinCVS. Try selecting a directory (make sure it's not one in which you have modified files - that's not fatal, but recovering your work is a darned nuisance -, then Modify Update. On the update screen select 'create missing directories' and 'get the clean copy'. See what happens. Next, open some directory in windows explorer and delete the files which have status unknown (but are not .a .o. or .exe) See what happens - they should get the status missing. (If they don't they are probably not in the repository in the first place.) Then try the above again to restore them. Finally, if none of this addresses the problem, you can always delete the directories and start over. I've had to do that several times when my copy and the cvs copy just got too far out of line. The good thing about the later versions of WinCVS is that it pretty much works, but it's not all that intuitive and takes some figuring out. Hope none of this is teaching grandmother to suck eggs. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d Thx for the help. Nothing worked so I did a checkout on an empty directory as you sugjested. If cvs creates the files all is ok. It does not work with files coming from a tarball or created by hand. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
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 find the file specified There are also some instructions I found on using CVS with Windows on the FlightGear site, but it refers to commands with umn.edu addresses, which does not correspond with the page it links to (flightgear.org). So now I'm confused by this as well. Someone please help me out. 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 - use 'Edit' to enter guest OK to enter all that, then OK to login on the login screen This will log you in - I've just done it Alternatively on Admin Command line enter: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login and only that then enter guest as the password when the splash screen is displayed HTH Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 - use 'Edit' to enter guest OK to enter all that, then OK to login on the login screen This will log you in - I've just done it When I go to Admin-Login, I just get a window that has a CVSROOT field at the bottom (empty). There's a button with an ellipsis on it, and when I select that, I can see the settings you mention, but they are greyed out...uneditable (and blank). Alternatively on Admin Command line enter: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login and only that then enter guest as the password when the splash screen is displayed I didn't get any splash screen or login prompt...only the same error message Unable to initialize the CVS process: The system cannot find the file specified. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
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 - use 'Edit' to enter guest OK to enter all that, then OK to login on the login screen This will log you in - I've just done it When I go to Admin-Login, I just get a window that has a CVSROOT field at the bottom (empty). There's a button with an ellipsis on it, and when I select that, I can see the settings you mention, but they are greyed out...uneditable (and blank). Alternatively on Admin Command line enter: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login and only that then enter guest as the password when the splash screen is displayed I didn't get any splash screen or login prompt...only the same error message Unable to initialize the CVS process: The system cannot find the file specified. I can't duplicate that which you describe. Perhaps a duff installation? Do you have Python or Perl installed? Are you using WinCvs 2.0.0.2 build 2? Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 the editing facility. Select: Protocol - pserver Repository Path - cvs.flightgear.org:/var/cvs/FlightGear-0.9 Keywords - Username - use 'Edit' to enter cvsguest - Password - use 'Edit' to enter guest OK to enter all that, then OK to login on the login screen This will log you in - I've just done it When I go to Admin-Login, I just get a window that has a CVSROOT field at the bottom (empty). There's a button with an ellipsis on it, and when I select that, I can see the settings you mention, but they are greyed out...uneditable (and blank). Alternatively on Admin Command line enter: cvs -d :pserver:[EMAIL PROTECTED]:/var/cvs/FlightGear-0.9 login and only that then enter guest as the password when the splash screen is displayed I didn't get any splash screen or login prompt...only the same error message Unable to initialize the CVS process: The system cannot find the file specified. I can't duplicate that which you describe. Perhaps a duff installation? Do you have Python or Perl installed? Are you using WinCvs 2.0.0.2 build 2? Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
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 first ran it, so I did install python. Not Pearl, though. Yes, I have version 2.0.0.2 build 2. Have you set the home directory in Admin preferences? V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 same error. Thanks, Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
-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 preferences? I hadn't, but I just did...I assume this is the directory in which the source trees get saved? Yes - removing it here produced the grey-out entries, but I can't reproduce the file error. It says to read the documentation, but I can't find the documentation. They are under Help CVS Documentation If they aren't do you have an incomplete installation? Do you have a (hidden) file cvspass somewhere on your system? This might be the missing file, but that's a WAG. Anyway, adding a home directory didn't change anything. I still get the same error. I think it might be uninstall and reinstall time. I have no other ideas. All I can say is that it's worked here for several years, and that I downloaded and installed the latest version a couple of days ago. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 make it work - it really is a boon during development. But you are right not to waste time on it. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d 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 install of wincvs 2.x but I had the same with the 1.3. Harald. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
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 install of wincvs 2.x but I had the same with the 1.3. Harald. I'm absolutely not a WinCVS guru. What I know about it has been learned mostly by trial and error (some of the former and lots of the latter). The documentation, shall we say, leaves a lot to be desired. So here goes. What are the extensions of the unknown status files? Many files in the source code are generated by the compiler, and are therefore not in the repository (sorry, BGOTO) extensions .a, .o .exe fall into this category. Files which you have generated and are not in the repository also have the status unknown. Some editors spew these like crazy; they are hidden in windows explorer, but not in WinCVS. Try selecting a directory (make sure it's not one in which you have modified files - that's not fatal, but recovering your work is a darned nuisance -, then Modify Update. On the update screen select 'create missing directories' and 'get the clean copy'. See what happens. Next, open some directory in windows explorer and delete the files which have status unknown (but are not .a .o. or .exe) See what happens - they should get the status missing. (If they don't they are probably not in the repository in the first place.) Then try the above again to restore them. Finally, if none of this addresses the problem, you can always delete the directories and start over. I've had to do that several times when my copy and the cvs copy just got too far out of line. The good thing about the later versions of WinCVS is that it pretty much works, but it's not all that intuitive and takes some figuring out. Hope none of this is teaching grandmother to suck eggs. V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 specified There are also some instructions I found on using CVS with Windows on the FlightGear site, but it refers to commands with umn.edu addresses, which does not correspond with the page it links to (flightgear.org). So now I'm confused by this as well. Someone please help me out. Thanks, Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
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). Apparently they do, although the effect is less well understood than blackout: http://www.faa.gov/avr/afs/ac91-61.txt Regards Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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. 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 used CVS before. I can't be wasting too much time on this...too many other things to do. Thanks, Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 of the source. 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 used CVS before. I can't be wasting too much time on this...too many other things to do. 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 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 used CVS before. I can't be wasting too much time on this...too many other things to do. 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 a second class citizen in this world. If you want to participate in development discussions and test the bleeding edge features, you need to speak the same language as the rest of the developers. :) I assume you are using cygwin? In which case you want you can run the setup.exe program you find at http://www.cygwin.com, check off the cvs box, and let the download/installation finish. Then just follow the instructions on the websites. SimGear and FlightGear are pretty much identical: http://flightgear.org/cvs/anoncvs.html http://simgear.org/cvs.html Basically, for each archive you do a cvs login, followed by a cvs co. Then you run an autogen.sh script in each to generate the configure script, then run them like you normally do. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 a second class citizen in this world. If you want to participate in development discussions and test the bleeding edge features, you need to speak the same language as the rest of the developers. :) I assume you are using cygwin? In which case you want you can run the setup.exe program you find at http://www.cygwin.com, check off the cvs box, and let the download/installation finish. I'm using Visual Studio. My current goal, though, is not to be testing bleeding edge features, to be perfectly honest. I've got a simulation that I'm developing, using FlightGear as an image generator, and I have a deadline to meet. Honestly, I'd love to get acquainted with CVS and familiarize myself with the process, but it's more important right now that I get this particular project finished. Also, I don't want to be introducing unknowns by working with a continually changing product. Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 have some free time. Drew ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
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 your advice, and get a later version of the source. 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 used CVS before. I can't be wasting too much time on this...too many other things to do. 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. I use Wincvs and Cygwin. I find that using Wincvs on the source code can muck things up for compiling on Cygwin, but it's just great for data, diffs individual source code files etc - just be careful when downloading the full source code. I haven't investigated it fully, but it seems to be a root issue. No worries, Cygwin comes with an easy to use command line version of cvs - just follow the instructions. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 black accordingly. And it offers three commands for Nasal context: black.open(); black.close(); black.toggle(); m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 pilot acceleration property to simulate GLOC. :) Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: Blank screen implementation
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 alpha value and tie it to the pilot acceleration property to simulate GLOC. :) And a red one for -ve G. With a bit of texture. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 [EMAIL PROTECTED] wrote: * 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 Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
(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 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Blank screen implementation
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 yesterday. (Not that it had to. But it was fun. :-) Actually, that would just cause a parser error. I suspect what's really happening is that on Drew's system the black.nas file is being loaded before props.nas (the order is arbitrary -- whatever the OS gives you). Nasal currently lacks an import feature that allows you to say please stop executing this file until this other file is loaded, then resume. Although with the new features, this would be easy to add. For right now, the safest thing is to put your initialization code (at least the parts that depend on other modules) into a function and set it to run after startup with settimer(). Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
