Hello Martin, On Thursday, May 12, 2005 at 10:53:57 PM Martin [MS] wrote:
>>> So it's time to write a bug report - I think. Will do it tomorrow. >> Whether one may like, or not, the way TB handles attached files when >> saved with the message and the way of opening them (i.e. writing attachment >> to >> a temp file and then opening it), it is _not_ a bug. It is WAD (Working >> As Designed). MS> How do you know? In my opinion it *is* a bug - an email client has MS> *never* to change a name of an attached file. Whether you like the current behaviour (with attachments stored in message base) or not: The Bat! does *not* change the attachments file name. If you open the file from inside The Bat! (and have attachments not stored in a separate directory), a temporary copy is create. This copies name is created in a fashion that makes sure the temporary file is *unique*, i.e. no other file with the same name exists. So even if you open an attached file twice it'll get a different name for the temporary file each time. That's intentionally and by design. If you want to play with the original, *the* attachment: save it from within The Bat!; there will be no change in the files name. That way you can open *the attachment*; the other way you can open an "anonymous copy" of the attachment. I'd *not* be amused if The Bat! would refrain from creating "unique named copies" in %TEMP%, simply because: Imagine you get two mails. Both have an attachment named "contract.doc"; Both mails from different companies. Now you open attachment of first mail, The Bat! keeps the name, the file is still open and you decide to open the second one as well (you want to compare the offers one-by-one). The Bat! would - either try to overwrite your first opened document, which will fails, as Word has a write lock on it (other word processing programs might do the same). - create a different file, with a derived name, e.g. 'contract-1.doc': The Bat! would changed the files name nevertheless, you won nothing compared to the current situation. The latter is what's done when you store attachments in a separate directory and for me this is one reason *not* to store attachments outside the message base file. I simply don't like The Bat! playing with my files names ;-) On the other hand the "create a arbitrary named temporary file that for sure does not collide in its name with an existing file name" is a philosophy run by *many* applications, even MUAs, on *nix systems. And it's a well-tried behaviour for a lot of years now ;-) So all in all it seems you really have to file a *feature request*, as Miguel already wrote, because The Bat! does nothing it shouldn't, but instead not only works as intended by design, but also as intended by a fundamental idea ;-� I know this doesn't help, but maybe it shows: TIMTOWTDI[1] -- Regards Peter Palmreuther (The Bat! v3.5 Return RC9 on Windows XP 5.1 Build 2600 Service Pack 2) Which caused little rhythmic darts of red to pulsate gently in the morning sun. [1] http://www.acronymfinder.com/af-query.asp?Acronym=TIMTOWTDI ________________________________________________________ Current beta is 3.5 Return RC/9 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
