[FieldTrip] cfg.latency and ft_timelockanalysis

[Nathan Weisz]

hi,

i just noticed that the option cfg.latency has been deprecated from ft_timelockanalysis.

does this have a specific reason? seems to be done on purpose :-)

i am asking because i always thought that it was a nice feature when later using beamformer analysis (lcmv) to have a more narrow window to calculate e.g. power (using ft_sourcedescriptives) or to orient sources when later applying filters to raw data, and to have a wider window including also prestim periods for covariance estimation. 

of course the workaround is to run two timelocks with a redefinetrial in between. but it appears rather awkward.

thanks for any input,
nathan