TOPIC:

Good afternoon,

I have been successfully using your Android SDK for a long time (5+ years).
My project is based on a late beta (or very early revision) of version 3.0 of the SDK.
I'm in the process of updating it to the latest version of the Android SDK (3.52.7).

The library is used primarily to edit PDF forms.

While the upgrade went mostly smoothly, there is an issue that nags me: multiple selection in check boxes in PDF forms.
That is: multiple check box fields sharing the same field name...
Previously, I was able to select multiple values.
With latest version, as soon as I select a new value, previous values are deselected.

As far as I can tell, method PDFPerformAnnot correctly identifies the field as being a checkbox (values 0 and 1) and not a radio button.

Any help would be appreciated.

Regards,
Michele Noberasco

Dear Michele,

Can you please send us a sample file?

Hi nermeen,

thank you for your reply.
Attached you will find an example of affected document.
It sports 2 groups of check boxes.

Regards,
Michele

Our developers are checking your file, we will get back to you as soon as possible.

Dear Michele,

Please check the new beta 3.53.1 beta3 , it should fix your issue.

Hi nermeen,

I tried out the new beta.

New behavior is different both from release version and ancient version I had been using:
- with ancient version, check boxes can be *individually* selected (tapping on one will not affect other check boxes of the same group)
- with current release version, only one checkbox of a given group can be selected (tapping on one will deselect all other check boxes of the same group)
- with new beta version, either all check boxes of a group are selected, or none is (tapping on a check box will select/deselect all check boxes of the same group)

I had been expecting 'ancient' behavior back, but got something else instead.
This makes me wonder: 'which should be the correct behaviour'?
I tried editing the form with Adobe reader, it matches the new behaviour of this latest beta.
Can you confirm this new behaviour is correct and adhering to PDF form specifications?

Regards,
Michele