Page 2 of 2

Posted: Mon May 08, 2006 1:42 pm
by Dare2
LOL. :lol:

Must have been very hard to write. :D

Posted: Mon May 08, 2006 1:46 pm
by traumatic
:oops: :lol:

Posted: Mon May 08, 2006 2:01 pm
by netmaestro
Robbing from my code from last year, the Image.pb code can be perfected in the main loop thus:

Code: Select all

If EventID 
  If GetActiveWindow()<>WindowID(0)
     ;redraw
  EndIf  
EndIf
That covers the eventuality that the window gets covered up and a repaint is not triggered. Only 1 or 2 events get fired after it goes inactive, so it isn't sitting back there redrawing endlessly.

BTW, if a callback is not getting the #WM_REPAINT message, that is no fault of PB's, so a bug report wouldn't likely produce any fix. imho anyway. [edit] - too late.

Posted: Mon May 08, 2006 2:53 pm
by Dare2
Okay, it makes sense to idle down the window if it thinks it is totally covered.

netmaestro wrote:BTW, if a callback is not getting the #WM_REPAINT message, that is no fault of PB's, so a bug report wouldn't likely produce any fix. imho anyway. [edit] - too late.
Depends - does PureBasic core get the info first and then call the callback? Or does windows call the callback and then pass the messages on to Pure? Either way, a message goes awol. The fact that it turns up in the main event loop is interesting. I am sure it means something deeply significant to someone but it just gives me a headache as I try to follow it through. :)