I have a controller class that creates an object and then calls a form for
the user to fill in some information that will populate the object with
after the form is closed. What is the best way for the controller to get
the data the user entered into the form. Should the controller pass the
object to the form and let the form in the save button assign the text box
fields to the object properties or should the form expose public properties
which the controller can call after the form returns and then the controller
populates the object properties? Or is there a better way to do it?
Bill
Mr. Arnold - 25 Jun 2007 00:28 GMT
>I have a controller class that creates an object and then calls a form for
>the user to fill in some information that will populate the object with
[quoted text clipped - 5 lines]
>controller populates the object properties? Or is there a better way to do
>it?
The object should be independent of who is using it. It should be passed
between the two, with each class working with the object as needed and
independently.
Ray Cassick - 25 Jun 2007 00:30 GMT
I like adding properties to the form for things like this.
>I have a controller class that creates an object and then calls a form for
>the user to fill in some information that will populate the object with
[quoted text clipped - 7 lines]
>
> Bill
Bob Powell [MVP] - 27 Jun 2007 20:08 GMT
See Windows Forms Tips and Tricks.

Signature
Bob Powell [MVP]
Visual C#, System.Drawing
Ramuseco Limited .NET consulting
http://www.ramuseco.com
Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm
Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm
All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.
> I have a controller class that creates an object and then calls a form for
> the user to fill in some information that will populate the object with
[quoted text clipped - 6 lines]
>
> Bill