Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Child form alignment
Message
From
21/12/2006 08:14:14
 
 
To
20/12/2006 21:09:21
Dragan Nedeljkovich (Online)
Now officially retired
Zrenjanin, Serbia
General information
Forum:
Visual FoxPro
Category:
Forms & Form designer
Miscellaneous
Thread ID:
01179249
Message ID:
01179500
Views:
8
I agree with you Dragan. In my experience, whenever I have attempted to force a child form's position in the past, users screamed holy terror. Often they want to move the child form out of the way temporarily to peek back at the parent form and see what record they were on or what they had typed when the child form was launched. They then move the child form back and start entering data or reviewing data, etc. Still, the idea of docking a child form within a parent form could be useful in some cases...



>>>Now if you wanted the child form within the parent form - that sounds like your parent form is a MDI form, but in the MDI paradigm child forms are free floating inside the parent form. This paradigm was invented for apps that handle one file per window, like Word.
>>>
>>>Now you want the child form to be in a fixed position over your form - which makes it a perfect candidate to not be a form at all, but rather a container. Sergey's already suggested a pageframe (tabbed or tabless - up to you) to hold your grids, which I would also suggest - except he's faster, as usual :).
>>
>>I'm not sure I follow. Why would a free-floating modal form need to be a child form at all? Any form can be that. What I was looking for was a form that would exist strictly within the context of the parent, including positioning. It's no longer an issue, Sergey steered me to the path of righteousness, but I guess I remain curious. What use are FoxPro child forms, anyway? I would especially be interested in the input of those who have used them.
>
>The only trouble is your wish for it to have a fixed position. The users have got this habit to move windows as they like, and if you create a form which can't move, they'll be at least somewhat confused, or maybe even pis*ed off.
>
>As for the general role of child forms in a MDI form, I haven't found use for them yet, not in a VFP app. Even in one case where I have an OCX editor within the app, the editor's window(s) reside(s) in _screen. This doesn't mean there isn't an app which would benefit from a MDI, just means I didn't write one yet.
.·*´¨)
.·`TCH
(..·*

010000110101001101101000011000010111001001110000010011110111001001000010011101010111001101110100
"When the debate is lost, slander becomes the tool of the loser." - Socrates
Vita contingit, Vive cum eo. (Life Happens, Live With it.)
"Life is not measured by the number of breaths we take, but by the moments that take our breath away." -- author unknown
"De omnibus dubitandum"
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform