Maybe I’m explaining myself badly
I’m not expecting the index to match the page order. I know the index could not match the page order, this is thee reason I opened this ticket
I’m not using your SDK to get acrofieldTag and selectedIndex.
This is my business logic
A) User1 give me a Pdf file already containing the RadioGroup. I store it
B) User2 give me an acrofieldTag. I have to get the Page, Positions and Dimensions of the widget (if the widget is a RadioGroup, I need Page, Positions and Dimensions and SelectedIndex of every RadioButton) to store them.
C) I give AcrofieldTag, Page, Positions, Dimensions and indexes I got at point B to User3. User3 give me the value I have to write on the Pdf (if the Widget is a RadioGroup, User3 will give me the index of the button he choose)
D) I write the value User3 gave me on the Pdf I got on point A
So, to answer your question, I get both acrofieldTag and selectedIndex from the users
If I could call GetPage, I think I could solve my issue, but Ryan here
told me
is Optional for an Annotation to have a reference to its parent Page, and even if present, is not guaranteed to be correct. It really should be ignored