thread 2 (in charge of mouse events) is going slower, which is an issue for the set_active functions. it will prompt the new active window after having printed the window + the box, voiding the effect of the click
suggested: mutex for an access_writing variable + condition if it is on TRUE.
thread 2 (in charge of mouse events) is going slower, which is an issue for the set_active functions. it will prompt the new active window after having printed the window + the box, voiding the effect of the click
suggested: mutex for an
access_writing
variable + condition if it is onTRUE
.