RE: export in csv does not save details

Franz Mayer wrote:

> And I don't get the point, why it should not be possible to export packet
> details in CSV.

The reason why the UI should not offer that possibility is that *no code
has been written to implement it*.  At least one reason why no code has
been written to implement it is that what "it" means isn't yet defined -
see below (and see my previous mail).

> It would be a nice feature, because I wanted to do some
> calculation on my own and therefore a CSV (can be opened in Calc or Excel)
> could be helpful!

See my previous mail for why, although it's certainly a *useful* feature,
it's not an *easy* feature to implement.  You can't just give it a list of
field names and say "export these", because that doesn't answer the
question of what "export these" means when, for one of "these", there's
*more than one instance* in the protocol tree.  Should it always export
the first one?  Should it always export the last one?  Should it export
all of them - and, if so, how?  It probably couldn't use commas to
separate the different values, unless CSV is "defined" to allow a "value"
to be a comma-separated list in brackets, or something such as that.  Or
should it simply fail if more than one instance of the field is found? 
Note that, as I indicated in a previous message, if "export packet fields
as CSV" failed if more than one instance of a field existed in the packet,
that would prevent exporting IP addresses if you have any form of
tunneling with two layers of IP header.