Back to the main page.

Bug 240 - interactive topo/single plotting does not work

Status CLOSED FIXED
Reported 2010-11-26 16:51:00 +0100
Modified 2011-01-26 15:38:29 +0100
Product: FieldTrip
Component: plotting
Version: unspecified
Hardware: PC
Operating System: Windows
Importance: P1 normal
Assigned to: Arjen Stolk
URL:
Tags:
Depends on:
Blocks:
See also:

Arjen Stolk - 2010-11-26 16:51:21 +0100

When topoplotting with interactive = yes, the channel selection box does not appear. Revision r2121 still allows to do this, but the current FT version does not. It is likely to be caused by changes in ft_select_channel. Here, ft_selectrange is called with an 'event' keyvalue which is defined at line 65 of ft_select_channel in the current version. current version: set(gcf, 'WindowButtonDownFcn', {@ft_select_range, 'multiple', true, 'callback', {@select_channel_multiple, callback}, 'event', event}); r2121: set(gcf, 'WindowButtonMotionFcn', {@ft_select_range, 'multiple', true, 'callback', {@select_channel_multiple, callback}, 'event', 'WindowButtonMotionFcn'});


Arjen Stolk - 2010-11-28 10:56:34 +0100

At line 65, event is only defined once. This is problematic when multiple event functions are set to the gcf. Therefore, the revision 2122 changes to ft_select_channel are undone for all three gui function settings. An example of one such change: set(gcf, 'WindowButtonDownFcn', {@ft_select_range, 'multiple', true, 'callback', {@select_channel_multiple, callback}, 'event', event}); -> set(gcf, 'WindowButtonMotionFcn', {@ft_select_range, 'multiple', true, 'callback', {@select_channel_multiple, callback}, 'event', 'WindowButtonMotionFcn'});


Robert Oostenveld - 2011-01-26 15:37:08 +0100

I closed all bugs that were resolved prior and including 2011-01-25. All resolved bugs should have been discussed by now, therefore we don't want to see them again in the next meeting. Instead, in the next meeting we want to see the recent improvements and fixes.


Robert Oostenveld - 2011-01-26 15:38:29 +0100

I closed all bugs that were resolved prior and including 2011-01-25. All resolved bugs should have been discussed by now, therefore we don't want to see them again in the next meeting. Instead, in the next meeting we want to see the recent improvements and fixes.