Yes, I realize that. My post wasn't a question but more a comment
for those who may be using Zipforge and relying on the settings they have
provided, which would make one believe they had added something to provide a
warning. I was in contact with them yesterday regarding this and they'll be
looking into some documentation on this.
I've gotten to the point where I no longer rely at all upon any of
the docs or settings provided with 3rd party components alluding to various
properties and/or events. I've been caught too many times with things like
this and now run tests on even the most minute services to ensure they
behave as stated.
from Robert Meek dba Tangentals Design CCopyright 2006
"When I examine myself and my methods of thought, I come to the conclusion
that the gift of Fantasy has meant more to me then my talent for absorbing
positive knowledge!"
Albert Einstein
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Cosmin Prund
Sent: Tuesday, April 04, 2006 1:35 AM
To: 'Borland's Delphi Discussion List'
Subject: RE: Tfilestream class
TFileStream is a worker, very low level class. It is not supposed to do any
kind of GUI work and you're not supposed to rely on it for a "message box".
The world would be a pretty confusing place if any low-level class would be
allowed to pop it's own message box etc. Just imagine TStringList showing
boxes on it's own.
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Robert Meek
> Sent: Monday, April 03, 2006 10:21 PM
> To: [email protected]
> Subject: Tfilestream class
>
> I was writing archiving code using ZipForge components and wanted to
> offer the user the ability to accept an over-write of the current archive
> made on the same day thus having the same name, or deleting the first and
> making a new Archive altogether. Now when a normal file copy is made, or
> a
> new file created with the same name Windows offers an over-write prompt
> warning you of the situation, but the TFileStream Class does not.
> Zipforge
> I found out depends on this class to handle the writing of the archive to
> disk, and has a number of its own parameters which work with those of the
> FileStream. I assumed, and I think the authors did also, that if using
> the
> fmCreate parameter, and there was already a file of the same name in the
> target directory that Windows would give an over-write warning. Leaving
> the
> parameter blank or setting it to fmOverwrite would not...it would simply
> overwrite the file. But it seems there's no way to get an overwrite
> warning
> when using this class. You need to write it yourself.
>
>
> from Robert Meek dba Tangentals Design CCopyright 2006
>
> "When I examine myself and my methods of thought, I come to the conclusion
> that the gift of Fantasy has meant more to me then my talent for absorbing
> positive knowledge!"
> Albert Einstein
>
>
>
> _______________________________________________
> Delphi mailing list -> [email protected]
> http://www.elists.org/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi
_______________________________________________
Delphi mailing list -> [email protected]
http://www.elists.org/mailman/listinfo/delphi
