[Octave-bug-tracker] [bug #52804] "Interruptible" and "BusyAction" properties

[Pantxo Diribarne]

Follow-up Comment #8, bug #52804 (project octave):

Here is a much better test (the cb.m function is attached) that I could check
in ML:


clf
set (gca, 'buttondownfcn', @cb, 'interruptible', 'on')
hui = uicontrol ('style', 'pushbutton', 'callback', 'disp (''button'')',
'busyaction', 'queue')


First click inside the axes to trigger the execution of the lengthy axes
callback. Then click multiple times on the button to see what happens.
Here is what I observe in Octave 
* whatever the value of "interruptible" and "busyaction", the uicontrol
callbacks are always executed after the axes buttondownfcn has returned. 
* the messages only appear onscreen once all the callbacks have been
executed.
* clicking the button while the axes callback is executing doesn't visually
look like the button reacts, even though the click is actually taken into
account


In Matlab:
* interruptible->on, busyaction->queue: uicontrol callbacks are executed each
time drawnow is called (if you have clicked 3 times the button in  5 seconds
then you see 3 "button" between 2 "processing queued callbacks")
* interruptible->off, busyaction->queue: uicontrol callbacks are all executed
after the axes callback as returned (drawnow has no effect)
* interruptible->off, busyaction->cancel: uicontrol callbacks are not
executed


(file #42953)
    _______________________________________________________

Additional Item Attachment:

File name: cb.m                           Size:0 KB


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?52804>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/