A bit late adding a question to this thread but the script below works
only for the first instance. If the end user fails validation a second
time then the field is not cleared.if (this.errorText)
this.rawValue=null;Any suggestions?
It would appear you have missed the point. Before this gets out of hand
let me clarify: multi-lining does NOT give you control over the starting
font. What it DOES do is shrink the starting text slightly. This may or
may not work depending on what you're looking for. For my purposes, and
at least one other person uses this workaround, it is sufficient.To
drive the point home, one of the forms I am working on has a field text
that is roughly 4.8 inches wide. With the font set to auto-shrink for
t...
I am building a form where I have added a repeatable subform. I need a
signature field within that subform. However, LiveCycle has prompted me
with an error in the image below.Several questions:1. Why does it say a
signature may become invalid in a dynamic pdf form? That's a conditional
statement and does not explain what conditions have to be met to render
the signature fields invalid.2. Wouldn't moving the signature filed out
of the subform prevent it from being replicated whenever the end use...
Flrorian - I get what Radzmar said. What I'm trying to convey here is
that if you set the box to allow multiple lines, as both I and SI_MSD7
said, it will shrink the text slightly to give you a smaller starting
text size.
I also stumbled into the "allow multiple line" as a partial fix. While
checking that option does not let you control the starting font size, it
does shrink the starting font size a bit making the font look more
appropriate with forms designed in the 10-11 font size range.
Hi folks - I'm looking for some help with the shrink-to-fit
functionality. Is there a method to set the default starting font to
something other than size 12 for the shrink-to-fit function?
I just rebuilt the data collection for the third time and it finally
seems to have taken and the error has gone away. Very inconsistent
software at times.
I just started working on a newly imported form (original was a Word
docx) and the same error has occurred. I created an object collection
and added one object to see if that would make the error go away but it
hasn't.
When I began adding fields to the data collection I did not have the
Automatic Scripting box checked. I always use automatic scripting for
the bar code but even after I checked that box I still kept receiving
the error message "Your script uses objects from a non-existent
collection." I thought that checking the automatic scripting box and
adding an assigned data collection would resolve this issue. It did not.
What's the deal?
I am working on developing forms that embed select fields into a 2D
paper form bar-code. I have to name some fields using the same binding
name. However, when I scan the barcode and look at the delimited file
those fields are present multiple times. For example, let's say I have a
field called "coffee consumption" and that field has 3 mutually
exclusive check boxes: None, Moderate, and Lots. I need to call each
check box the same exact name so I wrap each check box in a sub form and
then give ea...
I import forms from MS Word. When I begin to move some of the objects
around gray lines sprout out of nowhere. Initially I thought I must've
inadvertently turned on some kind of drawing aid but now I'm almost
convinced this is some kind of bug. These lines print btw. I really need
some input here as this is a showstopper for the project I'm on.
I went through and set my drawing aids to match what you posted and the
gray lines are still appearing. I've scoured the internet and many
forums but I have not seen this issue reported anywhere else. The odd
thing is that it only started happening when I began using the ES4. When
I used ES2 this was never an issue.
I have run into a snag using LiveCycle for form development. Whenever I
select any of the black bars that form the structure of the form, these
gray lines appear out of nowhere. I know I did not intentionally
activate anything. At first I thought they were guide to help the user
see smaller objects but that was not the case because when I went to
print the form those gray lines were clearly visible on the printout. I
do not use Java to develop these forms.
