> > Note that the API function needs to be defined ahead of time: > > > > DECLARE INTEGER LockWindowUpdate IN user32 INTEGER hWndLock
> Cool! What's your preference of where you'd declare that? I declared it in load event of the one form I had to implement this in, as init wasn't soon enough. It might be best to declare it up front in a very early environment setup routine as long as you don't have CLEAR DLLS commands in your app anywhere... Note that there is a slight performance hit with this method-- in my situation it cost about 100-200ms in this function. From what I could tell, it was because this was forcing the re-draw to occur and wait for it instead of continuing on with code and drawing once VFP had the chance(processing the message queue)... In our situation, flashing icons whenever we clicked a 'button'(not a real command button-- just a container that acts like a fancy button) was not acceptable. -- Derek _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
