* Melchior FRANZ -- Saturday 25 March 2006 18:01: > [...] the slider resolution is much too high for finding an entry [...]
Too low, of course. :-) > I've now hacked the airports widget to allow filtered lists: > > http://members.aon.at/mfranz/airports.jpg [30 kB] BTW: this is not in CVS because of the feature freeze *and* a necessary change in fg_command.cxx: @@ -1127,6 +1128,6 @@ do_dialog_apply (const SGPropertyNode * dialog->applyValue(name); - dialog->updateValue(name); + //dialog->updateValue(name); } else { dialog->applyValues(); - dialog->updateValues(); + //dialog->updateValues(); } These two lines break the whole concept of "dialog-apply" (copy data from widget to property) and "dialog-update" (copy data from property to widget). The log message for this paranoid addition was: | Do an update after apply to see what really got into FlightGear. But that's what update is for. In the case of the airport list we need two-way communication: getValue() returns the selected entry, but setValue() sets the filter rule. Copying the filter rule back as "selected entry" does no good. I'm still investigating if this change works with all our dialogs. Maybe one would have to add a "dialog-update" on some places. Should be trivial, though. If someone wants to test this, then I can post the patches. m. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
