Suggestion: deactivate output for mc.route on index 0

Hey there,

a quick search for mc.route in the forums didn't yield anything, so I thought I would throw this out here: It seems to me that mc.route is the gate we never received!

I imagine it might not be the most controversial thing to suggest that the inlet order in gate has always been wrong (see this old thread https://cycling74.com/forums/gate-inlets), but most likely there are too many projects relying on how gate was originally devised to ever change it at this point. PureData has no right-to-left message priority and perhaps Miller just designed gate in the same way we read text: from left-to-right. However, I have to say that I have virtually 0 cases in my projects where I ever wanted the index inlet on the left side of the object, i.e. where I want to select if the gate is open or not or which outlet to choose from after sending the value that should be blocked or routed through gate. Every, single, time, I have to use trigger or some other extra message flow object to ensure that the outlet index is first set before the value is sent. I mean, this is very PureData-esque, but okay...

I finally had a closer look at mc.route after all this time of using MC (it never occurred to me so far, I have to admit) and I realized it is just gate with it's inlets reversed! Rejoice!

But wait, there is one little detail: index 0 provokes the same behavior as index 1, in that the value sent in the left inlet is just routed to the first outlet the same.

Thus, here is my plead: can we make mc.route not send the value entered in the left inlet to any outlet if the index is <1?

P.S., to the Cycling '74 employee to implemented mc.route: if you looked at gate and said to yourself this is too much overhead to deal with and implemented mc.route for the specific purpose of routing messages from objects like mc.snapshot~ or similar... I want to both thank you, but also hate that it had to come to such a cheaky way to deal with this persisting issue, finally. At least, there is a "vanilla" way to have a reverse-gate.

Also, to everyone, maybe I am missing a "vanilla" object that is the exact copy of gate expect for the inlet order reversal. There are so many objects at this point and I would not be lying that I keep "re-discovering" objects, thinking "oh yeah, this would have been so much easier had I just remembered..."