Re: Mail: mailboxes in folders
Re: Mail: mailboxes in folders
- Subject: Re: Mail: mailboxes in folders
- From: "David P. Baker" <email@hidden>
- Date: Sun, 6 Apr 2003 19:40:54 -0400
Comments below.
On Sunday, April 6, 2003, at 06:23 PM, cricket wrote:
On Sunday, April 6, 2003, at 7:41 AM, David P. Baker wrote:
OK, I have a set of mailboxes in my IMAP account, some of which are
inside folders. That means their name is "Folder/Mailbox", or, for
example:
get mailbox "Archive/Job" of account 1
Fine and dandy. However, there is no property of that mailbox that
specifies the containing folder, as far as I can tell. So if I get the
name of the mailbox, I get just "Job" -- which will be wrong if I try
to get it by name if I have another mailbox named "Job":
We've added a 'parent' property of the mailbox class since 10.2.x, so
this should hopefully make it into the next major release.
Excellent. This release would be happening when? And where can I make
suggestions for future releases? (I have several.)
set box to mailbox "Archive/Job" of account 1
-- mailbox "Archive/Job" of account "email@hidden"
set box_name to the name of box
-- "Job"
set new_box to mailbox named box of account 1
-- mailbox "Job" of account "email@hidden"
We've fixed this internally.
OK, I guess I'll find out.
which is not the mailbox I wanted! I need some way of specifying the
correct mailbox other than a reference. (I'm storing the mailbox spec
in a data file.) Shouldn't there be a "path" property or something
that
I could use that would give "Archive/Job"? Or at least an opaque id
field that I could store as a string (there isn't one).
A unique id is what we were thinking of doing, but path isn't such a
bad idea as well. Personally, I dislike that asking for mailbox
"Archive/Job" actually works, given that the UI doesn't really have a
mailbox named "Archive/Job". This is a legacy of our mailbox creation
UI, which used to rely on slashes to created subfolders. Ick.
Whatever works. I don't really care. Although given that (in the case
of IMAP folders) these are objects that are really external to
Mail.app, you should probably provide a transparent identifier (in
addition to an opaque one, perhaps).
Have you considered using properties instead of external datafile?
I have, but that's a problem if more than one script needs to use the
property. Even if I use "load script", the client gets its own local
copy of the script object, so other clients can't share the property.
If you can tell me a better way, then do so!
I don't have any good suggestions for you to work around this.
Well, what about some bad ones?
- cricket
----->
Software Entomologist Mail for Mac OS X
http://www.apple.com/macosx/jaguar/mail.html
---------->
I'll never wash my lips again!
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.