I'm always open to improve the API docs but where should I mention it? PDBorderStyleDictionary.setBorder() has this:

    /**
     * This will set the border width in points, 0 = no border.
     *
     * There is a bug in Adobe Reader DC, float values are ignored for text field widgets. As a      * workaround, floats that are integers (e.g. 2.0) are written as integer in the PDF.
     *
     * @param w float the width in points
     */

Should I add: "In Adobe Acrobat DC, the values are shown as "0 = Invisible, 1 = Thin, 2 = Medium, 3 = Thick" ?

Does Adobe Acrobat DC show these for all annotations or only for link annotations?

Tilman


Am 14.11.2017 um 20:20 schrieb Gilad Denneboom:
It's under link.getBorderStyle().getWidth() ...

On Tue, Nov 14, 2017 at 8:16 PM, Tilman Hausherr <[email protected]>
wrote:

I know only getBorder() and getBorderStyle().

What "Border Width" item do you mean?

Tilman


Am 14.11.2017 um 13:35 schrieb Gilad Denneboom:

Hi all,

Just wanted to report something I stumbled upon today that was causing me
a
lot of confusion and headaches when working with Link objects.
I was trying to find the equivalent to the "link type" property that
Acrobat uses (ie, Visible Rectangle or Invisible Rectangle).
Looking at the PDAnnotationLink object I saw two very similar-sounding
methods, isInvisible and isHidden (both inherited from PDAnntation), but
it
turns out that neither of them corresponds with this property.
So I did some further research into the border cos object and found that
the actual property used by Acrobat is the Border Width (0 = Invisible, 1
=
Thin, 2 = Medium, 3 = Thick).
Might be a good idea to add this information somewhere in the API
Reference...

Gilad


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]




---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to