Comments on: Displaying hidden handle properties

By: Matlab’s HG2 mechanism | Undocumented Matlab

Matlab’s HG2 mechanism | Undocumented Matlab — Fri, 07 May 2010 10:53:01 +0000

[...] “Handle Graphics 2nd generation”, was already reported in the past as an undocumented hidden figure property (UseHG2). In normal Matlab usage, this boolean property is ‘off’: >> [...]

By: Axes LooseInset property | Undocumented Matlab

Axes LooseInset property | Undocumented Matlab — Wed, 24 Mar 2010 18:18:57 +0000

[...] another undocumented property of Matlab axes, ContentsVisible, was described by Matt Whittaker in a comment on my original article that introduced undocumented properties [...]

By: Customizing print setup | Undocumented Matlab

Customizing print setup | Undocumented Matlab — Wed, 25 Nov 2009 20:27:10 +0000

[...] the figure-specific print setup is stored in another hidden property, PrintTemplate [...]

By: Cris

Cris — Mon, 28 Sep 2009 09:40:00 +0000

Hey Yair, nice blog!

The ‘ApplicationData’ property might not be documented, but the GETAPPDATA and SETAPPDATA access functions are. It’s just a better structured implementation of the ‘UserData’ property. I still prefer using ‘UserData’ just because it’s more flexible. You get an error if you try to write anything that is not a stuct into ‘ApplicationData’.

By: Jason McMains

Jason McMains — Mon, 22 Jun 2009 18:26:24 +0000

@Yair, I finally think I figured out the problem, but its just a simple logic fix, every time I set the figure back to visible, I get the javaframe, and include that as the callback argument, and remove the old javaframe.

By: Jason McMains

Jason McMains — Tue, 09 Jun 2009 11:09:02 +0000

@Yair Unfortunately part of the code I’m working on is to “minimize to the system tray” like I can do in outlook and some other programs, which involves setting the visibility off to remove it from the task bar. I’ve gotten it to work some of the time, but certain sequences of commands still mess it up. The system tray icon is a great extra resource by the way, thanks for that little piece of wisdom:)

By: Yair Altman

Yair Altman — Sat, 30 May 2009 18:07:09 +0000

@Jason – the Java properties & callbacks are only relevant for visible figure frames. After all, how can you minimize/maximize a hidden frame??? Still, you can access these properties if you simply keep the figure visible and just set its position to somewhere off-screen (say, x=y=9999). The figure will remain visible although effectively hidden from view; it will remain displayed in the taskbar for this reason.

By: Jason McMains

Jason McMains — Fri, 29 May 2009 12:16:16 +0000

Yair, I’ve been looking around your getjframe program to get more of these “hidden handle properties.” This adds a lot of great extra functionality! Thanks for that! My question is that for some reason if I set the figure as invisible, all of those hidden callbacks, ie ‘WindowStateChangedCallback’ stop running. Any ideas?

Thanks
Jason

By: Matt Whitaker

Matt Whitaker — Fri, 15 May 2009 22:45:04 +0000

One nice little property of axes (using R2009a) is 'ContentsVisible'. Seems to be a nice way of toggling off the visibility contents of an axes while you update it.


plot(1:5)
t = text('Parent',gca,'String','Some Text');
set(gca,'ContentsVisible','off')
hold on
plot(5:-1:0)
set(t,'Position',[3,3])
set(gca,'ContentsVisible','on')

Sure it can be done numerous other ways but one scenario I have encountered is having a bunch of objects in an axes that have a mixture of visible states. You want to hide the contents while some update goes on. You have to find all the visible children, turn them off, keep that list in memory to only restore the visible stuff. The above seems much cleaner. I have not run into any gotchas yet. Thanks for the great website. You've been a great help over the last couple of years. Matt

By: Yair Altman

Yair Altman — Wed, 06 May 2009 17:22:40 +0000

Thanks Steve – that’s a nice catch that I probably would never have seen…
Hidden but documented: that’s a new one – I learn something new each day