Changelog 2.12: Difference between revisions

Jump to navigation Jump to search
Line 41: Line 41:
A tooltip is specified via a set-tooltip command in a pick (or slider or knob) animation's <hovered> bindings group. The tooltip is configured at this time, especially content and an ID. The mouse-handling system then displays the tooltip at the correct time. This design allows us to show tooltips at configurable points, either the standard method - after the mouse is stationary for a period of time - or in response to other actions, such as mouse clicks/drags.
A tooltip is specified via a set-tooltip command in a pick (or slider or knob) animation's <hovered> bindings group. The tooltip is configured at this time, especially content and an ID. The mouse-handling system then displays the tooltip at the correct time. This design allows us to show tooltips at configurable points, either the standard method - after the mouse is stationary for a period of time - or in response to other actions, such as mouse clicks/drags.
Continue reading at [[Tooltips]]...
Continue reading at [[Tooltips]]...
Stuart has pushed a further enhancement to the checklist feature. Aircraft authors may now add one or more <binding> elements to a checklist <item>. Conceptually, these are the actions that the user should execute to complete the item. The checklist GUI displays items with such <binding> elements with an additional [>] button. Clicking on the button executes the bindings, allowing the user to watch as the computer/co-pilot/instructor executes the checklist item.
The <binding> element is exactly as you would expect - so property-assign, nasal etc. works.
Due to the power of Nasal and properties, this feature only required 13 lines of code to write, most of which is displaying the button!
Stuart is planning to extend this function so that checklists with one or more items containing a <binding> element can have an (optional) button to execute the entire checklist. I'm still thinking of how best to implement this, as I think one would want a gap between each item.
Stuart highlights the property-interpolate command which provides a very convenient way to interpolate a property to a new value. See Docs/README.commands if you were unaware of this.
Stuart has updated the c172p checklists to use this feature, including some rather cute interpolations of the throttle, mixture and trim controls.
Continue reading at [[Aircraft Checklists]]...


''' Internationalization '''
''' Internationalization '''

Navigation menu