Malcolm Lidierth

@Doug

Many thanks. Looks like MATLAB is insisting on pass-by-value syntax in R2012b:
For backwards compatibility, I avoid [~], but your fix seems to work equally well with:

obj.hgcontainer=subsasgn(obj.hgcontainer, index, val);

Same problem could also arise at line 38. Change to:

obj.(index(1).subs)=subsasgn(obj.(index(1).subs), index(2:end), val);

FYI: Latest code for this is now in a GIT repo. See:

http://waterloo.sourceforge.net

Regards
Malcolm

@ Aurelien

w=com.mathworks.mde.desk.MLDesktop.getInstance().getMainFrame().getWindows()

returns a list of Windows including those for GWait.

Call
w(N).dispose()
to close the relevant windows.

Note that releases system resources, but does not delete the reference as per Java docs. The window can be reconstructed with a call to show.

Accepted - I should make that easier.

Malcolm

@Sebastian

I thought about this a bit more. The only problem I can see is in setting the visibility property for hgjavacomponents– everything else seems to work as intended. The problem is that GCardPane is generic – it has no “knowledge” of whether its contents are another GCardPane or a single layer uipanel. It manages OK regardless until undocumented components such as hgjavacomponents are added (which are not "seen" by all MATLAB search functions).

The quickest approach might be to create a couple of custom-subclasses: [1] of GTabContainer using [2] a GCardPane that “knows” the contents of the container. e.g by adding a new property (you could probably just use the appdata area but that would be less consistent with the overall design).
The outer tab pane would simply need to store a reference to the inner tabbed pane. Then overload setSelectedIndex for the outer card pane to look at the selection on the inner tab container before setting the visible properties to ‘on’ only for those hgjavacomponents that are children of the selected card in the inner container.
That would mean changing 1 method – setSelectedIndex - and adding support via a method (or the constructor) for the new property. Everything else would work (I think) so could just be inherited from the superclass. It should also allow nesting to arbitrary levels if you might need that later.

I think nested panels with undocumented features at the inner levels is probably stretching things a bit beyond what most users want - so I'll not put this on the TODO list.

Great idea. Wondering why ML did not do this. Seems pretty obvious. Filter objects are much easier to work with. This should have been a no brainer for ML.
Thanks

Hi,

I'm trying to learn Waterloo and jzy3d for Matlab.

Do you have code for the demo .jar?
It would help a lot, thanks.

I've posted on the sf forum as well.

Ivan