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

Statemachine Editor: Connecting state outcomes becomes progressively slower based on the number of existing state outcome nets #12

Closed
josephcoombe opened this issue Dec 6, 2017 · 3 comments

Comments

@josephcoombe
Copy link

Was using the Statemachine Editor to edit a sm with 10 states and ~25 state outcome transitions total.

Once I passed about 20 state outcome transitions (i.e. I had made 20 connections between states), I noticed that making new connections became progressively slower (and laggier).

I'd click on the state outcome name in the origin state and the screen would update slowly (and freeze for fractions of a second) while I tried to drag the net to the destination state.

This lagginess only manifests itself when making state transition connections and appears to get worse as the number of state transitions connections made increases.

(I'm working with 32 MB of RAM with a good processor and graphics card). Thanks!

@pschillinger
Copy link
Member

pschillinger commented Dec 7, 2017 via email

@pschillinger
Copy link
Member

Should be much smoother now, not dependent on the number of transitions anymore, and also update a transition while hovering over states. Hope this improves the performance for you.

@josephcoombe
Copy link
Author

Yep, loaded the same Behavior with the changes in PR #13 and was able to edit the transition net lists without the previous lag. Thank you!

fmessmer added a commit to fmessmer/flexbe_app that referenced this issue Jan 29, 2021
add nwjs mirror as download alternative
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

No branches or pull requests

2 participants