I'm having second thoughts about the performance of an MDI application I'm trying to make.
The application consists of some child forms within the MDI parent.
There aren't any problems when I run and eventually close one child form (which has its Top and Left properties set to "0"), as in here (don't know how to make the images small, sorry):
Attachment 96889
However, when I re-run the *same* child form, its .Top and .Left properties already changed, moving it twips away from the edge of the parent's borders, as in here:
Attachment 96891
It's as if the application acknowledges that the first "instance" of the form I opened is still there, that's why it moved the second "instance".
That somehow makes me think: is the first form still there?
I mean, what if the form was opened and closed say, 20 times? Do those 20 "instances" stick to the parent and consume system resources, even though the user knows that he already closed the forms?
I hope someone can understand my problem. Thanks in advance!!!!
The application consists of some child forms within the MDI parent.
There aren't any problems when I run and eventually close one child form (which has its Top and Left properties set to "0"), as in here (don't know how to make the images small, sorry):
Attachment 96889
However, when I re-run the *same* child form, its .Top and .Left properties already changed, moving it twips away from the edge of the parent's borders, as in here:
Attachment 96891
It's as if the application acknowledges that the first "instance" of the form I opened is still there, that's why it moved the second "instance".
That somehow makes me think: is the first form still there?
I mean, what if the form was opened and closed say, 20 times? Do those 20 "instances" stick to the parent and consume system resources, even though the user knows that he already closed the forms?
I hope someone can understand my problem. Thanks in advance!!!!