Back to the main page.
Bug 1636 - ft_select_range uses data limits instead of figure axis limits for horizontal selection
Status | CLOSED WORKSFORME |
Reported | 2012-08-08 14:49:00 +0200 |
Modified | 2013-01-17 10:38:17 +0100 |
Product: | FieldTrip |
Component: | plotting |
Version: | unspecified |
Hardware: | PC |
Operating System: | Mac OS |
Importance: | P3 normal |
Assigned to: | Roemer van der Meij |
URL: | |
Tags: | |
Depends on: | |
Blocks: | |
See also: |
Robert Oostenveld - 2012-08-08 14:49:22 +0200
Created attachment 296 screenshot, the selection should be vertically larger This can be reproduced with figure; plot(x, y, '.'); set(gcf, 'WindowButtonDownFcn', {@ft_select_range, 'multiple', false, 'xrange', true, 'yrange', false, 'callback', @disp, 'event', 'WindowButtonDownFcn'}); set(gcf, 'WindowButtonUpFcn', {@ft_select_range, 'multiple', false, 'xrange', true, 'yrange', false, 'callback', @disp, 'event', 'WindowButtonUpFcn'}); set(gcf, 'WindowButtonMotionFcn', {@ft_select_range, 'multiple', false, 'xrange', true, 'yrange', false, 'callback', @disp, 'event', 'WindowButtonMotionFcn'}); which results in a figure (with rubber-band selection) like in the attached figure
Roemer van der Meij - 2012-08-16 18:19:06 +0200
Weird, I can no longer replicate this. The rubberband-box limits are set to the current axis limits, every time the function is run. I can't think of a situation right now where this would be different. I don't think we did anything special at that time.