Pretty much what the title says. I had a macro which had no connections to outside the macro, only some floats connected to the output of the macro. When deleting modules that were connected like this the software crashed.
Edit: Only crashes when a module inside a macro is connected to the input or output "ports" of the macro. Can be worked around by simply disconnecting the relevant lines. I haven't tested if this happens if the deleted module is connected to another module that in turn is connected to the i/o of the macro.
Pretty much what the title says. I had a macro which had no connections to outside the macro, only some floats connected to the output of the macro. When deleting modules that were connected like this the software crashed.
Edit: Only crashes when a module inside a macro is connected to the input or output "ports" of the macro. Can be worked around by simply disconnecting the relevant lines. I haven't tested if this happens if the deleted module is connected to another module that in turn is connected to the i/o of the macro.
(v0.6.2 Windows)