Jon:
I just got R3 and none of these canvas issues were fixed. Everything
I described behaves the same as R1.
I have compositing on for the Main window, otherwise images in the
main window canvases disappear when calling a sheet dialog over the
window.
I tried implementing code in the Paint event to no success.
Yours truly
R Charles Flickinger
Corona: www.designersdomain.com/corona
Daktari: www.designersdomain.com/daktari
With 2006, if compositing is off, the opposite occurs, where
canvases do refresh when drag-dropping a file to the canvas a
Finder window (Finder in foreground), but when re-activating the
window, the images appear in the canvases. Essentially, you don't
know whether the drop was successful until you activate the window
back to the foreground. When I turn the window compositing on,
there is no difference, the same behavior occurs where the images
are not visible from the drop until the window (app) is once again
foreground. If the window is foreground (the drag-drop is from a
Finder window when Finder is in background) the images are appear
as expected. This is great, but we know that images are often
dropped onto windows when Finder is foreground. Note: this
behavior occurs with built 2006 apps, it does not occur when debug
run.
But when running this in 2006, the compositing prevents dropped
images from appearing (redrawing) in the canvases until the window is
reactivated.
Does Canvas.Refresh not work? I haven't seen that fail either.
In 2006, when I add me.refresh to the canvas' dropobject event,
whether compositing is on or off, the 5.5 behavior occurs as if
compositing is off. BTW, this behavior does not occur in debug
run, where everything works fine, better when compositing is on.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
