Comments (3)
aleneum
commented on June 9, 2024
1
If it is the auto transitions that you would not expect (which is the case according to your post), you can disable them by passing "auto_transitions=False" to the constructor:
from transitions import Machine
class Matter(object):
def say_hello(self): print("hello, new state!")
def say_goodbye(self): print("goodbye, old state!")
lump = Matter()
transitions = [
{ 'trigger': 'melt', 'source': 'solid', 'dest': 'liquid' },
{ 'trigger': 'evaporate', 'source': 'liquid', 'dest': 'gas' },
{ 'trigger': 'sublimate', 'source': 'solid', 'dest': 'gas' },
{ 'trigger': 'ionize', 'source': 'gas', 'dest': 'plasma' }
]
states = ['solid', 'liquid', 'gas', 'plasma']
m = Machine(lump, states, initial='liquid', transitions=transitions, auto_transitions=False)
print(m.get_triggers('plasma'))
# >>> []They are enabled by default and are valid triggers. That's why get_triggers will return them when they are enabled.
The relevant part from the documentation:
In addition to any transitions added explicitly, a to_«state»() method is created automatically whenever a state is added to a Machine instance. This method transitions to the target state no matter which state the machine is currently in:
lump.to_liquid()
lump.state
>>> 'liquid'
lump.to_solid()
lump.state
>>> 'solid'If you desire, you can disable this behavior by setting auto_transitions=False in the Machine initializer.
from transitions.
aleneum
commented on June 9, 2024
Hello @jonra1993,
triggers are only available on the source state. In your code example:
transitions = [
{ 'trigger': 'melt', 'source': 'solid', 'dest': 'liquid' },
{ 'trigger': 'evaporate', 'source': 'liquid', 'dest': 'gas' },
{ 'trigger': 'sublimate', 'source': 'solid', 'dest': 'gas' },
{ 'trigger': 'ionize', 'source': 'gas', 'dest': 'plasma' }
]
you can trigger "melt" from state "solid", "evaporate" from "liquid" and so on. Consequently, "melt" is not a trigger for "solid" since it cannot be triggered when in that state. As far as I can tell, "plasma" is not a source state for any of your transitions. Except auto transitions to_<state> there are no valid triggers. When you query triggers for "solid", you get "melt" and "sublimate":
from transitions import Machine
class Matter(object):
def say_hello(self): print("hello, new state!")
def say_goodbye(self): print("goodbye, old state!")
lump = Matter()
transitions = [
{ 'trigger': 'melt', 'source': 'solid', 'dest': 'liquid' },
{ 'trigger': 'evaporate', 'source': 'liquid', 'dest': 'gas' },
{ 'trigger': 'sublimate', 'source': 'solid', 'dest': 'gas' },
{ 'trigger': 'ionize', 'source': 'gas', 'dest': 'plasma' }
]
states = ['solid', 'liquid', 'gas', 'plasma']
m = Machine(lump, states, initial='liquid', transitions=transitions)
print(m.get_triggers('solid'))
# >>> ['to_solid', 'to_liquid', 'to_gas', 'to_plasma', 'melt', 'sublimate']from transitions.
jonra1993
commented on June 9, 2024
Hello @aleneum after using auto_transitions=False it worked as I expected thanks for your help. I have not noticed that before.
from transitions.
Related Issues (20)
- State transition during on_exception callback causes RecursionError
- "on_exception" is not invoked for "KeyboardInterrupt"
- Explicitly reexport package names
- GraphMachine: set proportional font or allow caller control HOT 3
- AttributeError: 'state' does not exist HOT 3
- prepare func raises Exception altough on_exception is defined HOT 1
- GraphMachine seems not working for parallel states HOT 1
- AsyncMachine transitions fail when a list of `State` objects are passed in to the FSM. HOT 2
- Cannot use Pydantic `BaseModel` class for models HOT 2
- All possible transitions are initialized, instead of those provided as an argument. HOT 2
- Machine get into wrong state. HOT 1
- after_state_change not triggered by set_state HOT 2
- AsyncMachine with queued transitions breaks when transition is cancelled
- AsyncMachine transitions aren't atomic HOT 4
- The Event and Machine have cyclic dependency. HOT 3
- Update COPR packages
- get_triggers does not get child states in HierarchicalAsyncMachine HOT 3
- may_ function in parallel state does not report correct value HOT 1
- 3.12 Performance HOT 10
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from transitions.