I meant to say change event per what your example was. I guess it is an
intersting bit of info that rawValue will work in the change event of a
checkbox. I'll stick to using xfa.event.newText to be consistent and
ensure someone looking at my code to apply to something else doesn't
have a problem.
"Is there any way I can achieve directly using bindings since we are
Have you created a Schema, data connection to it and bound your form
elements? If you bind two elements to the same item in the data
connection, when you change one, the other changes.
"hidden";TextField1.presence = "visible";The sub form the items are in
and all above it in the tree must have autosize on height.
Drop box is blocked for me.rawValue is not changed yet in the change
event. You need to use xfa.event.newText.The global variable thing seems
a waste to me. Can't you just reference the rawValue of each check box
in the calculate event of the text field?
I don't have an ID and am not going to create one to open the file.What
is this setting: File > Form Properties > Defaults tab > Preserve
scripting changes to form when saved? If manual, try automatic. If
already automatic, in what event are you setting the access to open.
When you say binding, do you mean an array index? Have you created an
XML Schema? The first step i perform when creating a form is to create
an XML Schema, create a Data Connection in the form with that Schema and
bind all my form elements to their corresponding data items. I don't
understand what it is that is going wrong for you, but binding to a
schema gives you control over what gets exported and imported.
It also works on my system to add a blank item at Design time. Maybe it
is a difference in the Acrobat version that the blank item is removed. I
would try removing the blank item at design time and adding in the
initialize event to see if it fixes it on the users system.
I don't hink you will be able to merge them as form based PDFs. Most if
not all third party libraries for PDFs don't handle them. Maybe install
Acrobat Pro on a server, set it up somehow to print to PDF to use that
the 'flatten' the form into a non-interactive one that third party tools
can deal with. We own the LiveCycle a server products that can flatten
them so it is just theory on my part.
If the exported XML is the same, I doubt adding a schema will help other
than it may make the file growth smaller. I am thinking the extra data
after the EOF is the form data, multiple saves, save multiple copies and
opening in Acrobat combines it all together. It is just a theory though.