This topic contains 3 replies, has 0 voices, and was last updated by Anonymous 9 years ago.
- February 24, 2010 at 3:42 pm #422
Maybe, I am doing this wrong but when I set a group that contains a bunch of fields to read-only, I can still edit all the fields in that group. When I set the group to hidden or disabled, that works as expected. Is this expected behavior or a bug?February 24, 2010 at 4:12 pm #5096
Could be expected if you haven’t set it correctly and there are other controls involved overriding the ‘group’ level behaviour. but what you have done on the ‘group’.. just add in the specific elements in the group as well to the SetState scriptFebruary 24, 2010 at 5:31 pm #5097
Each of the objects inside of the group have their states set to default. No behaviors alter their state. Setting the group’s state to hidden or disabled makes the entire group hidden or disabled, but setting it to read-only is not affecting any of the fields in the group. I’m not actually using the Set State object command. These fields need to stay read-only throughout the life of the form so I am setting in the properties section for the group.February 25, 2010 at 9:37 am #5098
See what you mean now this is ‘expected’ (although does make me think it isn’t correct behaviour so will raise it with the developers). But just select each item in the group and set their state to read only to get the behaviour you want
You must be logged in to reply to this topic.