Thanks for the recommendation. This is a funny bug. Actually, if I
just accept JPEG files, it works fine:
me.AcceptFileDrop "JPEG Image"
Or if I just accept PNG files (with PNG appropriately defined too):
me.AcceptFileDrop "PNG Image"
Works fine. But let's say I accept PNG and JPEG files:
me.AcceptFileDrop "JPEG Image"
me.AcceptFileDrop "PNG Image"
Now it won't accept either. And if I do it as you suggest:
me.AcceptFileDrop FileTypes.JPEGImage
me.AcceptFileDrop FileTypes.PNGImage
It also won't accept drops of either file type. Looking more and more
like a Windows build bug, and unfortunately, one that will send me
back to R1 :(. I'll follow-up with a bug ID later this morning.
-Brad
--
Brad Hutchings
e-mail: [EMAIL PROTECTED]
On Apr 17, 2006, at 8:26 AM, Joseph J. Strout wrote:
What you're doing is correct, and its failure should be reported as
a bug. However, it's not what I would recommend, unless you're
taking your project back and forth to 5.5 or earlier. Instead,
just name the file type object:
me.AcceptFileDrop FileTypes.JPEGImage
I doubt this will fix the problem, since a FileType object converts
itself to a string as the display name, which makes the above code
equivalent to what you wrote (unless you made a typo not evident in
your email). But I recommend it anyway, since it avoids the
possibility of such typos.
HTH,
- Joe
_______________________________________________
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>
