check whether state can change before evaluating conditions

this is a regression from the new implementation to use triggers per state machine layer. Since canChangeState was being called after evaluating the conditions, the trigger would be marked as used but the state wouldn't change. This makes sure canChangeState is called before. Diffs= 7f3314f4f9 check whether state can change before evaluating conditions (#8917)
rive-app · Jan 24, 2025 · 085a75d · 085a75d
1 parent e0ba592
commit 085a75d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.rive_head b/.rive_head
@@ -1 +1 @@
-d8d42c0f130ec1f7d70a9e4ca3cffb1f6e3b9860
+7f3314f4f98b54580758aa48a435a8a202ed9fcd
diff --git a/wasm/submodules/rive-runtime b/wasm/submodules/rive-runtime
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		d8d42c0f130ec1f7d70a9e4ca3cffb1f6e3b9860
		7f3314f4f98b54580758aa48a435a8a202ed9fcd
+1 −1		.rive_head
+10 −3		include/rive/animation/state_machine_input_instance.hpp
+2 −0		include/rive/animation/transition_trigger_condition.hpp
+34 −26		src/animation/state_machine_instance.cpp
+9 −0		src/animation/state_transition.cpp
+2 −2		src/animation/transition_property_viewmodel_comparator.cpp
+15 −1		src/animation/transition_trigger_condition.cpp
+ −		tests/unit_tests/assets/state_machine_triggers.riv
+79 −0		tests/unit_tests/runtime/state_machine_test.cpp