I have made the Graph class, and i want to simulate a distribution network. The Graph works 100%. But, i want to use that same struct/class in all my application! For example: I have Form1 that shows the simulation, but i want to insert Nodes (for example) but i want to do it in Form2! Since the data is always in the same class, i could make my Graph instance global but C# does not take global variables. So, how would i solve this? Any ideas? Thank you!
+4
A:
Give the forms a reference to the Graph in their constructor.
Graph g = new Graph();
Form1 f1 = new Form1(g);
Form2 f2 = new Form2(g);
Then both forms are working with the same graph.
Matt Greer
2009-12-29 18:23:48
OP here,So your saying that f1 and f2 have the SAME graph? not a copy?
Ricardo
2009-12-29 18:29:22
They each have different **references** to the same graph, but yes, it's the same graph.
John Feminella
2009-12-29 18:31:43
thank you very much!
Ricardo
2009-12-29 18:32:44
Other people are recommending the Singleton pattern. However, I recommend caution with that pattern, as it can be a crutch and it can really hamper your code in the long run. Not saying singleton pattern is always bad, but it's a difficult pattern to use correctly.
Matt Greer
2009-12-29 18:37:38
Problem is solved! I thought that would generate a copy of the instance, but it really passes the SAME instance to both forms.
Ricardo
2009-12-29 18:41:49
Both f1 and f2 got different references that lead them to the same object.
Matt Greer
2009-12-29 18:46:21
A:
C# has static fields for this. You can use SIngleton pattern in conjunction with static field. But don't forget that misusage of application-wide objects can bring down your design.
Vitaliy Liptchinsky
2009-12-29 18:23:59
+2
A:
Make your Graph instance a public static member of a static class and for all practical purposes you have your global.
Nemanja Trifunovic
2009-12-29 18:24:22
+2
A:
Take a look at the Singleton pattern for one possible approach to having a common object:
Peter Loron
2009-12-29 18:24:30
+4
A:
Make a static class. The variables that need global access, put them inside that class.
Even better idea would be to use Singleton objects to represent globally accessible objects.
missingfaktor
2009-12-29 18:24:39
Note that either solution will cause all consumers to be tightly coupled to the Graph class. Among other things, this will make it difficult to test those consumers in isolation.
TrueWill
2009-12-30 01:17:33