The method call page.AddAnnotEditbox always return false in my case. Also the editbox is not displayed on the screen, which is probably the logical result of this return value.
Java doc states "the added annotation can be obtained by Page.GetAnnot(Page.GetAnnotCount() - 1), if this method return true.". This is what I am doing here.
Is there any restriction in this using page.AddAnnotEditbox without license key? I am just evaluating if these functions work properly in order to buy the premium version.
Can someone please point me in the right direction? I am pretty stuck here.
thank you very much for your quick reply.
After some hours of work I found out that it was a license problem. I didn`t set the package name to com.radaee.reader.
Why is that information hidden in the knowledge base? Why isn`t there any "How to get started" page on your web site?
This is really a bad way of documentation. I just found that by chance.
After doing that, page.AddAnnotEditbox works fine.
But now I have the same problem with page.AddAnnotBitmap. My code works fine in the demo project. But when I cut and paste the same function in my project page.AddAnnotBitmap always returns false. Package name is set to com.radaee.reader.
thank you very much for pointing me in the right direction: m_doc.SetCache did the job.
I didn't know that setting the cache is mandatory for adding images.
Is this true only for images? page.AddAnnotEditbox worked fine without cache. Why is that so?
Seriously: you need better documentation. The important pieces of information are cluttered all over your website. Why don't you put together a "get started page" wich contains the complete information which is needed to get started with your library?
You could probably sell more licenses when your documentation would be better. It was really a pain and took me 4 work days to understand how to use your library properly. This could optimised severely ....
Thank you Max for your suggestions.
We're aware about our actual weakness (documentation, well done xamarin integration, good ready to be integrated PDF reader) as our tool started as a all purpose PDF rendering and manipulating API and was addressed, particularly, to skilled developers.
Right now the border between "skilled developers" and "developers who needs quickly to go on the market" is really thin.
About our actual activities:
- we're improving iOS xamarin and ready to be run reader. It's an internal release but we share it with customers who are looking for it
- improving Android performances and clean the code, mostly optimizing speed/memory consumption rate
After that we will start:
- Android official xamarin interface and ready to be included reader
- improving documentation
It's quite a long process and we are approaching it trying not to alter our price list: providing free support and perpetual update require us a big effort.
Thank you for your further information. I bought the premium license for our customer yesterday. This is now the fourth project where we use your library.
I would really appreciate if you could beef up your documentation. It would help a lot if your java classes you ship with your viewlib would be more structured and readable. More comments would be nice there also.