#Legend matlab code

Martin Apat 23:29 вЂ“ Yes, IвЂ™d say this is related. Update: As suggested below by Martin, here is a more elegant solution, which attaches a text object as a direct child of the legendвЂ™s hidden property DecorationContainer (we cannot add it as a child of the legend since this is prevented and results in an error): Please shoot me an email, or leave a comment below. We canвЂ™t win вЂ™em allвЂ¦ If you know a better solution, IвЂ™m all ears. Yes, this is indeed a bit of an unfortunate regression from HG1, but I currently see no other way to solve this. % Add destruction event listener (no need to persist here - this is done by addlistener)ДЄddlistener(hLegend, 'ObjectBeingDestroyed', HG2 legend with title Setappdata(hLegendAxes, 'listeners', hLinks) % persist hLinks, otherwise they will stop working when they go out of scope HTitle = title (hLegendAxes, 'Plot types:', 'FontWeight', 'normal', 'FontSize', 8 ) % Default is bold-11, which is too large % Link between some property values of the legend and the new axes % Add the axes title (will appear directly above the legend box) ) % as before % Create an invisible axes at the same position as the legend We also add an event listener to destroy the axes (and its title) when the legend is destroyed: We attach property listeners on the legendвЂ™s Units, Position and Visible properties, linking them to the corresponding axes properties, so that the title will change if and when the legendвЂ™s properties change (for example, by dragging the legend to a different location, or by resizing the figure).

Well, we can always resort to the poor-manвЂ™s solution of an optical illusion: displaying a an invisible axes object having the same Position as the legend box, with an axes title.

As such, if MathWorks chose to remove the Title property from the legend object, we will never find it. But it also means that legends are apparently not axes but rather unrelated siblings. This make sense, since they share many properties/features. As far as I could tell, HG2вЂ™s legend is a standalone object of class that derives from exactly the same superclasses as axes: Try as I may in HG2, I could find no internal handle anywhere to the legendвЂ™s axes or title handle. This is yet another example of such a spectacular failure on my part. In any case, maybe some of these problems for which I have not found a solution do have one that I have simply not discovered, and maybe they donвЂ™t вЂ“ in most likelihood I will never know.

#Legend matlab code

Well, the truth must be told that for each investigation that yields such a success story, there is at least one other investigation in which I failed to find a solution, no matter how hard I tried or countless hours spent digging (this is not to say that the success stories are easy вЂ“ distilling a solution to a few lines of code often takes hours of research). Readers of this blog always hear the success stories, and might mistakenly think that every problem has a similarly simple solution that can be hacked away in a few lines of nifty code. In this blog IвЂ™ve presented ~300 posts so far that discuss solutions to problems. Well, it turns out that hard enough (at least for me)вЂ¦ How hard then could a corresponding solution be in HG2 (R2014b+), right? Set(hTitle, 'String','Plot types:', 'VerticalAlignment','middle', 'FontSize',8) HLegend = legend(, 'Location','NorthWest') Set (hTitle, 'String', 'Plot types:', 'VerticalAlignment', 'middle', 'FontSize', 8 ) HLegend = legend (, 'Location', 'NorthWest' )