Opps…. I was using the wrong syntax: MarkedClean is an EventName and I was accidentally treating it as a PropertyName. Also, ignore the “MarkedDirty” reference in the error message which was in response to a different version of the listener. #NewbieMistake

The first syntax below is the correct one to use with MarkedClean, as Yair demonstrated in this blog post.

el = addlistener(hSource, EventName, callback)  
el = addlistener(hSource, PropertyName, EventName, callback)

I noticed that listeners responding to MarkedClean in geoaxes throw an error even though MarkedClean appears to have public ListenAccess.

ax = geoaxes('basemap','satellite');
MC = metaclass(ax);
E = MC.EventList;
E(10)

 GraphicsMetaEvent with properties:

    HasCallbackProperty: 0
                   Name: 'MarkedClean'
            Description: 'description'
    DetailedDescription: 'detailed description'
                 Hidden: 1
           NotifyAccess: 'public'
           ListenAccess: 'public'  <--------
          DefiningClass: [1×1 matlab.graphics.internal.GraphicsMetaClass]

But when assigning a listener to geoaxes,

addlistener(ax,'MarkedClean', ...
    'PostSet', @(a,b)myFunc(a,b));

Error using matlab.graphics.axis.GeographicAxes/addlistener
The name 'MarkedDirty' is not an accessible property for an instance of class 'matlab.graphics.axis.GeographicAxes'.

I’ve used this type of listener in other axes without problem but I don’t understand what’s blocking it with geoaxes.

@Tucker – AFAIK markedClean still works even in the very latest release. In recent years MathWorks added a few documented hooks for trapping axes updates etc., but the markedClean event still seems to be a general common mechanism.
If and when you have some information on the transforms, then please let me know.

Is “markedClean” still your recommendation for wanting to redraw graphics primitive like objects? I’m working on trying to make some native-like graphics objects and need to know when to redraw.

Also, are you still looking for window transforms / data2pixel and its inverse? I have some info that you might find helpful. Will be posting code soon.

-Tucker

Yair – It looks like setting the Axes ‘NextPlot’ property to ‘add’ may prevent the resetting of HitTest. There is more behavior to investigate, but at least I seem to be on some kind of path. Thank you again

@Nick – this is a “known” undocumented side-effect of using the high-level plotting functions (such as plot), which reset several axes properties including HitTest and Tag. In contrast, the low-level plotting functions (such as line) do not reset these properties.

I just learned a fun fact: plotting to an axes object who’s HitTest property is set to ‘off’ appears to reset HitTest to ‘on’

You are my hero – thank you for this invaluable resource. And thank you for pointing me to an (embarrassed) *documented* feature.

Cheers!

@Nick –

set(gca,'HitTest','off')

I thought maybe I could set a listener for ObjectBeingDestroyed, but it fires after the object is gone (or there’s a synch issue).

Is there some kind of ObjectAboutToBeDestroyed or DestroyObjectRequest thats double-secret-undocumented?

Any thoughts as to how I can hook into this behavior (or as a welcomed alternative, turn off the ability to delete axes with the keyboard – I mean seriously, why is that even a thing?)

function testAxesDelete
    hs = struct('fig', figure);
    hs.fig.MenuBar = 'none';
    hs.fig.ToolBar = 'figure';
    hs.fig.KeyPressFcn = @myKeyCallback;
    
    hs.ax = axes;
    hs.line = plot([0 0], [-1 1]);

    hs.ax.DeleteFcn = @myDeleteCallback;
    hs.ax.ButtonDownFcn = @myButtonCallback;
    
    addlistener(hs.ax, 'ObjectBeingDestroyed', @obdCallback);    
end

function myKeyCallback(hobj, event, varargin)
    disp('Pressed a key on figure!');
    disp('Axes still is deleted if you press delete with the axis selected');
    disp('Axis is deleted prior to executing this function')
    keyboard
end

function myDeleteCallback(hobj, event, varargin)
    disp('Deleting axes!');
    disp('Axis is deleted prior to executing this function')
    keyboard
end

function myButtonCallback(hobj, event, varargin)
    disp('Does not intercept delete key');
    keyboard
end

function obdCallback(hobj, event, varargin)
    disp('Object being destroyed callback');
    disp('this happens *after* the axes have been deleted ');
    keyboard
end