#151 generic protocol: (Line and var) separators gets wrong in <output>

[Anonymous]

Originally created by: hanzu...@gmail.com

The issue here is that you have a protocol with both <input> and <output>, the separators <var_separator> and <line_separator> from <input> will override any separators defined in <output>, no matter the order of <input> and <output> in the xml file.

What steps will reproduce the problem?
1. Create a protocol with both <output> and <input> with different separators (see attachment for example file).
2. Start FG with --generic=file,in,1,input.txt,AFGcockpit  --generic=file,out,1,output.txt,AFGcockpit
3. Verify that FG can read the input (attached file changes parking brakes).
4. Study the output and see that the separators are same as for <input>

What is the expected output? What do you see instead?
In the attached files the input is separated by comma for variables and \r\n for lines. The output should be \r\n for both variables and lines.
The expected output is:
M1
B0
T000
M2
B0
T000
...
M15
B1
T000

but instead I get:

M1,B0,T000
M2,B0,T000
...
M15,B1,T000

What version of the product are you using? On what operating system?
FlightGear Mac os X 1.9.1 (232) on Mac OS 10.5.8

Please provide any additional information below.
A workaround is to define two separate protocols, one for input and one for output.

[Anonymous]

Originally posted by: bre...@gmail.com

Not reproducible with FG2.0/2.2.0. Log history also shows a related fix.

Labels: Network
Status: Testing

[Anonymous]

Originally posted by: bre...@gmail.com

Apparently fixed.
Otherwise reopen or create fresh report with new info.

Status: Fixed

[Anonymous]

Originally posted by: bre...@gmail.com

(No comment was entered for this change.)

Status: Temp

[Anonymous]

Originally posted by: bre...@gmail.com

(No comment was entered for this change.)

Status: Fixed

[Anonymous]

Originally posted by: gijsrooy

(No comment was entered for this change.)

Labels: Milestone-2.0.0