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
I would propose to permit the removing of a LFO controller if it's not connected to any control. If it's connected, a dialog should ask a confirmation to the user to unconnect all controls driven by this controller before removing it.
Paul Giblock: Oops sorry. Forgot to close the issue. This should be resolved.
Paul Giblock: Reopened. The reason this wasn't Closed is because we need to make Peak Controller delete properly.
Tobias Doerffel: What about it? Is it fixed now?
Paul Giblock: No, it isn't fixed. You can remove the FX, then the controller will auto-destroy.
However, if you remove the Controller, the FX will not be destroyed becaues there is currently no way to destroy the FX without knowing where the view is. This goes back to the whole problem of LMMS's classes still being highly View dependent, even after the MV changes.
Any implementation suggestions?
The text was updated successfully, but these errors were encountered:
I would propose to permit the removing of a LFO controller if it's not connected to any control. If it's connected, a dialog should ask a confirmation to the user to unconnect all controls driven by this controller before removing it.
Paul Giblock: Oops sorry. Forgot to close the issue. This should be resolved.
Paul Giblock: Reopened. The reason this wasn't Closed is because we need to make Peak Controller delete properly.
Tobias Doerffel: What about it? Is it fixed now?
Paul Giblock: No, it isn't fixed. You can remove the FX, then the controller will auto-destroy.
However, if you remove the Controller, the FX will not be destroyed becaues there is currently no way to destroy the FX without knowing where the view is. This goes back to the whole problem of LMMS's classes still being highly View dependent, even after the MV changes.
Any implementation suggestions?
The text was updated successfully, but these errors were encountered: