On Saturday 28 December 2002 2:13 pm, David Megginson wrote: > Curtis L. Olson writes: > > What would be really useful when you get into modeling push buttons is > > to be able to model a switch where it is "true" while the mouse is > > depressed and then immediately returns to false when the mouse button > > is released. Currently you need to click a second time to return the > > button to false. > > Done, finally (this has been in my queue since 25 October). I've just > checked in changes that allow mod-up support for panel mouse bindings, > add a 'repeatable' flag, and ensure that other bindings are tried if > one fails a conditional test. > > To demonstrate the new support, I've changed the bindings for the 2D > single magneto switch so that the switch engages the starter when you > click past 'both', then snaps back as soon as you let go of the > mouse. You'll need to update the base package to see this. >
ROCK! > > We have both types of buttons on the KR-87 ADF, those that you depress > > and they click in and stay depressed, and then you push them again and > > they come back out (ADF, BFO). And also the kind of buttons (FRQ, > > Flt/Et, Set/Rst) where they immediately return to not-depressed when > > you remove your finger. > > I've noticed that the property radios/ subtree has separate branches > for KR-87, etc., when it really should have only adf[0], adf[1], > etc. -- otherwise, we have to know exactly what radio type to bind > for. Let's try to keep the bindings generic. > I think that was just an interim thing until we could make the KR-87 the default, but Curt would know. I think I have some other bendix thingy in the pipeline that needed that too. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
