In the help example for clirecorder
|
std::cout << " 'host=\"LabPC1\" or host=\"LabPC2\"'\n\t"; |
there is a statement, which in console looks:
LabRecorderCLI.exe foo.xdf 'type="EEG"' 'host="LabPC1" or host="LabPC2"'
but resolve_bypred accepts hostname, ex.:
pylsl.resolve_bypred("hostname='LabPC1'", timeout=5)
So, IMO example statement should be corrected!
My testing on host "himik":
- 'hostname="himik"' (as in example - single quotes outer, double around value) - FAIL, matches anything, print in stdout as double single: ''hostname=himik''
- 'hostname="himik"' - FAIL, matches anything, print in stdout ''hostname="himik"''
- "hostname='himik'" - WORK, stdout: ... matching 'hostname='himik''
- "hostname=himik" - FAIL, matched no stream!
- "hostname='himik'" - FAIL, matches anything, print in stdout '"hostname='himik'"'
- "host='himik'" - FAIL, stdout: "host='himik'" matched no stream! (host is not LSL property)
So, ONLY double quotes searchstr with a values in single quotes are able to work in Windows console.
complex query "hostname='himik' and type='EEG'" works.
Related issue: 99
The same behavior for LabRecorderCLI.exe 1.16.2 and 1.16.4 in Windows 10, in standard command console.
In the help example for clirecorder
App-LabRecorder/src/clirecorder.cpp
Line 10 in 84b9a6c
there is a statement, which in console looks:
but resolve_bypred accepts hostname, ex.:
So, IMO example statement should be corrected!
My testing on host "himik":
So, ONLY double quotes
searchstrwith a values in single quotes are able to work in Windows console.complex query
"hostname='himik' and type='EEG'"works.Related issue: 99
The same behavior for LabRecorderCLI.exe 1.16.2 and 1.16.4 in Windows 10, in standard command console.