Back to the main page.
Bug 1213 - request: shut off fprintf if cfg.feedback='none' in ft_databrowser?
Status | CLOSED FIXED |
Reported | 2011-12-05 12:40:00 +0100 |
Modified | 2013-01-17 10:45:31 +0100 |
Product: | FieldTrip |
Component: | plotting |
Version: | unspecified |
Hardware: | All |
Operating System: | All |
Importance: | P3 enhancement |
Assigned to: | Roemer van der Meij |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Johanna - 2011-12-05 12:40:22 +0100
When using ft_databrowser for viewing components, I find it a bit cumbersome that so much gets printed to the command line every time I click to go to next trial or next set of components. Some of it is 'fprintf' statments within ft_databrowser, other is post-amble, calls to ft_prepare_layout, etc, other I'm not sure. Here is one example, after clicking to view next set of components, that appears on the command line: 'runica021' 'runica022' 'runica023' 'runica024' 'runica025' 'runica026' 'runica027' 'runica028' 'runica029' 'runica030' redrawing with viewmode component fetching data... done fetching artifacts... done preprocessing data... done the call to "ft_prepare_layout" took 0 seconds and an estimated 0 MB plotting artifacts... plotting events... plotting data... the call to "ft_prepare_layout" took 0 seconds and an estimated 0 MB plotting component topographies... done For clicking to see the next trial, I 'only' get this: redrawing with viewmode component fetching data... done fetching artifacts... done preprocessing data... done the call to "ft_prepare_layout" took 0 seconds and an estimated 1 MB plotting artifacts... plotting events... plotting data... the call to "ft_prepare_layout" took 0 seconds and an estimated 0 MB done Can any of this be shut off with a user cfg option? Thanks!
Johanna - 2011-12-05 12:41:21 +0100
Joern, re-assign if you don't want it :-)
Roemer van der Meij - 2012-03-02 15:40:32 +0100
Stealing a few bugs ;)
Roemer van der Meij - 2012-04-18 17:03:01 +0200
Ft_databrowser has been asked to turn it down a bit, hopefully it will comply.