On Mon, 2011-01-17 at 08:56 -0500, Martin Peach wrote:
On 2011-01-17 05:54, Roman Haefeli wrote:
I suppose my explanation from above missed its main point. From what I understood, the '//' is used as a wild-card for an arbitrary number of address fields, so that //position matches /body/arm/hand/position, but also /body/head/position. However, I'm looking for a shortcut for matching /body/arm/hand/position. Currently this needs to be done with 4 [routeOSC] objects:
[routeOSC /body] | [routeOSC /arm] | [routeOSC /hand] | [routeOSC /position]
My suggestion is to allow a shortcut:
[routeOSC /body/arm/hand/position]
Currently, [routeOSC /body/arm/hand/position] never matches anything.
Ah of course! I was thinking it already did that, but no.
I'll do that next.
Great!
Sorry for my overly verbose explanations.
Cheers Roman
On Mon, 2011-01-17 at 17:16 +0100, Roman Haefeli wrote:
On Mon, 2011-01-17 at 08:56 -0500, Martin Peach wrote:
On 2011-01-17 05:54, Roman Haefeli wrote:
I suppose my explanation from above missed its main point. From what I understood, the '//' is used as a wild-card for an arbitrary number of address fields, so that //position matches /body/arm/hand/position, but also /body/head/position. However, I'm looking for a shortcut for matching /body/arm/hand/position. Currently this needs to be done with 4 [routeOSC] objects:
[routeOSC /body] | [routeOSC /arm] | [routeOSC /hand] | [routeOSC /position]
My suggestion is to allow a shortcut:
[routeOSC /body/arm/hand/position]
Currently, [routeOSC /body/arm/hand/position] never matches anything.
Ah of course! I was thinking it already did that, but no.
I'll do that next.
I reckon you've already done it. Many thanks. This is incredibly useful!
Roman
-
Roman Haefeli