Back to the main page.
Bug 2819 - Matlab2014b causing error with cfg.artfctdefvalue.zvalue.interactive
| Status | CLOSED FIXED |
| Reported | 2015-01-30 18:38:00 +0100 |
| Modified | 2015-07-15 13:31:10 +0200 |
| Product: | FieldTrip |
| Component: | external |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Windows |
| Importance: | P5 normal |
| Assigned to: | Robert Oostenveld |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Neo - 2015-01-30 18:38:25 +0100
FIELDTRIP Version 20150115 Hi, Recently I updated to Fieldtrip version 20150115 (was using 2014 Septemper version earlier) which resulted in a GUI error in the Matlab command window when any buttons in the interactive window were clicked. The GUI which I activated was cfg.artfctdefvalue.zvalue.interactive = 'yes'; I believe this error arises only on the Matlab2014b version since the error was not reproduced in Matlab2014a version. Given below is the error that was displayed: MATLAB COMMAND WINDOW showing trial 1, channel Cz No appropriate method, property, or field Key for class matlab.ui.eventdata.ActionData. Error in ft_artifact_zvalue>parseKeyboardEvent (line 1079) key = eventdata.Key; Error in ft_artifact_zvalue>keyboard_cb (line 680) key = parseKeyboardEvent(eventdata); Error using waitfor Error while evaluating UIControl Callback SAMPLE OF THE CODE: cfg=[]; cfg.continuous = 'yes'; cfg.trl = trl_2; cfg.artfctdef.zvalue.channel = data.label{jj}; cfg.artfctdef.zvalue.cutoff = 8; cfg.artfctdef.zvalue.trlpadding = 0; cfg.artfctdef.zvalue.artpadding = 0.05; cfg.artfctdef.zvalue.fltpadding = 0; cfg.artfctdef.zvalue.cumulative = 'yes'; cfg.artfctdef.zvalue.medianfilter = 'yes'; cfg.artfctdef.zvalue.medianfiltord = 9; cfg.artfctdef.zvalue.absdiff = 'yes'; cfg.artfctdef.zvalue.interactive = 'yes'; %%%%%% P.S. - I was aware of Bug2461 and that is why I upgraded to the latest FT version since a post dated this month states that FT had partially resolved the issues from Handle graphics 2.
Robert Oostenveld - 2015-02-27 08:56:49 +0100
this has been resolved as part of bug 2857