Patti, You have to move the control up and left, then cut or copy the control, then click on (either kind of) panel, then paste. Then the panel will be the container that the control is in, and the panel will have the form as its container. The way you were doing it, the controls were not contained in the panel.
If you don't move the control up left first, it might paste off the bottom and or right of the panel, and it will be harder to find. Enhanced panels are just newer than panels, and have more properties. Bill (sent from Android mobile) On Jan 25, 2015 4:35 PM, "Patti Jakusz" <[email protected]> wrote: > Hi Bill, > I was experimenting with a panel and put it underneath after my controls > were all on. That didn't work. So maybe I need to put the panel down and > then my controls? And I didn't use enhanced panel. I wasn't really sure > what a panel was so I didn't know if I should "enhance' it. > > Patti > > ------------------------------ > *From:* Bill Downall <[email protected]> > *To:* RBASE-L Mailing List <[email protected]> > *Sent:* Sunday, January 25, 2015 4:09 PM > *Subject:* [RBASE-L] - Re: Another question about Radio Groups > > Patti, > If these controls can all be situated near each other, locate an Enhanced > Panel, put all the controls on the panel, and use a single property command > to make the whole panel and everything on it visible or invisible. > Bill > (sent from Android mobile) > On Jan 25, 2015 4:05 PM, "Doug Hamilton" <[email protected]> wrote: > > Hi Patti - > Give each of the static text and radio groups component IDs that have the > same first x number of characters, then you can use a wild card in the > PROPERTY command: > e.g. > You might name the Static Texts cidST1, cidST2, cidST3a, cidST3b, cidST4, > etc > The radio Groups can the same IDs also - cidST1, cidST2, etc. > The "cid" prefix is part of my own naming convention for ComponentIDs. > > Then issue a PROPERTY cidST* VISIBLE 'TRUE' and they would all be visible, > 'FALSE' makes them invisible. > You could issue PROPERTY cidST3* VISIBLE 'TRUE' to make only cidST3a and > cidST3b visible. > PROPERTY cidST3a VISIBLE 'FALSE' would make only that one question > invisible. > > Be sure you use the correct wild card - type SHOW at the R> and look for > MANY. > > I'm not sure about your second question...make sure the DBEdit is not > buried under the radio group. Right-click the DBEdit and click Bring to > Front; you could then right-click it and make it Hide On Startup. Use the > PROPERTY [componentid] VISIBLE 'TRUE' when they click the appropriate radio > button. > > Happy Sunday, > Doug > > On 1/25/2015 2:23 PM, Patti Jakusz wrote: > > > I have 8 static text and 8 radio groups that I want to make visible or > not. And I have a bunch of sets of these. Is there a way to tie them all > together and make them invisible all at once? > > Also I have a couple of radio groups that have "Other" as the last > button, and then I want to put a edit field for them to describe their > other choice. Is there a type of control for this already build. I tried > to locate my DBedit field in the radio group box, but that didn't work. > > I really hate this form. Entering a form on a computer is not how a > social worker should be getting to know a new client. But, that is what > they want. > > Patti > > > > > > ------------------------------ > <http://www.avast.com/> > This email has been checked for viruses by Avast antivirus software. > www.avast.com > > > >
