Ah no, i mostly just use one in front and behind my current frame.
That drag-clicking was just as a cpu endurence test on an empty/full project.
Just clicking one button on and an other off has the delay also , for example :
My lighttable is on 4 frames ahead and one 1 front.
I move two frames ahead and i want to change button 4 to 2 (ahead)
in order to have the same image underneath my current frame.
When i do this, namely disable 4 and enable 2 the delay on the buttons sometimes causes the button 3 enabled together with 4 while passing over it (and i'm not dragging, just a fast click and a move). Which is a bit annoying.
However if i click it and wait till it toggles (able/enable) then go the other button and then click that button, wait till it toggles (able/enable) it works fine. The waiting is onle about a third of a second. It is not a biggie as i said, it just teaches me patience, which is a good thing if you look at it in a zen way.
I hope this is understandable. Anyway, it seems to be just a hardware thing and i can live with it. (doesn't hurt a bit )
Thank you for all your time. Gracias.
I'll surely bother you some more at a later time...