Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-12 Thread Csaba Halász
On Fri, Dec 12, 2008 at 1:19 PM, Melchior FRANZ wrote: > * Csaba Halász -- Tuesday 09 December 2008: > >> it creates the node and immediately removes it. So how does >> the code in fgValidatePath trigger the listener? > > The validation interface has one reference since long before the > Nasal cod

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-12 Thread Melchior FRANZ
* Csaba Halász -- Tuesday 09 December 2008: > var n = props.globals.getNode("/sim/paths/validate", 1).remove(); > Okay, that must be some magic from Melchior again :) :-P > it creates the node and immediately removes it. So how does > the code in fgValidatePath trigger the listener? remove()

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-10 Thread BARANGER Emmanuel
Hello all, For information, We tested (several people) the Jester patch : http://pastebin.ca/1281126 And after patch, registrations code running again in mp. We can see the registrations of other players. So thank you to Jester. Hoping that this be included in CVS ;) Best regards. Emmanuel

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread gerard robin
On mercredi 10 décembre 2008, Csaba Halász wrote: > On Tue, Dec 9, 2008 at 8:52 PM, Csaba Halász <[EMAIL PROTECTED]> wrote: > > The only suspicious thing so far is that the DataVariance is set to > > STATIC. > > Indeed, setting it to dynamic seems to fix this problem. Maybe other > animations are a

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread Csaba Halász
On Tue, Dec 9, 2008 at 8:52 PM, Csaba Halász <[EMAIL PROTECTED]> wrote: > > The only suspicious thing so far is that the DataVariance is set to STATIC. Indeed, setting it to dynamic seems to fix this problem. Maybe other animations are affected too. -- Csaba/Jester Index: simgear/scene/model/ani

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread Csaba Halász
On Tue, Dec 9, 2008 at 6:03 PM, Brisa Francesco <[EMAIL PROTECTED]> wrote: > Hi > > I am currently investigating why the change immatriculation script for > dr400 aircraft stop working. Anyway, the xml loading doesn't seem to have anything to do with the problem. All files load fine. The only prob

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread Csaba Halász
On Tue, Dec 9, 2008 at 6:25 PM, Csaba Halász <[EMAIL PROTECTED]> wrote: > > Those are supposed to be created in io.nas, line 303: > ># validation listeners for load[xml]/save[xml]/parsexml() (see > utils.cxx:fgValidatePath) >var n = props.globals.getNode("/sim/paths/validate", 1).remove();

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread Csaba Halász
On Tue, Dec 9, 2008 at 6:03 PM, Brisa Francesco <[EMAIL PROTECTED]> wrote: > > fgValidatePath is in util.cxx and it tries to set something in the > /sim/paths/validate/read > > when I am in fgfs and browse the property tree this "directory" does not > exists ! > > could this be the cause of it fail

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread Brisa Francesco
Martin Spott ha scritto: > Brisa Francesco wrote: >> am currently investigating why the change immatriculation script for >> dr400 aircraft stop working. >> > Would you please have a look at the updated 'Protocol/fgcom.xml' file, > remove the last-but-one section: > > > callsign >

Re: [Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread Martin Spott
Brisa Francesco wrote: > I am currently investigating why the change immatriculation script for > dr400 aircraft stop working. Would you please have a look at the updated 'Protocol/fgcom.xml' file, remove the last-but-one section: callsign string CALLSIGN=%s /sim/multiplay/

[Flightgear-devel] problem with dr400 and path validation

2008-12-09 Thread Brisa Francesco
Hi I am currently investigating why the change immatriculation script for dr400 aircraft stop working. looking from the nasal code I ended up that it calls: fgcommand("loadxml", args) ? ret : nil; that is inside io.nas. Now, loadxml is a built in function inside fg_commands which calls the do_