Re: [Flightgear-devel] Improved usability
If this is any help , it appears that one of the objects disappears if there are multiple objects in the pick animation. Will continue testing . Syd On Fri, Apr 12, 2013 at 3:17 PM, James Turner wrote: > > > On 12 Apr 2013, at 20:11, Stuart Buchanan wrote: > > > On Fri, Apr 12, 2013 at 6:01 PM, James Turner wrote: > >> On 12 Apr 2013, at 16:56, James Turner wrote: > >>> No, handling should be the same as before, but I didn't test > the b1900d - will take a look and ensure I haven't done anything silly. > >>> > >>> The change I have made (which did need some re-work, and may have > caused the bug you're seeing) is *visible* pick animations can have > invisible 'pick-proxy' elements, specified by 'proxy-name' in the XML. The > C172P uses these so tiny switches (on the KMA-20 audio-panel) are easier to > hit. (The C172p 3D model already had such polygons, the actual switches > were not pickable - this didn't work so well in my new scheme, hence the > support for pick-proxies to make things as usable as possible). > >>> > >>> Again, this is likely 'just a bug', I'll test / fix over the weekend. > >> > >> Based on a *very* quick look, the B1900d seems fine here - can you send > me a screenshot of what is 'missing'? I also don't see any errors about bad > object names either. > > > > I'm seeing a number of missing controls on the a4f as well with > > current git binaries. They are present with a binary from about a > > month ago, so I'm fairly sure it's related to the recent changes. > > > > I get a bunch of console errors matching the missing instruments: > > > > Could not find at least one of the following objects for animation: > > 'UHFFreqSelectManual' > > Could not find at least one of the following objects for animation: > > 'UHFFreqSelectGoXMIT' > > Could not find at least one of the following objects for animation: > 'UHFOff' > > Could not find at least one of the following objects for animation: > 'UHFTR' > > Could not find at least one of the following objects for animation: > 'UHFADF' > > Could not find at least one of the following objects for animation: > > 'TACANModeOFF' > > Could not find at least one of the following objects for animation: > > 'TACANModeREC' > > Could not find at least one of the following objects for animation: > > 'TACANModeAA' > > Could not find at least one of the following objects for animation: > > 'RadarModeOFF' > > Could not find at least one of the following objects for animation: > > 'RadarModeSTBY' > > Could not find at least one of the following objects for animation: > > 'RadarModeSRCH' > > Could not find at least one of the following objects for animation: > > 'RadarModeAG' > > Could not find at least one of the following objects for animation: > 'GunSwitch' > > Could not find at least one of the following objects for animation: > > 'RadarRangeSwitchLong' > > Could not find at least one of the following objects for animation: > > 'BHDIModeSwitchNAVCMPTR' > > Could not find at least one of the following objects for animation: > > 'BHDIModeSwitchNAVPAC' > > Could not find at least one of the following objects for animation: > > 'SpoilerSwitchArm' > > Could not find at least one of the following objects for animation: > > 'SteeringSwitchOff' > > Could not find at least one of the following objects for animation: > > 'APCSwitchOff' > > > > Most of these objects are animated in > > AIrcraft/a4/Models/Instruments/a4f-panel-xh.xml > > > > Screenshot highlighting the missing knobs: > > http://www.nanjika.co.uk/flightgear/missing.jpg > > Yep, I'm sure this is my flat, thanks for providing the info. Will take a > look over the weekend. > > Regards, > James > > > > > -Stuart > > > > > -- > > 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 > > > -- > 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 > -
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 20:11, Stuart Buchanan wrote: > On Fri, Apr 12, 2013 at 6:01 PM, James Turner wrote: >> On 12 Apr 2013, at 16:56, James Turner wrote: >>> No, handling should be the same as before, but I didn't test the >>> b1900d - will take a look and ensure I haven't done anything silly. >>> >>> The change I have made (which did need some re-work, and may have caused >>> the bug you're seeing) is *visible* pick animations can have invisible >>> 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses >>> these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The >>> C172p 3D model already had such polygons, the actual switches were not >>> pickable - this didn't work so well in my new scheme, hence the support for >>> pick-proxies to make things as usable as possible). >>> >>> Again, this is likely 'just a bug', I'll test / fix over the weekend. >> >> Based on a *very* quick look, the B1900d seems fine here - can you send me a >> screenshot of what is 'missing'? I also don't see any errors about bad >> object names either. > > I'm seeing a number of missing controls on the a4f as well with > current git binaries. They are present with a binary from about a > month ago, so I'm fairly sure it's related to the recent changes. > > I get a bunch of console errors matching the missing instruments: > > Could not find at least one of the following objects for animation: > 'UHFFreqSelectManual' > Could not find at least one of the following objects for animation: > 'UHFFreqSelectGoXMIT' > Could not find at least one of the following objects for animation: 'UHFOff' > Could not find at least one of the following objects for animation: 'UHFTR' > Could not find at least one of the following objects for animation: 'UHFADF' > Could not find at least one of the following objects for animation: > 'TACANModeOFF' > Could not find at least one of the following objects for animation: > 'TACANModeREC' > Could not find at least one of the following objects for animation: > 'TACANModeAA' > Could not find at least one of the following objects for animation: > 'RadarModeOFF' > Could not find at least one of the following objects for animation: > 'RadarModeSTBY' > Could not find at least one of the following objects for animation: > 'RadarModeSRCH' > Could not find at least one of the following objects for animation: > 'RadarModeAG' > Could not find at least one of the following objects for animation: > 'GunSwitch' > Could not find at least one of the following objects for animation: > 'RadarRangeSwitchLong' > Could not find at least one of the following objects for animation: > 'BHDIModeSwitchNAVCMPTR' > Could not find at least one of the following objects for animation: > 'BHDIModeSwitchNAVPAC' > Could not find at least one of the following objects for animation: > 'SpoilerSwitchArm' > Could not find at least one of the following objects for animation: > 'SteeringSwitchOff' > Could not find at least one of the following objects for animation: > 'APCSwitchOff' > > Most of these objects are animated in > AIrcraft/a4/Models/Instruments/a4f-panel-xh.xml > > Screenshot highlighting the missing knobs: > http://www.nanjika.co.uk/flightgear/missing.jpg Yep, I'm sure this is my flat, thanks for providing the info. Will take a look over the weekend. Regards, James > > -Stuart > > -- > 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 -- 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
Re: [Flightgear-devel] Air-to-air refuelling enhancement
On Wed, Apr 10, 2013 at 11:24 PM, jean wrote: > one more bug (was my mistake ): > > in tanker .nas, we need to normalise the degre in line 26O-261 to have: > > me.hOffsetN.setDoubleValue(view.normdeg(me.bearing - > ac_hdg)); > me.vOffsetN.setDoubleValue(view.normdeg(elev - ac_pitch)); > > this was done in the 2.10.1, but not in next ( i sent you a mail > probably lost in the numerical world). Yes - I lost that email. Now committed. Thanks, -Stuart -- 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
Re: [Flightgear-devel] Joystick dialog configuration fix
Hi Clément, On Thu, Apr 11, 2013 at 1:15 PM, Clement de l'Hamaide wrote: > I'm using a Thrustmaster Hotas-x and I noticed that section on top > of the original file ( > $FG_DATA/Input/Joysticks/Thrustmaster/T-Flight-Hotas-X.xml ) is not copied > to the custom file written in $FG_HOME after modification from the "Joystick > Configuration" dialog. > This missing section break the behaviour because 2 variables are not > declared (in my case, I don't know for other .xml files). > > Looking at joystick.nas this is expected since is not handled so > I've fixed it. > Here is the "git diff" who fix the issue : http://pastebin.com/XaanECUs This has now been committed. Thanks! -Stuart -- 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
Re: [Flightgear-devel] Improved usability
On Fri, Apr 12, 2013 at 6:01 PM, James Turner wrote: > On 12 Apr 2013, at 16:56, James Turner wrote: >> No, handling should be the same as before, but I didn't test the >> b1900d - will take a look and ensure I haven't done anything silly. >> >> The change I have made (which did need some re-work, and may have caused the >> bug you're seeing) is *visible* pick animations can have invisible >> 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses >> these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The >> C172p 3D model already had such polygons, the actual switches were not >> pickable - this didn't work so well in my new scheme, hence the support for >> pick-proxies to make things as usable as possible). >> >> Again, this is likely 'just a bug', I'll test / fix over the weekend. > > Based on a *very* quick look, the B1900d seems fine here - can you send me a > screenshot of what is 'missing'? I also don't see any errors about bad object > names either. I'm seeing a number of missing controls on the a4f as well with current git binaries. They are present with a binary from about a month ago, so I'm fairly sure it's related to the recent changes. I get a bunch of console errors matching the missing instruments: Could not find at least one of the following objects for animation: 'UHFFreqSelectManual' Could not find at least one of the following objects for animation: 'UHFFreqSelectGoXMIT' Could not find at least one of the following objects for animation: 'UHFOff' Could not find at least one of the following objects for animation: 'UHFTR' Could not find at least one of the following objects for animation: 'UHFADF' Could not find at least one of the following objects for animation: 'TACANModeOFF' Could not find at least one of the following objects for animation: 'TACANModeREC' Could not find at least one of the following objects for animation: 'TACANModeAA' Could not find at least one of the following objects for animation: 'RadarModeOFF' Could not find at least one of the following objects for animation: 'RadarModeSTBY' Could not find at least one of the following objects for animation: 'RadarModeSRCH' Could not find at least one of the following objects for animation: 'RadarModeAG' Could not find at least one of the following objects for animation: 'GunSwitch' Could not find at least one of the following objects for animation: 'RadarRangeSwitchLong' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVCMPTR' Could not find at least one of the following objects for animation: 'BHDIModeSwitchNAVPAC' Could not find at least one of the following objects for animation: 'SpoilerSwitchArm' Could not find at least one of the following objects for animation: 'SteeringSwitchOff' Could not find at least one of the following objects for animation: 'APCSwitchOff' Most of these objects are animated in AIrcraft/a4/Models/Instruments/a4f-panel-xh.xml Screenshot highlighting the missing knobs: http://www.nanjika.co.uk/flightgear/missing.jpg -Stuart -- 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
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 16:56, James Turner wrote: > No, handling should be the same as before, but I didn't test the > b1900d - will take a look and ensure I haven't done anything silly. > > The change I have made (which did need some re-work, and may have caused the > bug you're seeing) is *visible* pick animations can have invisible > 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses > these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The > C172p 3D model already had such polygons, the actual switches were not > pickable - this didn't work so well in my new scheme, hence the support for > pick-proxies to make things as usable as possible). > > Again, this is likely 'just a bug', I'll test / fix over the weekend. Based on a *very* quick look, the B1900d seems fine here - can you send me a screenshot of what is 'missing'? I also don't see any errors about bad object names either. I'm assuming you have latest git versions of everything. 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
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 16:18, syd adams wrote: > too tired to do proper testing right now but I'll try again later .Just > noticed that a lot of switches have vanished in the b1900d and the terminal > reports that the objects cant be found for animation , but that could be me > not doing this wrong.Do pick animations need true now ? > After a good sleep I'll probably discover what I'm doing wrong :) No, handling should be the same as before, but I didn't test the b1900d - will take a look and ensure I haven't done anything silly. The change I have made (which did need some re-work, and may have caused the bug you're seeing) is *visible* pick animations can have invisible 'pick-proxy' elements, specified by 'proxy-name' in the XML. The C172P uses these so tiny switches (on the KMA-20 audio-panel) are easier to hit. (The C172p 3D model already had such polygons, the actual switches were not pickable - this didn't work so well in my new scheme, hence the support for pick-proxies to make things as usable as possible). Again, this is likely 'just a bug', I'll test / fix over the weekend. 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
Re: [Flightgear-devel] Improved usability
too tired to do proper testing right now but I'll try again later .Just noticed that a lot of switches have vanished in the b1900d and the terminal reports that the objects cant be found for animation , but that could be me not doing this wrong.Do pick animations need true now ? After a good sleep I'll probably discover what I'm doing wrong :) Syd On Fri, Apr 12, 2013 at 8:47 AM, James Turner wrote: > > On 12 Apr 2013, at 15:33, syd adams wrote: > > > I've apparently missed something... I cant right-drag , how do i enable > that ? Knob actions work fine so I'm adding this feature > > to the b1900d since I'm overhauling it anyway.I also get the same nasal > error that Stuart mentioned. > > Oh , and tooltips don't appear for me .Ive got a few days off now , so > I'm looking forward to digging into this . > > > > Debug menu -> User Interface Options to enable tooltips and right-drag > mode. > > Under what situations do you get the Nasal error? I've seen it when > property values are nil / undefined until first initialised, but that's all. > > 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 > -- 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
Re: [Flightgear-devel] Improved usability
On 12 Apr 2013, at 15:33, syd adams wrote: > I've apparently missed something... I cant right-drag , how do i enable that > ? Knob actions work fine so I'm adding this feature > to the b1900d since I'm overhauling it anyway.I also get the same nasal error > that Stuart mentioned. > Oh , and tooltips don't appear for me .Ive got a few days off now , so I'm > looking forward to digging into this . > Debug menu -> User Interface Options to enable tooltips and right-drag mode. Under what situations do you get the Nasal error? I've seen it when property values are nil / undefined until first initialised, but that's all. 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
Re: [Flightgear-devel] Improved usability
I've apparently missed something... I cant right-drag , how do i enable that ? Knob actions work fine so I'm adding this feature to the b1900d since I'm overhauling it anyway.I also get the same nasal error that Stuart mentioned. Oh , and tooltips don't appear for me .Ive got a few days off now , so I'm looking forward to digging into this . Syd On Fri, Apr 12, 2013 at 2:12 AM, James Turner wrote: > > On 11 Apr 2013, at 23:57, Saikrishna Arcot wrote: > > > I haven't tried the latest Git, but just in my opinion, if using > > Flightgear on a laptop, holding-down right-click to pan around can be > > bit of a pain. I would personally rather have the click-move-click > > method. > > There's three answers to this: > > - the current method will stay as an option on right-click (but probably > off by default) > - the current method will stay available on Tab, especially for laptop > users / Mac users who haven't found (or don't want) the option in System > Preferences to enable right-clicking > > (best for last!) > > - at least on my MacBook Pro, with right-clicks enabled in System > Preferences, I *can* right-drag. This was a complete surprise to me when > testing the new code, but actually it works great; touches on the > right-click area which become drags are interpreted as right-dragging and > everything just works. Indeed, looking this way is almost /more/ natural > than with the mouse, although the sensitivity needs to be tweaked. > > Of course I have no idea which other laptop trackpads / OSs support this - > I assume all must support right clicking somehow since it's a bit more > likely to be needed on Linux/Windows :) > > > Then again, not that many people probably use Flightgear on a laptop, > > and I haven't tried the latest Git. > > I would urge you to when you have time, all feedback is good! > > 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 > -- 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
Re: [Flightgear-devel] Improved usability
On 11 Apr 2013, at 23:57, Saikrishna Arcot wrote: > I haven't tried the latest Git, but just in my opinion, if using > Flightgear on a laptop, holding-down right-click to pan around can be > bit of a pain. I would personally rather have the click-move-click > method. There's three answers to this: - the current method will stay as an option on right-click (but probably off by default) - the current method will stay available on Tab, especially for laptop users / Mac users who haven't found (or don't want) the option in System Preferences to enable right-clicking (best for last!) - at least on my MacBook Pro, with right-clicks enabled in System Preferences, I *can* right-drag. This was a complete surprise to me when testing the new code, but actually it works great; touches on the right-click area which become drags are interpreted as right-dragging and everything just works. Indeed, looking this way is almost /more/ natural than with the mouse, although the sensitivity needs to be tweaked. Of course I have no idea which other laptop trackpads / OSs support this - I assume all must support right clicking somehow since it's a bit more likely to be needed on Linux/Windows :) > Then again, not that many people probably use Flightgear on a laptop, > and I haven't tried the latest Git. I would urge you to when you have time, all feedback is good! 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
Re: [Flightgear-devel] Improved usability
On 11 Apr 2013, at 22:29, Stuart Buchanan 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
