Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any idea how to sort the state machines? #115

Open
sefirosweb opened this issue Sep 24, 2021 · 3 comments · May be fixed by #172
Open

Any idea how to sort the state machines? #115

sefirosweb opened this issue Sep 24, 2021 · 3 comments · May be fixed by #172

Comments

@sefirosweb
Copy link
Contributor

My bot starts to have a HUGE number of functions :D I'm proud of that, and I reuse a lot of functions in a lot of things, it saves me time and bugs

BUT I have a little problem, I start to have a tree too much and it does not begin to be clear,

One of the "" problems "" is that when I use the same function in different behaviors they are seen in all, (example take items from the chest / floor)

I don't know from where starts / end the functions

Any advice on how to improve this?
I attach my tree of states

Screenshot_2

I was thinking of making each nested a dropodown / or a rectangle but I don't know if it could be more confusing

@sefirosweb
Copy link
Contributor Author

Any one use them? seems i'm are alone developing with state machine XD

I'm on the right path, right? 🙁

@sefirosweb
Copy link
Contributor Author

Guys I have an idea to improve the webservice,

Istead to have a larger buttons with a bit "indent" why not create a folder / subfolders style? adding the option to dropdown or not the sub behaviors

SImilar has:
image

I can do it myself, but first to save waste time what do you think? If you see ok i will develop

Also i think is necessary to move the bar bar manually instead fixed

image

@sefirosweb
Copy link
Contributor Author

Preview:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant