Continued:
Because I'm using sheet window dialogs, the main window must be
composited.
What makes you think this is the case? I've used sheets with
non-composite windows a lot. But...
Thanks for asking. To not mislead, needs to clarify.
In 5.5, if compositing is off, the canvases actually do refresh when
drag-dropping a file to the canvas from a Finder window (Finder in
foreground), , but when re-activating the window, the the images
disappear from the canvases. The image references are present, but
the image is immediately wiped out each time they're drawn. Perhaps
I need to add code to the canvas paint event? However, when I turn
the window compositing on, the dropped images retain and are visible
when activating the window to the foreground from Finder, the never
disappear. So, with compositing on, I don't need a paint event.
This behavior occurs whether in debug run or built.
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.
Have you reported a bug with a project to demonstrate the issue?
I appreciate you asking, and I've used the feedback system before.
At one time I thought I saw bug reports describing nonperformance
with canvases..
Just make a newproject, add a JPEG file type, throw a canvas on the
window, set the acceptfiledrop in the open event to accept JPEGs,
handle the dropobject event with:
me.Backdrop = obj.FolderItem.OpenAsPicture. Works fine in debug run,
built app doesn't, whether compositing is on or off.
Yours truly
R Charles Flickinger
Corona: www.designersdomain.com/corona
Daktari: www.designersdomain.com/daktari
_______________________________________________
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>
