On Saturday, June 18, 2011 01:17:10 AM Vivian Meazza wrote:
> Hal,
>
>
>
> Since the dialog seems to be fundamentally broken, and in view of the
> freeze that has been declared on fgdata, I won't be merging this
> immediately. I'll see if I can fix up the Nasal errors, and then review
> the situation.
>
>
>
> Vivian
Vivian,
Beyond commenting out the calls related to the menu I made some other changes
to the nasal code including adding a reimplementation of controls.ptt() and a
new listener for the tr-lock along with correcting other issues with the code
(references to systems/comm were changed to instruments/comm and some of the
code had logic errors). At this point with the menu related stuff commented
out it all works and no error or warning messages are produced.
Everything else that is new is in the xml file which is now approaching 680
lines. I still need to add illumination animations for the new components
(fittings/connectors) on the bottom if the control box so it may be over 700
lines when this is all in place. All of the items in the xml are animations
of some sort.
I am not even close to being proficient on the menu part of this since the only
FG related menu I have ever made was the P-51D specific menu. This is a very
simple menu that does mostly very simple things (IE. it is a list of things
that the user can choose to enable/disable like loading rockets or drop tanks)
and this is a standalone menu not something that is a replacement for a
standard menu item. So it is a very different beast from the radio menu.
The radio can be used as is and is fully functional. The only issue is that
it is limited to the VHF frequencies that were programmed into comm1 and comm2
at startup. Users could setup some property over rides for these in fgrun or
on the command line to setup the four VHF channels for their flight plan or
change these using the property browser. This would actually be more
realistic but less convenient than having a menu to change these since in the
real thing you can't change the installed frequencies other than having a
radio tech do this on the ground. That is the radio needs to have new
crystals installed and then be tuned up/adjusted for the changed frequencies.
So it is worth while getting the new version integrated into your Spit even if
it will not be part of GIT until after the freeze. In the mean time maybe we
can figure out the menu stuff. I will have this in my fgdata clone later today.
Hal
>
>
>
> -----Original Message-----
> From: V. Engel [mailto:hven...@gmail.com]
> Sent: 18 June 2011 05:50
> To: flightgear-devel@lists.sourceforge.net
> Subject: Re: [Flightgear-devel] SCR-522
>
> On Friday, June 17, 2011 11:33:29 AM Hal V. Engel wrote:
> > On Sunday, June 12, 2011 03:07:25 AM Vivian Meazza wrote:
> > > Hal,
>
> snip
>
> > I grabbed your code off of GIT and did some minor mods to it mostly to
> >
> > point things at the right locations. The menu XML is currently
> >
> > unmodified. I am trying to get it to work but I am getting loadxml errors
> >
> > from Nasal when I hit the
> >
> >
> >
> > var radio = gui.Dialog.new("dialog",
> >
> > "Aircraft/Instruments-3d/SCR-522C/Dialogs/radios.xml")
> >
> >
> >
> > line of code. The error message says:
> >
> >
> >
> > loadxml: reading '<full path to the above file>' denied (unauthorized
> >
> > access) Nasal runtime error: Dialog class: XML dialog mush have <name>
> >
> >From mfranz on the forums I learned that this should not be happening and
>
> that it could be an issue with the "loadxml" fgcommand when using
> --fg-aircraft. My fg-aircraft path is showing up in the log in the
> IORules/READ: line when I have --log-level=info set. I am running GIT from
> about 3 weeks ago.
>
> > > That's all looking good. Can we get it into Git soon?
>
> snip
>
>
>
> I now have everything except the menu working. The 3D model is complete
> although the texturing of the fittings on the bottom of the unit is crude
> (but these are not visible in most installations). All of the controls have
> hot spots and the radio control unit can be fully manipluated with a mouse.
> Everything appears to be working correctly including how the ptt works with
> a remote ptt switch. All of the lights are functional and so is the dimming
> mask.
>
>
>
> I will be pushing this to my gitorious fgdata copy tomorrow along with some
> other P-51D updates after I make sure that everything is tested again. WIth
> the freeze I don't know if I will be able to get this into GIT but the
> radio has been in GIT for some time so perhaps I can. Once it is in my
> gitoriious copy of fgdata you can grab it for your Spitfire work. In the
> mean time perhaps some one here might know how to get the radio menu
> working or perhaps have some ideas about things that can be tried.
>
>
>
> Hal
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
