You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When layouting using a GraphLayoutEngine like the LibavoidLayoutProvider it would be nice to be able to cancel a started operation. This class creates a LibavoidServer, which writes and reads the graph via I/O. For large diagrams, a server might wait for a long time (20+ seconds) for a response of the routed graph. Having a way to cancel this operation, for example using the progress monitor, might be very useful. If there isn't such an option yet, I think it would be an approvement to implement one.
I'm keen to hear your thoughts on this topic, especially whether such a feature aligns with your design priorities or if you see alternative approaches to addressing this situation.
Desired behavior
Right now im using a workaround, that destroys the Server Process, if my ElkProgressMonitor is canceling. I have the server accessible via the LayoutProvider it was started in, so the process can be terminated without any memory leaks.
The text was updated successfully, but these errors were encountered:
Description
When layouting using a
GraphLayoutEngine
like theLibavoidLayoutProvider
it would be nice to be able to cancel a started operation. This class creates aLibavoidServer
, which writes and reads the graph via I/O. For large diagrams, a server might wait for a long time (20+ seconds) for a response of the routed graph. Having a way to cancel this operation, for example using the progress monitor, might be very useful. If there isn't such an option yet, I think it would be an approvement to implement one.I'm keen to hear your thoughts on this topic, especially whether such a feature aligns with your design priorities or if you see alternative approaches to addressing this situation.
Desired behavior
Right now im using a workaround, that destroys the Server Process, if my ElkProgressMonitor is canceling. I have the server accessible via the LayoutProvider it was started in, so the process can be terminated without any memory leaks.
The text was updated successfully, but these errors were encountered: