SetSize
(1)
IStream
(1)
TeamB
(1)
FILEDESCRIPTOR
(1)
DWORD
(1)
Years
(1)
Pigs
(1)
COM
(1)

drag/drop files > 4G

Asked By David F.
01-Nov-09 11:43 AM
My existing drag / drop interface uses the various COM interfaces but they
use DWORD values for file positioning.  What interface should I be using to
support files > 4G and what platforms does that interface work on?

Thanks.

David F. wrote:theyusing toI am not sure I understand.

Igor Tandetnik replied to David F.
01-Nov-09 11:15 PM
they
using to

I am not sure I understand. Which part of drag/drop deals with file sizes =
but cannot represent sizes greater than 4G? The only place I could think =
of off the top of my head where file size is mentioned is in =
FILEDESCRIPTOR structure, but it does use two DWORDs to represent size.
--=20
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not =
necessarily a good idea. It is hard to be sure where they are going to =
land, and it could be dangerous sitting under them as they fly overhead. =
-- RFC 1925

Agreed.

Remy Lebeau replied to Igor Tandetnik
02-Nov-09 06:14 PM
Agreed.  Also, when passing data around using IStream, its SetSize() and
Stat() methods also support 64-bit sizes as well.

--
Remy Lebeau (TeamB)

David F. wrote:I am not sure I understand.

David F. replied to Igor Tandetnik
03-Nov-09 03:42 AM
I am not sure I understand. Which part of drag/drop deals with file sizes but
cannot represent sizes greater than 4G? The only place I could think of off
the top of my head where file size is mentioned is in FILEDESCRIPTOR
structure, but it does use two DWORDs to represent size.
--

I do not know - I was just going from memory from 9 years ago, now I look at
what was there about 4G is commented out and using 64bit values.  So perhaps
it was limited to some platform or using some other interface.  Sorry about
that.
Post Question To EggHeadCafe