The Drag and Drop Component Suite v5.0 released

7 votes, average: 3.71 out of 5

Loading ...

Author: Anders Melander

Filed under: DragDrop, Delphi

7 Dec 2009

I’m pleased to finally announce the release of version 5 of the Drag and Drop Component Suite.

The core changes in this version includes:

Full Unicode support.
Supports Delphi 2009 and Delphi 2010.
6 new example applications.
The DragDetectPlus function now behaves nicely on controls that use popup menus.
Improved support for drag/drop to and from Outlook.

RSS feed for comments on this post

12 comments »

Michael December 7th, 2009 at 05:26 1 +1

YAY!
Very well done, sir!

Reply to this comment

mouser December 7th, 2009 at 05:52 2 +1

Fantastic — thank you so much for sharing this with all of us.
-mouser

Reply to this comment

joe December 7th, 2009 at 06:57 3 +1

thank you! very good component!

Reply to this comment

Radek December 7th, 2009 at 09:58 4 +0

Nice, but why is TDropFileTarget.Files declared as TUnicodeStrings instead of TFileStrings from same unit? This is problem for nonunicode delphi.

Reply to this comment
1. Anders Melander December 7th, 2009 at 14:24 5 +1
  The Files properties are declared as TUnicodeStrings in order to support Unicode file names on all versions of Delphi.
  
  This should not be a problem for older versions of Delphi (i.e. pre-D2009) as they will implicitly convert the Unicode strings to Ansi as needed.
  
  E.g. this works just fine:
  var Filename: string; begin Filename := DropFileTarget1.Files[0]; ShowMessage(Filename); end;
  Reply to this comment

Erich Wanker December 7th, 2009 at 16:23 6 +0

Thank you. This is realy a great component.

I have a little question: If i drag&drop a mail with attachment and "save it", i get an error in the "Outlook drop target demo" : Project OutlookDemo.exe raised exception class EOleSysError with message "access denied ". process stopped….

Mails with no attachments are working fine.

Office Outlook 2003(11.8217.8221) SP3
Borland Delphi Enterprise Version 7.0
Windows XP SP3

Thanx for your great work.

best regards

Erich

Reply to this comment
1. Anders Melander December 7th, 2009 at 17:13 7 +0
  
  I have reproduced the problem and am investigating the cause.
  
  Thanks for the feedback.
  
  Reply to this comment
2. Anders Melander December 7th, 2009 at 18:49 8 +1
  
  I have found a solution to this problem.
  
  Instead of trying to construct a MSG file from the IMessage interface, which apparently is a really complex and fragile task even though it should be simple, I now keep a reference to the original IStorage interface and save that instead.
  
  I will release the updated demo once I have tidied up the modified source, but I'm out of time for today.
  
  Reply to this comment

Simon December 9th, 2009 at 17:35 9 +0

Thanks Anders. I find this one of the most valuable component suites for Delphi. Really happy to see it's still begin maintained

Reply to this comment

izia February 24th, 2010 at 09:34 10 +0

Hi!
I tried your demos virtualfilestream and virtualfile with outlook attachment but it only works with .txt files. I tried it with pdf and the program catch the name of the file but not all of the content.
If a drag the file from your program to the desktop, the program creates the file but I can't open it. It gives me an error, and say that can't repair the file.
¿Do you know what the problem is?

Reply to this comment
1. Anders Melander February 24th, 2010 at 15:45 11 +0
  The VirtualFile demo, by design, limits the amount of data to 32K. This is documented in the source:
  // Limit the amount of data to 32Kb. If someone drops a huge amount on data on // us (e.g. the AsyncTransferSource demo which transfers 10Mb of data) we need // to limit how much data we try to stuff into the poor memo field. Otherwise // we could wait for hours before transfer was finished. MemoContents.Lines.Text := Copy(FTargetDataFormat.Contents, 1, 1024*32);
  The VirtualFileStream demo, again by design, limits the amount of data it saves to 1K. This isn't explicitly documented in the source, but the source comments does hint that for a real application you will need to implement your own storage of the data:
  // In a real-world application we would write the buffer to disk // now. E.g.: // FileStream.WriteBuffer(p^, BufferSize-Chunk);
  If you set a break-point in the OnDrop event handlers it should be pretty clear what is going on with the data.
  
  I will try to work a little on the VirtualFileStream example to make it more obvious what one has to do.
  Reply to this comment

izia February 25th, 2010 at 12:05 12 +0

Thank you! Finally I can save the entire drop file saving the FTargetDataFormat.Contents directly, and I commented ClearData ..etc.

Reply to this comment

Entries (RSS)
Comments (RSS)

Dont bother...

...writing comments. I don't have time or motivation to moderate comments or answer questions and my wordpress is so broken that I can't even turn the comment option off. If you need help, please try stackoverflow. Sorry.

MelanderBlog

The Drag and Drop Component Suite v5.0 released

12 comments »

Leave a comment

Results

Recent Posts

Recent Comments

Dont bother...

Meta