[Flightgear-devel] mice.xml bug
I have a custom mice.xml file that seems to have worked quite nicely up until a few days ago. That's when I first noticed that in my view mode I can set /control/flight/rudder by holding down LMB and moving the mouse right and left. Aileron and elevator are unaffected. I can't figure this out since nowhere in my mice.xml file does /control/flight/rudder appear. Anyone know where this behavior is coming from so I can kill it? Here's the mice.xml file: ?xml version=1.0? PropertyList mouse n=0 mode-count type=int2/mode-count mode archive=y type=int0/mode mode n=0 cursorinherit/cursor constrained type=boolfalse/constrained pass-through type=booltrue/pass-through button n=2 binding commandproperty-assign/command property/devices/status/mice/mouse[0]/mode/property value type=int1/value /binding /button /mode !-- Mode 1: view mode -- mode n=1 cursorleft-right/cursor constrained type=booltrue/constrained pass-through type=boolfalse/pass-through !-- left button centres the offsets -- button n=0 binding commandproperty-assign/command property/sim/current-view/heading-offset-deg/property value alias=/sim/view/config/front-direction-deg/ /binding binding commandproperty-assign/command property/sim/current-view/goal-pitch-offset-deg/property property/sim/current-view/config/pitch-offset-deg/property /binding /button button n=1 binding commandproperty-assign/command property/sim/current-view/field-of-view/property value alias=/sim/view/config/default-field-of-view-deg/ /binding /button !-- right button switches modes -- button n=2 binding commandproperty-assign/command property/devices/status/mice/mouse[0]/mode/property value type=int0/value /binding /button button n=3 binding commandproperty-multiply/command property/sim/current-view/field-of-view/property factor type=double0.952380952380/factor min type=double5.0/min /binding /button button n=4 binding commandproperty-multiply/command property/sim/current-view/field-of-view/property factor type=double1.05/factor max type=double120.0/max /binding /button !-- Mouse left/right motion -- x-axis !-- No buttons pressed: move the view position left or right -- binding condition and not property/devices/status/mice/mouse[0]/button[0]/property /not not property/devices/status/mice/mouse[0]/button[1]/property /not /and /condition commandproperty-adjust/command property/sim/current-view/heading-offset-deg/property factor type=double-380/factor min type=double0/min max type=double360/max wrap type=booltrue/wrap /binding /x-axis !-- Mouse up/down motion -- y-axis !-- No buttons pressed: tilt the view up and down -- binding condition and not property/devices/status/mice/mouse[0]/button[0]/property /not not property/devices/status/mice/mouse[0]/button[1]/property /not /and /condition commandproperty-adjust/command property/sim/current-view/pitch-offset-deg/property factor type=double-180/factor min type=double-90/min max type=double90/max wrap type=boolfalse/wrap /binding /y-axis /mode /mouse /PropertyList ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] mice.xml bug
Josh Babcock wrote: I have a custom mice.xml file that seems to have worked quite nicely up until a few days ago. That's when I first noticed that in my view mode I can set /control/flight/rudder by holding down LMB and moving the mouse right and left. Aileron and elevator are unaffected. I can't figure this out since nowhere in my mice.xml file does /control/flight/rudder appear. Anyone know where this behavior is coming from so I can kill it? It's probably being picked up from the default $FG_ROOT/mice.xml file. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] mice.xml bug
David Megginson wrote: Josh Babcock wrote: I have a custom mice.xml file that seems to have worked quite nicely up until a few days ago. That's when I first noticed that in my view mode I can set /control/flight/rudder by holding down LMB and moving the mouse right and left. Aileron and elevator are unaffected. I can't figure this out since nowhere in my mice.xml file does /control/flight/rudder appear. Anyone know where this behavior is coming from so I can kill it? It's probably being picked up from the default $FG_ROOT/mice.xml file. All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel Yeah, that's the problem. Looks like the nasal script for the throttle is also sneaking in. Can I define a null binding? Is there a way to override the whole base package mice.xml? Josh ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] mice.xml bug
Josh Babcock wrote: Yeah, that's the problem. Looks like the nasal script for the throttle is also sneaking in. Can I define a null binding? Is there a way to override the whole base package mice.xml? Yes and no. You can define a null binding using the command null, but there is no way to skip reading mice.xml (at least not yet). All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] mice.xml bug
David Megginson wrote: Josh Babcock wrote: Yeah, that's the problem. Looks like the nasal script for the throttle is also sneaking in. Can I define a null binding? Is there a way to override the whole base package mice.xml? Yes and no. You can define a null binding using the command null, but there is no way to skip reading mice.xml (at least not yet). All the best, David ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel The null commands worked just fine, I don't think it's too much trouble to update my file to reflect any additions to the base file. Josh ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
