[Bug] Dependency function problem in macro parameters

[TIME]

1. What happened.
   When the invisible effect in Dependency is applied to a parameter, that parameter disappears and the parameters below it are moved up one place in turn.This results in the wrong parameters being entered into the device.
2. Does it happen consistently, or randomly?
   It happen consistently.
3. The steps to reproduce it.
   
   
   
   Under normal circumstances:
   
   When the “invisible” condition is met:
   
   

-----After testing, the problem still exists in 4017-----

[HYLK]

I wonder, if the ports are connected to a wire, do the wires move as well? If so, I guess this is intended behaviour but confusing. It would be better if said ports would get a different colour instead, indicating they are not visible or something.

[Delta_Research]

I think this is the same bug that I’m experiencing.

[Bug] Parameter order gets messed up randomly, usually on the bottom parameters

This bug seems to be difficult to reproduce and is slightly different every time. When I was working on my colorize macro, the parameters get messed up in order the first time, so I wired the parameters to the correct devices. However, when I restarted WM, this time the name AND the parameter order got messed up. There are also sometimes “phantom” parameters that do nothing and replace an actual parameter.

[TIME]

the wires wont move,thats the problem :D,the wrong parameters will be entered into the device.

[TIME]

oh,that’s what it is, but it does lead to the wrong results.

[Stephen]

Thanks for the bug report for good reproduction steps! I’ll look into it shortly.

[Stephen]

Update:

This bug has been fixed in the next build of WM.