v1.8

Bugfix for SimHub 9.2.0

v1.7

Added property value locking

• Added property value locking via NCalc/Javascript expression. Enables properties' values to be changed only when the expression result is true.

This is especially useful for creating menu systems that can be navigated using a single input source. For instance, if you want to navigate multiple menus using a rotary encoder, you will bind the same controls to multiple properties (using cycler binds). However, when you change the selected option on one submenu, it will alter the property values of other menus.

With this new feature, the properties can be "locked" so that the value can only be changed when a given NCalc/Javascript expression returns true. This allows you to only affect the property of the menu that is currently open.

v1.6.1

V1.0 settings files are no longer supported, please make sure you export your settings now as a backup. V1.1+ files are compatible.

• Removed V1.0 import support.
• Fixed importing settings not working when property list is empty.
• Invalid imported settings no longer causes a crash.

Full Changelog: v1.6...v1.6.1

v1.6

What's Changed

Apply Changes without Reloading (and other fixes) by @LukasLichten in #1

• Automatically applies changes
• Fixed being able to name two Properties (and the Binds within) the same (and cause them not to work correctly)
  • Highlighting for when names collide
• Renaming Properties and Binds no longer unbinds InputMaps
• Deleting Properties and Binds removes InputMaps
• When adding a Cycler or Toggle to a Property without any maps will generate a template
  • Cycler spawns with two normal binds and a Cycler in Forward mode
  • Toggle spawns with a normal bind named Default and a Toggle named Toggle
  • If binds already exist it just adds a Cycler/Toggle
  • Binds will also generate with a default name (PropertyName_"number")
• Added Tooltips
• Export now exports a Indented Json for better readability
• Added Warning to Import that it deletes existing Properties

New Contributors

• @LukasLichten made their first contribution in #1

Full Changelog: v1.5.1...v1.6

v0.5.1

Fixed cycler bind bug where looping would not occur when value binds were at the top of the list of binds for a property.

Full Changelog: v1.5...v1.5.1

v1.5

Added feature - Bind Name property

A new property has been added to provide the name of the currently active bind of the respective property. This could be used as the title label for the currently active page, or in NCalc formulas if you prefer.

Full Changelog: v1.4.1...v1.5

v1.4.1_hotfix

Hotfix - Fixed ability to delete ToggleBind and CyclerBind

Full Changelog: v1.4...v1.4_hotfix

v1.4

Added feature - Property toggle binds

Toggle binds can be used to display a specific page/display when a button is pressed but returns to the previous page.

A use case for this could be the "Brake Magic" feature on Mercedes F1 cars, where a screen displaying brake temperatures is displayed temporarily until it is de-activated.

Full Changelog: v1.3...v1.4

v1.3

Added feature - Property cycling binds

Cycler binds can now be created (forward or reverse) that can be used to increment/decrement a property's value. This can be used to allow a + & - style binding to the property, instead of setting the value with specific binds. This could be used for a DASH + and DASH - button to perform the same function as a multi-position rotary encoder for example.

Exported settings files using the old JSON format are still compatible, using an automated conversion.

Full Changelog: v1.2...v1.3

v1.2

• Removed "MultiPositionWidget" references from the events and properties. This was an older name for the plugin that has been changed.

You will have to alter your property bindings to fix the references, but the binds will be unaltered

Full Changelog: v1.1...v1.2