[
https://issues.apache.org/jira/browse/PDFBOX-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14663306#comment-14663306
]
John Hewson edited comment on PDFBOX-2918 at 8/9/15 7:40 AM:
-------------------------------------------------------------
{quote}
Although that could be done with the setters it might be better to have an
extra method
{quote}
The downside with that is that we'd be dependent on that method for updating
styles... i.e. if the user fails to call the method, then the appearance will
_never_ be generated. That's going to catch a lot of people out.
{quote}
doing multiple settings would require to constructAppearances() every time.
Simply replacing e.g. the border definition wouldn't work as the padding of the
text is dependent on the border width.
{quote}
Is there any reason why we can't construct appearances each time? It's by far
the most robust and reliable approach.
{quote}
Constructing the appearance when it's next fetched would only work AFAIK if
after the changes the form will not be saved immediately. Or we delay
constructing appearances just before saving the document.
{quote}
I was thinking that we could delay constructing the appearance until the
appearance stream is next accessed, but it's going to get quite complex that
way. Probably best avoided.
was (Author: jahewson):
{quote}
Although that could be done with the setters it might be better to have an
extra method
{quote}
The downside with that is that we'd be dependent on that method for updating
styles... i.e. if the user fails to call the method, then the appearance will
_never_ be generated. That's going to catch a lot of people out.
{quote}
Although that could be done with the setters it might be better to have an
extra method as doing multiple settings would require to constructAppearances()
every time. Simply replacing e.g. the border definition wouldn't work as the
padding of the text is dependent on the border width.
{quote}
Is there any reason why we can't construct appearances each time? It's by far
the most robust and reliable approach.
{quote}
Constructing the appearance when it's next fetched would only work AFAIK if
after the changes the form will not be saved immediately. Or we delay
constructing appearances just before saving the document.
{quote}
I was thinking that we could delay constructing the appearance until the
appearance stream is next accessed, but it's going to get quite complex that
way. Probably best avoided.
> Allow to refresh an AcroForm field appearance
> ---------------------------------------------
>
> Key: PDFBOX-2918
> URL: https://issues.apache.org/jira/browse/PDFBOX-2918
> Project: PDFBox
> Issue Type: Improvement
> Components: AcroForm
> Affects Versions: 1.8.10, 2.0.0
> Reporter: Maruan Sahyoun
> Labels: Appearance
>
> When a field widgets 'style' is changed such as a border is defined this is
> not immediately visible as the change is not reflected in the widgets
> appearance stream.
> There should be a possibility to force a refresh of the fields appearance
> after such settings have been specified.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
