On 11 Apr 2013, at 22:29, Stuart Buchanan <stuar...@gmail.com> wrote:
> Hi James, > > This is superb work. I've just taken a flight in the c172p to try out > the new features, and I'm very impressed. Thank you! > > Though I'm a dyed-in-the-wool mouse-looker who continually switched > between cursor and mouse-look, I'm completely converted to this way of > looking - way more intuitive IMO and really easy for users to learn. > > One minor suggestion - I used the mouse wheel field-of-view control a > lot when in look mode. Having it change the field of view while the > right mouse button is pressed would be good. Right, I'm somewhat torn here. 'Normal users' for which I normally mentally imagine my parents (retired), find 'chord presses' on mice pretty tricky, is my impression. (Piano players and similar might be an exception) So I was trying to avoid any actions that require 'using another mouse button or the wheel while right dragging' - when I add head-movement modes (pan, zoom) to right-drag, it will be via modifier keys (alt/shift) which everyone can safely use while dragging (and consistent with most 3D editing tools). However, there's no problem with supporting the option for people such as you who *can* hold down a button and use the wheel. > I'm seeing some bugs in this, in particular after hovering over some > control in the c172p (possibly the alitmeter?) I got "Aircraft Help" > displayed as all tooltips, and the following errors in the console: > > Nasal runtime error: nil used in numeric context > at /home/stuart/FlightGear/data/Nasal/geo.nas, line 241 > called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 167 > called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 119 > called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 91 > called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 270 > called from: /home/stuart/FlightGear/data/Nasal/canvas/tooltip.nas, line 313 > > geo.normgeg should probably be more robust…. Yes, I should have mentioned the known issues list: (although the 'aircraft help:' one is new to me) - tooltips sometimes appear partially off screen (need to adjust position somehow when near the borders) - dragging knobs and sliders doesn't work outside the windows bounds; unfortunately this is an OSG issue, most OSs do send mouse move events once you're 'tracking' (buttons held down) but osgViewer seems not to receive them. Or maybe this is only on Mac? - after tooltip-on-click, the tooltip stays visible when you move over other tooltip-areas, when it should probably disappear until the next click. > As a "bonus" function, for multi-mode toggle switches, it would be > great to be able to define labels for different values (e.g. 0=OFF, > 1=ON) There's a mapping function which uses Nasal, that's how C172 magneto key and audio-panel tooltips work. But I realised all the present uses are simply for an integer -> string mapping table, so yes, I should add explicit support for that. Thanks for the feedback, and testing, it's much appreciated. Regards, James ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
