Bug 57 - String list parameters are not parsed properly
Summary: String list parameters are not parsed properly
Status: CLOSED FIXED
Alias: None
Product: LinuxSampler
Classification: Unclassified
Component: LSCP (show other bugs)
Version: SVN Trunk
Hardware: PC Linux
: P2 normal
Assignee: Christian Schoenebeck
URL:
Depends on:
Blocks:
 
Reported: 2007-09-18 16:19 CEST by Grigor Iliev
Modified: 2008-04-11 14:13 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Grigor Iliev 2007-09-18 16:19:10 CEST
The problem is that, when you execute a command like:
SET MIDI_INPUT_PORT_PARAMETER 0 0 ALSA_SEQ_BINDINGS='0:0','0:1','14:0'
the parser removes the apostrophes and calls SetMidiInputPortParameter
with ParamVal="0:0,0:1,14:0", thus __parse_strings recognize it as a
list with a single value: 0:0,0:1,14:0 instead of list with 3 values,
and connection is made only to 0:0. And this affects all string list
parameters.
Comment 1 Christian Schoenebeck 2007-10-04 14:40:27 CEST
I just commited a quick hack to lscp.y to fix this bug. As this device 
parameters job is a bit cumbersome, please check if all device parameters work 
now as expected and that this fix did not break anything else!

Btw, I also commited a small refactoring of your introduced DB path arguments 
in lscp, you might remember that we discussed this once in an email. It's just 
a renaming of those grammer rules, so it shouldn't change any behavior, but 
just to let you know.