Back to the main page.
Bug 717 - ft_getopt does not return an output if the input is something else than a cell-array, a struct, or a config object
| Status | CLOSED FIXED |
| Reported | 2011-05-31 14:27:00 +0200 |
| Modified | 2011-06-01 13:39:02 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Mac OS |
| Importance: | P1 normal |
| Assigned to: | Jan-Mathijs Schoffelen |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Jan-Mathijs Schoffelen - 2011-05-31 14:27:25 +0200
Sometimes, people call ft_XXX like this: ft_blabla([], data). If in the long run, the assignment of default cfg options will be done by ft_getopt, an output should be generated, also when the input 'obj' == []
Jan-Mathijs Schoffelen - 2011-05-31 14:28:19 +0200
I added the following lines in ft_getopt (>line 63): elseif isempty(opt) % input can be an empty variable (e.g. when calling a ft-function with % ft_XXX([], data) val = default;
Robert Oostenveld - 2011-05-31 15:33:22 +0200
can you please check that this is consistent with the mex-file implementation of ft_getopt? it means that you have to look at the c-code... another change of learning mex programming ;-)