1. Re: group control: parent to members ; & control selection
Hi, Dan,
Yes, that's exactly what I planed for group parenting in the .exw, I just
haven't gotten there yet. And all controls in the group would be parented
and x,y corrected.
The concept of being able to add another control just like the one you just
added WAS the way the IDE worked prior to the changes I made for the
depression of Control pad control and lifting up problem you found. That
routine is a bit harry but I'll see where it prevents multiple use of the
control picked. If all else fails, I'll put back the original code.
Judith
On Tue, 10 Oct 2000 05:53:08 -0700, Dan B Moyer <DANMOYER at PRODIGY.NET>
wrote:
>Judith,
>
>re: GROUP CONTROL PARENT TO MEMBERS:
>I wasn't sure from reading your todo if you intend to make elements of a
>group be parented to the group. Radio buttons in particular *need* to do
>that, so if you click on a radio *outside* the group, it shouldn't affect
>any radio *inside* any other group (and visa versa), but would affect any
>other radios *inside* its group. You do have to make sure to position the
>controls inside the group *relative to the control*, rather than the
window,
>which I forgot to do when testing this :)
>
>Not sure if any others placed in a group need to be parented, but it would
>seem to be a good idea, I would think.
>
>re: RETENTION OF SELECT A CONTROL TO USE:
>And here's another thought:
>maybe it would be a good idea to allow the retention of the selection of a
>control to create after the user has created one? I mean: user clicks a
>button to select a control to use, then clicks in design pad to put control
>there; but if they want to make another of same type, has to go back &
click
>same button again; why not just leave previous selection selected? If they
>want something else, they'll have to click on its button anyway.
>
>Dan
