Yes, In QM, disabling macros and triggers with Ctrl+D is indeed very convenient.
there is another scenario. For instance, in a project, I've defined a library file. I want to create its second version, so I intend to disable the first version. I don't want to delete it. If I don't disable it, some variables or functions in the two library files might conflict. Or is there a better way to handle this?
there is another scenario. For instance, in a project, I've defined a library file. I want to create its second version, so I intend to disable the first version. I don't want to delete it. If I don't disable it, some variables or functions in the two library files might conflict. Or is there a better way to handle this?