@Yaron – this post was written in 2012 and was extensively researched, so I believe that it does work on R2012a. My hunch is that either you have a bug in your code, or perhaps your figure window has some element which causes the annotation scribe layer to behave differently. Try to recreate my example on a new empty figure and then try to see what is different in your existing code/figure.

@Marcas – it is possible that the change in behavior changed across Matlab releases. It is using undocumented/unsupported internal code after all…

I did notice one thing while using the code. Where you have

x = [xValue, xValue];

I had different values for x(1) and x(2). When the coordinate conversion is done by the call to hgconvertunits, something is wrong with x(2). After the calls to pin the annotation, in particular:

hAnnotation.Pin(2).DataPosition = [x(2), y(2), 0];

it is in the expected position.

Marcas

A lot of things broke in R2014b due to the replacement of the graphics engine in this release (HG2). There’s probably a new way to do the same functionality in HG2, but I do not have the time or inclination to dive into this at the moment. Feel free to investigate and if you find out anything useful, come back here and place a comment for the benefit of others.

What about pinning annotation shapes such as ellipses and rectangles? Is there another property besides DataPosition that should be set for the length/width of these objects?

Thanks.

“Parameter must be a handle array.”

My Code:

 
tAnnotation = handle(annotation('textbox', [x(1),0.72,0.1,0.1],'String', 'Text','LineStyle','none'));
tAnnotation.pinAtAffordance(1);
tAnnotation.Pin(1).DataPosition = [timeOUTPlot(index1:index1), 10, 0];

Maybe you have some ideas? 🙂

@Andy – I don’t see why a textbox annotation cannot be used. Try playing with the relevant properties. If you’d like me to investigate this specific issue for you, email me.