You've made my day.
Fascinating note on how users build a mental model of the software
they're using: when I first started using PM several years ago, I tested
to see if this worked: by deleting an email (moving it to mail trash).
Since this had no affect on the enclosure, I assumed that PM wasn't able
to handle it, and have been managing that by selecting enclosures,
deleting them, tabbing to the body of the email, and deleting it. For years.
The interesting thing is to note how the user develops a User Model of
the software. It's easy for us, as developers, to think "Ach! Those users
are just not savvy [smart?] enough to see how to use the software!" But
here I am, a developer myself (and, I think, a reasonably intelligent
man), and the monkey part of my brain hadn't gone past trying one thing
to get it to work, and I hadn't even thought to try something else.
Thanks, Jerome!
On 4/16/05 at 10:05 AM, PowerMail Engineering ([EMAIL PROTECTED]) said:
>Steve Abrahamson wrote:
>
>>One thing that's always struck me as double work is that when I delete an
>>email with enclosures, I have to delete the enclosures first, then delete
>>the mail.
>
>PowerMail moves the attachments to the Finder trash when a message is
>deleted (ie, when the trash is emptied, or when old messages are deleted
>from the trash on quit). However, only attachments that are still in the
>attachment folder are moved to the trash; if you have moved them outside
>of the attachment folder, PowerMail will leave them untouched.
Steve Abrahamson
Ascending Technologies
FileMaker 7 Certified Developer
http://www.asctech.com
[EMAIL PROTECTED]
