On Mar 17, 2007, at 5:32 PM, Info - PeterTools wrote:
Hi Mike,
Hello everybody,
although I've been a reader for long time, this is my first post
here on the Apple Lists.
First of all please send plain text e-mails, not HTML. As you can see
in the text the HTML (quoted below) does not make it through the list
server (at least not for digest readers like me) and the resulting
text is very hard to read. Messages that are hard to read cost more
time to read. And the likelyhood of someone helping you will get
lower the more time it takes to even understand your question.
For what it's worth, plain text messages do offer some advantages
over HTML/Rich Text messages:
- They never get mangled when I hit the reply button, such as having
blank lines inserted as above.
- They are much smaller. According to Mail, your original message was
12.7K. When I sent it to myself as plain text for a test it was 3.4K.
On disk, where Mail stores every message as a separate file, it was
16K vs. 4K. For those people with tens of thousands of saved messages
because they can't bear to delete anything that isn't spam, that adds
up.
- People can read them in the preferred font and size they've set in
their e-mail clients. Sometimes people post messages that show up in
some tiny little size I can barely read.
So unless there's a real need for styling information in an e-mail,
it's better to use plain text when posting messages.
(which will be loaded by another application, not programmed by
me).
I've setup a lightweight communication protocol between the two
using
Apple Events. they are so easy to use and things went
straightforward
even if this is the first time I use them.
The application and the plugin can be loaded and unloaded
separately so
both of them
An application is not loaded or unloaded. It is launched and quit.
Plugins might be loaded or unloaded. So your description is only half
correct.
Come on Mike, I think everybody understood what I meant!
I wasn't quite sure. ;-) Are you saying your application is launched
by another application, the one you didn't write? When you're talking
about a system involving two applications and a plug-in it's best to
be as accurate as possible in your description.
Also, what kind of plug-in is this? Which applications might load it?
(Just curious here.)
can sometime be sending apple events to a non-existing target.
When I
reproduce this scenario AESendMessage returns -600 (procNotFound) as
expected, my question is.
Obviously you can't send to a non-existing target. The AppleEvent
Manager is telling you so with its error code.
How are you addressing your non-existant target?
Both direction of my communication define targets using
typeApplSignature.
For what it's worth, building and sending AppleEvents to a
nonexistent target is a waste of resources. If you're sending a lot
of them, or in normal use the target won't be around, then I'd look
into a way to avoid sending it AppleEvents when it isn't there.
Sending dozen of messages to a non-existing target and being
returned
procNotFound will cause memory leakage, somehow slowdown the session
or cause an app crash?
When your application receives an AppleEvent, your application
doesn't release any memory allocated for the AppleEvent, the
AppleEvent Manager releases it. As I understand it the AppleEvent
Manager releases the memory used by an AppleEvent whether the target
exists or not once you've sent it.
I'm not seeing any memory leak by the Apple Event Manager, but I
wanted
to know if doing this is a suggested-practice or a completely
deprecated!
I'm not sure to what "this" refers. Sending AppleEvents or sending
them to nonexistent targets?
Larry
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
