K
kirk
I have program.cs, my "main" form and then a "settings" form.
My "main" form existed for awhile and I had constants, instantiations,
properties, etc within it created.
I went to create my "settings" form and constantly found myself
adjusting my "main" form entities to be static and inevitably just
passing in the "main" forms 'this' instance to the "settings"
constructor to simplify it all.
My question is, what is the proper way to be setting this all up. Is
there a way to avoid all of this, and give all forms implicit access
to this written common code in the "main" form? I have many forms to
come later and I don't want to have to tailor each to have a property
or constructor to accept one or more form instances holding
information they may need.
My "main" form existed for awhile and I had constants, instantiations,
properties, etc within it created.
I went to create my "settings" form and constantly found myself
adjusting my "main" form entities to be static and inevitably just
passing in the "main" forms 'this' instance to the "settings"
constructor to simplify it all.
My question is, what is the proper way to be setting this all up. Is
there a way to avoid all of this, and give all forms implicit access
to this written common code in the "main" form? I have many forms to
come later and I don't want to have to tailor each to have a property
or constructor to accept one or more form instances holding
information they may need.