Anyone know the logic behind this?
It seems that if you create a form from scratch in LiveCycle Designer ES3, you do have the possibility of setting edges for e.g. text fields to be None - rendering them usable (you can tab to them), but invisible. However, given there is no underlying artwork, you probably would not want this.
However, when you are basing a form design on a PDF artwork (e.g. from InDesign) when you are far more likely to want your fields to be 'invisible' - Designer does not allow it.
So, if - for example - your PDF artwork contains some great 'graphic' field areas that you want to make fillable in Designer, you seem to have to endure having Designer plonk its own 'lines and squares' on top (not so pretty).
This seems an odd state of affairs - it seems obvious that if you are bringing in pre-existing artwork, then in most cases the fields will have been done by the DTP person (to keep the graphic integirty of the design). So, anyone bringing it into Designer would assume that Designer could put interactive fields on top, but as 'see through' fields - just as Acrobat can do.
Is there any technical reason why Designer can't do this? Seems a bit weird.
