Stéphane, thank you very much for your example!
However, everyone of my callback functions is short-lived: it just does
a few things and exits. Sometimes the response is instantaneous but
sometimes it takes a long time. I have not so far managed to notice any
pattern in that.
Stefan
On
Depending on what you want to do, some have to be interruptible, and
some have to prioritary. For example in the following example, where you
can start/stop incrementing a slider, the "start" callback must be
interruptible but the "stop" callback must be prioritary :
function stop()
Hi, thanks.
Yes, but it doesn't seem to make much difference. And I don't exactly
understand the different options.
Stefan
On 2022-09-20 12:03, Stéphane Mottelet wrote:
Hi,
Did you try to play wth callback_type (interruptible or not) ?
Le 20/09/2022 à 10:48, Stefan Du Rietz a écrit :
Hi,
Did you try to play wth callback_type (interruptible or not) ?
Le 20/09/2022 à 10:48, Stefan Du Rietz a écrit :
Hello Stéphane,
a minimal example works OK all the time ...
So, there must be something in my rather complex GUI environment, with
many private functions, that does not. But
Hello Stéphane,
a minimal example works OK all the time ...
So, there must be something in my rather complex GUI environment, with
many private functions, that does not. But since I get no warning or
error messages, I don't know how to proceed.
Can the delays be due to timeouts?
Regards
Hello Stefan,
Can you give a minimal and reproductible example ?
S.
Le 18/09/2022 à 12:18, Stefan Du Rietz a écrit :
Hello,
I have a problem with GUI: when I choose a menu or press a button,
sometimes it takes half a minute before the callback starts. Scilab is
then using 100% of CPU,
Hello,
I have a problem with GUI: when I choose a menu or press a button,
sometimes it takes half a minute before the callback starts. Scilab is
then using 100% of CPU, according to Bash top. I suppose it has
something to do with Java? What can I do?
--> ver
ans =
"Scilab Version: "
