timer causes drawing problem when loading a figure
1 view (last 30 days)
When running a GUI that has a timer callback, I notice that loading other GUI figures often fails (incorrect rendering). Is this known behavior? Are there any workarounds? I assume that the code loading the figures isn't immune to a timer spontaneously injecting code ... (e.g. updating the current figure or axes).
Edit: I'm using Matlab 2016a or newer (need to check specific version) on Windows 7. The code to load the figure is:
fig = openfig(fig_path);
After running this line the figure is rendered incorrectly. The figure is the wrong size and components are not where they are supposed to be.
The loaded figures have been created by GUIDE with no code generation (just figure layout). The remaining code (not shown) only adds callbacks and updates display strings; no components are created or positions/sizes changed.
Jan on 22 Sep 2017
A timer callback can change the current figure and current axes. How do you "load" the figures? Do the conflict appear inside the OpeningFcn? Which objects are concerned? Does any user-defined code run, which assume the current figure and axes to be static? Then a solution would be to define the 'Parent' property in every case:
FigH = figure;
AxesH = axes('Parent', 'FigH);
plot(1:10, rand(1, 10), 'Parent', AxesH);
Then a timer callback cannot disturb the creation.
Another idea would be not to change the current figure and axes inside timer callbacks.