Back to the main page.
Bug 582 - 'q' in ft_databrowser doesnt work when in 'component' viewmode/input
| Status | CLOSED FIXED |
| Reported | 2011-04-15 11:04:00 +0200 |
| Modified | 2011-07-13 14:46:40 +0200 |
| Product: | FieldTrip |
| Component: | core |
| Version: | unspecified |
| Hardware: | PC |
| Operating System: | Linux |
| Importance: | P1 normal |
| Assigned to: | Jörn M. Horschig |
| URL: | |
| Tags: | |
| Depends on: | |
| Blocks: | |
| See also: |
Stephen Whitmarsh - 2011-04-15 11:04:57 +0200
Funny, since it does work with timelocked data.
Robert Oostenveld - 2011-05-05 13:12:42 +0200
should be checked/fixed once the new implementation is done
Ingrid Nieuwenhuis - 2011-05-05 22:44:46 +0200
A maybe related thing that happens, if the GUI buttons are used (by clicking with mouse) the short cut keys (on key board) don't work anymore. (including the 'q'). Mouse still works normally, and closing the figure by clicking on the cross still works as it should. Just annoying. Ingrid
Jörn M. Horschig - 2011-07-06 15:37:03 +0200
works with new implementation @Ingrid: I think the problem you describe is more Matlab related. The problem is that the callback function does only work if the handle is the currently selected object. If you click a button, the button's handle becomes the object of interest. I asked Google about this, and he agrees: http://www.mathworks.cn/matlabcentral/newsreader/view_thread/158449 There seems to be a workaround though by disabling the button, drawnow and enabling it again - and just before sending this comment, I included this in the code and commited the change. ft_databrowser_new ll.723ff
Robert Oostenveld - 2011-07-06 15:51:31 +0200
to solve the handle issue in ft_databrowser there is the getparent helper function. It will determine the uppermost parent of any figure element handle. Perhaps this can be used to resolve the issue here (which I did not look into in detail)
Jörn M. Horschig - 2011-07-06 16:41:43 +0200
it's solved ;) from what I got from the mathworks forum, the only reliable workaround is by disabling and enabling the button.