Back to the main page.

Bug 103 - with addition of optional cfg.inputfile ylim error

Reported 2010-07-01 15:55:00 +0200
Modified 2014-12-24 22:43:03 +0100
Product: FieldTrip
Component: plotting
Version: unspecified
Hardware: PC
Operating System: Linux
Importance: P1 enhancement
Assigned to: Robert Oostenveld
Depends on:
See also:

Tim Engelkes - 2010-07-01 15:55:19 +0200

ft_singleplotER(cfg, data) In de code staan herhaaldelijk nieuwe loops die nieuwe varargin en nargin voorwaarden aanhalen wat mogelijk voor dit probleem zorgt als ik inputfile inbouw. cfg=[]; cfg.inputfile={('Tim_testdata/freqsingle')} ft_singleplotER_new(cfg) ??? Error using ==> set Bad property value found. Object Name : axes Property Name : 'YLim' Value must be a 2 element vector. Error in ==> ylim at 44 set(ax,'ylim',val); Error in ==> ft_singleplotER_new at 315 ylim([ymin ymax]);

Robert Oostenveld - 2010-12-15 20:47:40 +0100

plotting functions don't have to support cfg.inputfile. The inputfile option also did not make it into ft_singleplotER.

Robert Oostenveld - 2011-01-05 11:56:55 +0100

selected a long list of resolved bugs from roboos and changed the status into "RESOLVED"

Robert Oostenveld - 2011-01-05 12:01:00 +0100

selected all old bugs from roboos with status RESOLVED and changed it into CLOSED

Robert Oostenveld - 2014-12-24 22:43:03 +0100

(In reply to Robert Oostenveld from comment #1) note that by now it is supported to use cfg.inputfile in the plotting functions.