Changing macro input to wildcard fails if other wildcard inputs in use
If I have existing wildcard inputs in a macro that are connected to something in the macro, then I add a new input (any non-wildcard type) and try to change that input type to wildcard, the input doesn't change, even though the details panel says it is now a wildcard:
So easily workaroundable and also unlikely to go unnoticed so it's pretty minor, but worth reporting.
Expected result: The input type should change to wildcard (or if it's difficult to fix, the details panel should at least display the type correctly i.e. not allow you to change it to wildcard)
I was able to reproduce this issue on our end. I have written up a report and I have submitted it to the developers for further consideration. I have provided a link to the public tracker. Please feel free to use the link provided for future updates.
Make it a great day
answered May 05 '17 at 07:09 PM
Rudy Q ♦♦ STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here