That’s all there is to it: Whenever YTick changes its value(s), our callback function ( m圜allbackFunction) will automatically be called. Unfortunately, addlistsner cannot always be used, and I keep forgetting under which circumstances, so I generally use handle.listener directly as above: It’s simple enough to use that I find I never really need to use the simple addlistener wrapper, but you are welcome to try it yourself. If you take a look at the addlistener function’s code, you will see that it also uses setappdata after creating the listener, for exactly this reason. Forgetting to store listener handles is a common pitfall when using them. If we had not stored this listener handle somewhere, then Matlab would have immediately deleted the listener hook and our callback function would not have been called upon tick value updates. This ensures that the listener exists for exactly as long as the axes does. Note that we have used setappdata to store the hListener handle in the axes. HListener = handle.listener(hhAxes, hProp, 'PropertyPostSet', 'YTickListener', hListener) HProp = findprop(hhAxes,'YTick') % a schema.prop object
HhAxes = handle(hAxes) % hAxes is the Matlab handle of our axes Setappdata (hAxes, 'YTickListener', hListener ) listener (hhAxes, hProp, 'PropertyPostSet', ) HProp = findprop (hhAxes, 'YTick' ) % a schema.prop object HhAxes = handle (hAxes ) % hAxes is the Matlab handle of our axes The idea is to use the built-in handle.listener function with the PropertyPostSet event, as follows: Such a mechanism was already demonstrated here in 2010, as one way to achieve continuous slider feedback.
#Matlab format axis update#
This can be done by using UDD, or more precisely the ability to trap update events on any property (in our case, YTick). The solution – using a property change listenerĪ better way to solve this problem is to simply trap changes to the displayed tick values, and whenever these occur to call our dedicated function to update the labels according to the new tick values. Also, if we modify the axes limits explicitly (via the corresponding YLim property) or indirectly (by modifying the displayed plot data), then the callbacks are not called and the labels are not updated. This will work for these cases, but we need to do it separately for zoom and pan.
Of course, we can always trap the zoom and pan callback functions to update the tick labels dynamically while keeping the tick values automatically. So, if we now zoom or pan the plot, our new labels remain unchanged although the tick values have changed, causing much panic and frustration… If we also set the tick values manually, this solves that problem but leaves us with another: now, when we zoom or pan, we no longer see any ticks or tick labels at all! Have you ever tried to customize the way in which tick labels appear in Matlab plot axes?įor example, setting the numerical precision of the labels, or adding some short descriptive text (for example, the units)? If you have, then I bet that you have encountered the following dilemma: Once we modify the tick labels (for discussion sake, let’s assume the Y axis, so this is done by updating the YTickLabel property), then the corresponding YTickLabelMode property changes from ‘auto’ to ‘manual’ and loses its relationship to the tick values ( YTick).
0 kommentar(er)
