Dear Jacek and Volkmar,
I agree with Volkmar and could reproduce the error with R2016b when
deliberately setting the position of an axis to overflow outside of its
parent figure. It seems that getframe.m was changed in R2017a to prevent
the error by cropping the rectangular area to be saved.
What does the following return?
global st
st.vols{1}.ax{1}.ax.Position
st.vols{1}.ax{2}.ax.Position
st.vols{1}.ax{3}.ax.Position
Best regards,
Guillaume.
On 06/06/18 15:57, Jacek Matuszewski wrote:
> Dear Volkmar,
>
> Thank you for your reply. I don't think I use anything other than
> default graphics window SPM brings up after calling it in matlab, I
> don't recall changing anything in default settings.
>
> I use check cheg on 1 image with X movie direction, default intervall
> (-90.0 90.0) 1mm stepsize and Select image: 1.
>
> Best,
>
> Jacek
>
>
> W dniu 06.06.2018 o 16:07, Volkmar Glauche pisze:
>> Dear Jacek,
>>
>> the mentioned code line in spm_ov_movie captures frames of the displayed image axis objects. The error message suggests that MATLABs getframe() function tries to capture image frames from an axis that extends beyond the figure (graphics window) boundaries. Normally this should not happen as spm_orthviews should always place each image axis entirely within the graphics window. Did you perhaps somehow zoom into the graphics window or move some of the image axes partially outside the graphics window?
>>
>> Best
>> Volkmar
>>
>> ########################################################################
>>
>> To unsubscribe from the SPM list, click the following link:
>> https://www.jiscmail.ac.uk/cgi-bin/webadmin?SUBED1=SPM&A=1
>
--
Guillaume Flandin, PhD
Wellcome Centre for Human Neuroimaging
University College London
12 Queen Square
London WC1N 3BG
|