@TIG:
Thank you for your response !
Well, I just arrive in the company, I will be there for only three months so I have no pretension to represent anyone but me ^^
I use, for personal projects, only open-source work and collaborative forum like yours. This is why I preferred to go here in a first time.
Actually, I was a little bit surprised by your first part of your response BUT (;)) I understand it completely !
To return to the main point of the subject, I have read the API of course and I know what you wrote. However, I wish you explain more your sentence :
@unknownuser said:
Timers do work 'asynchronously', BUT of course block up your threads if they are 'incomplete' or still 'running'.
Moreover, I test a little thing :
UI.start_timer(0, false) {
Thread.new {
$i=0
while true
$i+=1
end
}
}
and you can see in Ruby Console that $i continues to change although the main code has finished.
Maybe you are right : I should ask to a Boulder guy because he has an access to the source code.
Thanks again, have a nice day !