Handling OSC messages - Is there a better approach than explicit route objects?


    Sep 21 2012 | 10:55 am
    When handling OSC messages I'm stuck creating many route objects to filter the incoming messages. This soon gets a bit messy as indicated by this patch.
    I'm working with the assumption that the messages can only handled with a switch case like scenario as they need to be explicitly known beforehand. However, if anyone has any suggestions for a more elegant and flexible method when filtering a large number of incoming OSC messages it would be most welcome.