This example is still confusing to me, and I will have to study it more. My main concern is that in this type of situation, if the button1.setText() call was replaced by some other call that may depend on the state of an object that may have changed by button1.doClick(). Then, I believe I would need a drawnow() after button1.doClick() for things to occur in the correct order. With my limited understanding of how matlab interacts with the EDT thread, I almost feel as if I need many drawnow() calls in my matlab/swing gui.

The side-effect with dir is interesting. Also interesting is the case where we put a dir() command between the button1.doClick() and the button1.setText() calls. To me, it seems as if the button1.setText() call is always occurring on the main thread.

An interesting side-effect can be seen in the Command Window, if immediately after submitting edtTest() you issue any command that requires MT (e.g., another computation or even a simple dir) – this will be blocked until button1Callback ends, and before button2Callback starts. As far as I understand, this is because button2Callback is scheduled on the EDT (by button1Callback’s doClick() request) and is therefore executed after the Command Window command.

Or maybe I’m just mixing things up…

Thank you for your many helpful posts everywhere.

I am still a bit confused as to how this is supposed to work. In the following small example, I would have expected that all methods invoked on button1 get run on the EDT. This to me means that the setText() call would be queued up and run after button1′s callback has finished. However, this is not the case.

In other words, I would have expected the text ‘Button 1 text: New Button 1′ (or perhaps, ‘Button 1 text: Button 1′) to be the last thing displayed.

Can you provide me with more insight? Thanks!!

Sorry for the ill-formatted code. I cannot seem to get the code fragment tags to work.

function edtTest()
 
    % Create buttons
    button1 = javaObjectEDT('javax.swing.JButton', 'Button 1');
    button2 = javaObjectEDT('javax.swing.JButton', 'Button 2');
 
    % Assign callbacks
    set(handle(button1, 'CallbackProperties'), 'ActionPerformedCallback', {@button1Callback, button2});
    set(handle(button2, 'CallbackProperties'), 'ActionPerformedCallback', @button2Callback);
 
    % Do stuff
    button1.doClick();
    button1.setText('New Button 1');
    fprintf('Button 1 text: %s\n', char(button1.getText()));
    fprintf('edtTest finished.\n');
 
% Callback for button1
function button1Callback(~, ~, button2)
    for k = 1 : 10
        svd(rand(1000, 1000));
    end
    button2.doClick();
    fprintf('Button 1 callback finished\n');
 
% Callback for button2
function button2Callback(~, ~)
    for k = 1 : 10
        svd(rand(1000, 1000));
    end
    fprintf('Button 2 callback finished\n');

V = sscanf(version, '%d.', 2);
if V(1) >=7 && V(2) >=6, ...

This is a fast Mex, which can consider all 4 version numbers from VERSION: http://www.mathworks.com/matlabcentral/fileexchange/27231-ismatlabver

Kind regards, Jan