Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

kingphysh
kingphysh
Offline

Badges

Badges
27

Accepted Solutions

Accepted Solutions
35

Likes Received

Likes Received
41

Posts

Posts
288

Discussions

Discussions
9

Questions

Questions
279

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Top badges earned by kingphysh
Customize the badges you want to showcase on your profile
Re: flowed subforms (again) - Adobe LiveCycle 10-11-2017
Simply, from the perspective of you just beginning to use Designer (on day #1)? The answer is No. You cannot switch to "flowed" and expect the objects to remain in their initial layout. You must put the objects in the flowed order that you want (drag and drop in the hierarchy panel) and size them in the "Layout" panel to get the layout you desire, when using "flowed".

Views

1.7K

Likes

0

Replies

0
Re: Using string to designate a subform for the instanceManager - Adobe LiveCycle 12-03-2014
Hi Radzmar,I ran your JS script (added a semicolon at the end of 1st line) and got:Exception in line 2 of function top_level, script XFA:form1[0]:SubformBody[0]:SubformLocation[0]:SubformPropCrDb[0]:DdlPropCreditDesc[0]:exitAlso, tried the same without the quotes ("1") with same resultAny idea whats going on?Message was edited by: kingphysh

Views

828

Likes

0

Replies

0
Re: Using string to designate a subform for the instanceManager - Adobe LiveCycle 12-03-2014
Thanks Robert,I might be missing something--I've never seen square brackets used in the way you suggest. Am I missing something?The subform doesn't have an index[propOptSubformID] It would have an index[0] when it actually does exist. This isn't really an index problem. That would be easy and I think I may have to go that way (i.e. name them alll the same and reference them by index) if I can't reference the object.instanceManager and use its method setInstances() with a string.This might be a c...

Views

829

Likes

0

Replies

0
Using string to designate a subform for the instanceManager - Adobe LiveCycle 12-03-2014
var propOptSubformID = "8011"var propSubformName = Concat("SubformPropOption",propOptSubformID,".instanceManager") //since instanceManager is object$.resolveNode(propSubformName).setInstances(1)I get:I can't seem to find a way to use the instanceManager and successfully reference a subform using a string. Any ideas? I want to avoid using conditional statements or switch if possible. I have 35 different subforms eachl with 0 instances. I want to identify one of the subforms using a variable (stri...

Views

1.5K

Likes

0

Replies

4
Re: Field Appearance "underline" not visable in Preview PDF - Adobe LiveCycle 27-07-2012
OK--a few things. I have found that some lines require a min of .01in thickness to be rendered. The default .0069in doesn't cut it for check boxes, and I believe the underline style of a text field, also. It really doesn't perceivably change the appearance/thickness but it impacts whether it will be rendered.Also, try set to "None" the "Background Fill" in the Borders Tab--like in the image I posted a while ago (above). Sometimes the fill interferes with the border rendering. I'm dealing with a ...

Views

800

Likes

0

Replies

0
Re: Problem with Subform Instances at First Opening - Adobe LiveCycle 17-04-2012
OK--I figured it out--however, I still don't fully understand it.Thanks! kjaeggin for your question: "did you or did you not reproduce this with a simplified version of your form?" I had tried some simplifications, using "Inactive" presence--but that didn't flesh out the problem.I started deleting parts of the form one subform at a time--testing after each delete -- until the behavior went away.Here's what I found:mySubform had a sibbling and a child subForm with the same name and I was using th...

Views

978

Likes

0

Replies

0
Re: Problem with Subform Instances at First Opening - Adobe LiveCycle 17-04-2012
I'm sorry. I can't post my form to a public place. Even if I could share it, I think it highly unlikely that someone would have time to carefully examine the form (it contains 1000's of objects and has 80,643 lines of XML). Besides, the answer is figuring out what happens during the original layout, that doesn't happen with initiation of a new instance? That is, understanding the form processing better will help to determine where to look to find the cause.Just now, as an experiment, I added a b...

Views

968

Likes

0

Replies

0
Re: Problem with Subform Instances at First Opening - Adobe LiveCycle 17-04-2012
Hi, Thanks kjaeggin and Bruce,I have the checkBoxes unchecked and the occur element is .Actually, this is the way the checkBoxes and XML have been all along and the results are what what I have previously described. One of my attempts to fix this was manually adding the "initial" attribute to the element (by directly editing since it won't stick in the Object pallet) that the edit reverts to .Also I have tried this is what I really want (max="1") and it reverts to as wellAnd reverts to The...

Views

963

Likes

0

Replies

0
Re: Problem with Subform Instances at First Opening - Adobe LiveCycle 16-04-2012
Hi, The target version is set for Acrobat/Reader 10.0 or later. Here is the scenerio://////////////////////Grandparent //min="1" Parent //non-reoccuring mySubform //min="0" TextField1//////////////////////Right now, when I open the form, I get: GrandParent.Parent.mySubform.TextField1 (I see TextField1 and that is not what I want) And when I do Grandparent.addInstance(1) I get: GrandParent.Parent.nothingElse (I don't see mySubform.TextField1 in the new GrandParent. Great! that is as it should be)...

Views

962

Likes

0

Replies

0
Re: Problem with Subform Instances at First Opening - Adobe LiveCycle 16-04-2012
Hi, Thank you for considering my problem and posting your questions. I am not merging data and I have not associated a Schema. No Data Connection has been set up, yet. Any bindings are "Use name". Perhaps this will help:I will call the subform described above: mySubformRegarding this.parent.parent of mySubform can also have multiple instances--but, is set to start with 1 instance (which it does correctly). When an instance of this.parent.parent is added, it does so correctly--without containing ...

Views

970

Likes

0

Replies

0