These forums are now Read Only. If you have an Acrobat question, ask questions and get help from one of our experts.

Icon buttons not working

Masi
Registered: Sep 18 2008
Posts: 22
Answered

XFA Specification 2.5 (and laters) specifies an icon button widget that may contain image references to icon image, rollover icon image and mouseDown icon image. Still this doesn't seem to work in Designer ES / Acrobat 9.3 when using following button definition:
<field relevant="-print" h="10mm" name="button" w="30mm" x="0mm" y="0mm">
<caption>
<font typeface="Arial" size="9pt">
<fill>
<color value="55,55,55"/>
</fill>
</font>
<value>
<text> Up Text </text>
</value>
</caption>
<value>
<image contentType="image/jpeg" href="..\Images\Button.jpg"/>
</value>
<items>
<image name="down" contentType="image/jpeg" href="..\Images\Button_h.jpg"/>
<text name="down"> Down Text </text>
<image name="rollover" contentType="image/jpeg" href="..\Images\Button_d.jpg"/>
<text name="rollover"> Rollover Text </text>
</items>
<font typeface="Arial"/>
<margin leftInset="7mm"/>
<ui>
<button highlight="push"/>
</ui>
</field>
 
Rollover and down states works when using only texts. But when the image references are defined then text effects stop working too.
 
Currently we use javascript and imagefields to show two different images under the button depending on user action. But when the form is signed, javascript that changes the image presence will set the signature status to unkown and the signature panel will show several fields that have changed their properties. Using icon button widget would be the best solution for us regarding this issue, but it just doesn't work even when it has been in specification for several version numbers.
Any ideas how this could be solved or how we can get the same effect without breaking existing signatures.
 
- Masi

My Product Information:
LiveCycle Designer, Windows
Masi
Registered: Sep 18 2008
Posts: 22
Accepted Answer
Latest specification has a note that image buttons described above are not implemented in Adobe products. Hopefully they will implement it in future since I think it is important usability issue and although javascript can be used to implement similar functionality, there are cases where javascript cannot be used or are not allowed to be run at the first place.