🚀 go-pugleaf

Steve,

There are, I'm afraid, inconsistencies in the object model that can drive you nuts. I do not like the behavior we're discussing here. Knowing whether or not your script has to check for this error when dealing with an allegedly read/write object is not a good thing -- after all, it's the kind of thing that can be missed oh so easily during testing only to have it happen the first time your customer/client/user tries to run the script.

But for now we have to live with it. The best we can do collectively is help each other discover these idiosyncrasies, while expressing our displeasure to Adobe here: <http://www.adobe.com/support/feature.html> or here: <http://www.adobe.com/misc/bugreport.html> depending on how strongly we feel about it.

Dave