🚀 go-pugleaf

>I think most developers would define a bug as something which exhibits unexpected behaviour. 

Unexpected by who? If a user has the wrong idea of what a product
does, is that a bug?

>As I mentioned in my last post, the OCX is distributed with Acrobat, as well as the Reader. That would certainly make it available as a programming tool. 

That doesn't make it supported. Why would Adobe write about 10,000
pages of documentation for Acrobat developers if they expected you to
use something else?

>If the control was not meant to be used, the code could have been more easily  distributed as a dll and used as an COM add-in. 

But it wasn't. Doesn't change the situation.
>
> If there is another usable method, please point the poster (and myself, for that matter) to it. 

Have you even looked at the Acrobat SDK? If you develop by guesswork,
you will get unreliable solutions.

>If not, I expect that we need to hear from Adobe that it won't be fixed, or that they are working on the problem. 

It would be useful if they did, but since this is a User to User
forum, don't hold your breath.

Aandi Inston