v1.5.0

1.5.0 (2019-10-28)

Features

• Tracking: clear stored SurfaceData when SurfaceLocator enabled (3b4b95c)

  The SurfaceData type now has a Clear method which clears down the saved data within the datatype, which is called from within the OnEnable method of the SurfaceLocator to ensure the SurfaceData is clean from any previous state if the component is disabled.

Bug Fixes

• Tracking: provide correct null check on TargetValidity Rule (c1ca943)

  The TargetValiduty null check within the SurfaceLocator would never have been null because the Rule always contains the RuleContainer.

  The fix is to ensure the null check is done against the Rule.Interface which can be null if no Rule is provided.

Miscellaneous Chores

• deps: bump io.extendreality.malimbe from 9.6.0 to 9.6.1 (ef66393)

  Bumps io.extendreality.malimbe from 9.6.0 to 9.6.1. - Release notes - Changelog - Commits

  Signed-off-by: dependabot-preview[bot] [email protected]

v1.4.1

1.4.1 (2019-10-28)

Bug Fixes

• README.md: provide more concise release data and update info (083c14c)

  The Releases section has been removed and is now just a simple badge at the top of the README. There has been an additional section in Getting Started on how to update the package via the Unity Package Manager.

  The links have also been ordered in the order of appearance in the document.

v1.4.0

1.4.0 (2019-10-27)

Features

• Process: a IProcessable that emits event when processed. (8c9985c)

  Allows to call any no argument methods for a given moment.

v1.3.1

1.3.1 (2019-10-26)

Miscellaneous Chores

• deps: bump io.extendreality.malimbe from 9.5.3 to 9.6.0 (126af58)

  Bumps io.extendreality.malimbe from 9.5.3 to 9.6.0. - Release notes - Changelog - Commits

  Signed-off-by: dependabot-preview[bot] [email protected]

v1.3.0

1.3.0 (2019-10-26)

Features

• .github: use organization .github repository (9921b22)

  GitHub provides a mechanism where a global organization .github repo can be used as a fallback to provide default community health files instead of repeating the same files across multiple repos.

  ExtendRealityLtd now has a .github repo which should be used as it provides the correct details for this repo.

  The README.md has been updated to provide definitive links to the relevant files.

v1.2.0

1.2.0 (2019-10-25)

Features

• Haptics: option to allow all haptic processes in list to process (779103b)

  The HapticProcessor now has a CeaseAfterFirstSourceProcessed option which is defaulted to true to ensure existing default behaviour does not change, which is when the first active Haptic Process is processed then the HapticProcessor would cease to process any further Haptic Processes.

  With this new option, this default behaviour can be turned off and all Haptic Processes listed in the HapticProcessor can be processed if they are active in the scene.

Bug Fixes

• Velocity: provide more appropriate tooltip documentation (c509ce6)

  The VelocityTrackerProcessor has had the tooltip documentation updated to make it more appropriate and the code has been tidied up a bit so it is more succinct.

v1.1.1

1.1.1 (2019-10-24)

Bug Fixes

• Data: stop Vector2ToFloatTest extending MonoBehaviour (0f0ed28)

  Tests should not need to extend MonoBehaviour and this was causing a warning to be displayed due to this test extending it. The fix is to simply prevent the test class from extending MonoBehaviour.

• Tracking: update exception message in ObscuranceQuery (fa000c5)

  The ObscuranceQuery logic was changed so the Target requires either a Collider or if it has a Rigidbody then there must be at least 1 child Collider.

  The Exception messages we never updated so it provided inaccurate information if the usage criteria was incorrect.

v1.1.0

1.1.0 (2019-10-22)

Features

• Collection: allow query operations on list to run when inactive (95950d7)

  The query operations on the ObservableList such as Contains and IsListEmpty were previously encapsulated by the [RequiresBehaviourState] tag meaning a list contents check could only be performed if the list component was active in the scene.

  This blanket denial of operation is too heavy handed as just because a list object is inactive it shouldn't mean a contains check returns false because the list, even though inactive, still can contain the object to check for.

  It is still correct that components shouldn't perform an action when they are disabled, so if a list is queried then it should return the correct result but shouldn't perform any action, such as emitting any appropriate events.

  This solution uses the new Behaviour extension IsValidState to replicate the [RequiresBehaviourState] functionality within the method body to allow the correct return value but to prevent the event actions from occurring.

• Extension: determine if Behaviour is in a valid active state (de34e2f)

  The IsValidState extension method can be used to determine if a Behaviour is in the appropriate valid active state depending on whether the component is enabled and/or whether the GameObject the component resides on is active within itself or within the scene hierarchy.

  This mechanism is a copy of the Malimbe [RequiresBehaviourState] tag but can be used inline in methods rather than just a blanket early return from the entire method.

• Rule: determine if the rule component state can auto reject (32238fd)

  A new base abstract Rule class has been added that all existing MonoBehaviour rules now extend from. And on this new base Rule is the concept of being able to set whether the rule can automatically reject any request based on the state of the Rule component.

  Previously, if a Rule component was disabled or on an inactive GameObject then it would always reject the Accepts request, but this isn't always the requirement when using a Rule. The new AutoRejectStates enum flag allows a Rule to specify what states the rule can be in to automatically reject any request.

  All of the tests have been updated to show this new state selection option in practice.

v1.0.6

1.0.6 (2019-10-20)

Build System

• deps: bump io.extendreality.malimbe from 9.5.2 to 9.5.3 (b5dfbb0)

  Bumps io.extendreality.malimbe from 9.5.2 to 9.5.3. - Release notes - Changelog - Commits

  Signed-off-by: dependabot-preview[bot] [email protected]

Miscellaneous Chores

• deps: add dependabot configuration (2611d88)

v1.0.5

1.0.5 (2019-10-20)

Bug Fixes

• Data: prevent collapsible event drawer from setting scene as dirty (dfabfb9)

  The CollapsibleUnityEvent drawer Editor drawer was setting the scene as dirty on first draw of the component which was then causing an error in Unity 2019.1 and above when a prefab utilizing the custom drawer was drawn in the inspector. This is because the prefab cannot be saved if it is coming from a 3rd party Unity package and attempting to set the scene as dirty was causing an attempt to save.

  There is no reason for this SetDirty to occur as it provides no required functionality so the line has been removed which should fix the error it was causing.