Skip to content

Add support for globbing in oscmatch...#24

Open
foolswood wants to merge 1 commit into
michaelforney:mainfrom
foolswood:osc_improve_matching
Open

Add support for globbing in oscmatch...#24
foolswood wants to merge 1 commit into
michaelforney:mainfrom
foolswood:osc_improve_matching

Conversation

@foolswood
Copy link
Copy Markdown
Contributor

and some unit tests for it.

I started thinking about how to get the device info from the backend to the GUI(s) and think this might help on that front.

Basically if you could do a request to /inputs/*/* then you could get the channel info (and which support what) out by the presence of the various endpoints.

My initial thought was to have a /device part of the tree. I still think this might be nice to give the name (and maybe number of inputs and outputs so it's easier to allocate memory in C-like languages). But when I started putting all the info about names/flags etc in that subtree it got very duplicate-y and required the client to know how that info related to paths in another bit of the tree, which seemed a bit silly.

I am aware that the oscmix.c doesn't know how to handle globs for its arrays yet, but if you think this is a reasonable sort of thing to do then I don't think that should be particularly hard to fix.

and some unit tests for it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant