Raise Number:=vb Object Error ERR_WINDOW_LOCK_FAIL, _ Description:="Unable to set a Power Point window lock" Exit Property End If Else ' Unlock the Window to refresh Lock Window Update (0&) Update Window (hwnd) hwnd = 0 End If End Property 'Sample Usage: Sub Long Processing Sub() ' Lock screen redraw Screen Updating=False ' --- Long time consuming code ' Redraw screen again Screen Updating=True ' Also see below article for another example of usage of the code End Sub It's fairly simple to open a Power Point file (*.ppt) for editing using VBA code however opening a Power Point Show (*.pps) file for editing is altogether another matter. Open method and it defaults to open the file in Slide Show mode. The routine below illustrates a manner of woring around the default behaviour and opening the file for editing.
I'm running a macro that has to open and run code from a module, then open a table after it's done.
The problem is that the user can see the code module a few seconds before the table is opened.
To get the framerate smooth, i have tried several options, with poor results: Agree with Skip. I am not sure if VBA can do similar API manipulation of DCs as VB itself.
It certainly would be faster to use a Create Compatible DC function (Lib "gdi32") and do your manipulation there, in memory, and then dump it back to the screen in toto. Gerry Well, I've made some improvement with this combination: Lock Window Update (Find Window("XLMAIN", vb Null String)) Call Send Message(Find Window("XLMAIN", vb Null String), _ WM_SETREDRAW, 0&, By Val 0&) Update Objects Call Send Message(Find Window("XLMAIN", vb Null String), _ WM_SETREDRAW, 1&, By Val 0&) Lock Window Update 0However, as you said, using more than say 40 visible objects at once, really slows the framerate. btw: The Bitmap Viewer as well as the Ascii converter only swallow 24-bit Bitmaps.
I want to be able to do the whole process without that "flickering".