Problem–displaying graphform fm another form buttonclick event wo losing data

[mwgjr]

Problem – displaying a graphics form from another form’s button click event without losing the XY data plot.

If the Startup form is the GraphWindow form the Graphlib.vb calls create a XY data plot.
Code outline (not everything included):
(Sub GraphWindow_Pai nt(ByVal sender As Object, ByVal e As Sys…PaintEventA rgs) _ Handles Me.Paint)
Call Graphscale(xmin , xmax, ymin, ymax)
Call DrawAxis(10,10)
XY data
Call GraphPlot
End Sub
End Class

If the Startup form is changed to PrintData form with a Test button which calls the GraphWindow form, the Graphlib.vb calls do not create a XY data plot. They are called because certain graph subroutines variables are dumped to a file.

PrintData Form Test button code:
Me.Hide( )
Dim frmGraphWindow1 As New GraphWindow
frmGraphWindow1 .ShowDialog( ) ‘also tried Show

[tlhintoq]

How do I get my Form2 to react to something on my Form1?
How do I make my Form1 control something on my Form2?

Although you can have Form1 directly access items on Form2 it isn't the recommended way to go. It ties the two forms tightly to each other. If a change is made in Form2 such as removing one of the controls, then code in Form1 breaks.
It is better to Form1 raise an event, and have Form2 contain its own code for how to react to this. This places responsibility for Form2 within Form2, and Form1 within Form1.
It keeps Form1 blissfully ignorant of Form2 - and a logging component - and a progress component, and a dozen other little black boxes that can be subscribed to events in Form1, all without Form1 being made responsible for directly affecting controls other than itself.
Events tutorial (including Form to Form which is the same as class to class)
This tutorial for a cash register does exactly that: It makes a virtual numeric keyboard.
Bad: Directly accessing controls of one class/form from another.

bool IsOn = Form2.button1.IsChecked;

Good: Use a property to get such information

//Form1
bool IsOn = Form2.IsOn;

//Form 2
public bool IsOn
{
   get { return button1.Checked; }
   set { button1.Checked = value; }
}

It's a subtle but important difference as your applications become more complex. Using properties means your target class/form (Form2) can be changed and updated a thousand different ways yet won't negatively impact the classes that are reading from it. If you change the name of a control for example: No break in all your other classes. If your target form evolves where it needs to do 10 things when it is turned on, then the responsibility stays within Form2, and that burden on not put on Form1 and a dozen other forms that might be using Form2. The goal is to compartimentali ze the work so that Form2 is responsiblity SOLELY for Form2. From1 should only have to say "Turn on" or "Turn Off"

Form2
public bool IsOn
{
   get { return btnMeaningfulName.Checked; }
   set {
            btnMeaningfulName.Checked = value;
            panelDashboard.Visible = value;
            labelStatus = value == true ? "On" : "Off";
            btnRunNow.Enabled = value;
}

Now when Form1 tells Form2 to turn on, Form2 will check a box, make an entire panel visible, change its Status label to say 'On' and enable a Run Now button.

[mwgjr]

Tryed suggestion with new project, Form1 & Form2 - worked ok with IsOn.
Form1 button_click code: Me.Hide(),Dim Form2req As New Form2,
Form2req.Show
Tryed IsOn code with orginal problem code. Had the same problem.
My problem seems to be when a forms btn_click calls a Graphics form.
(Sub Graphwindow.Pai nt( ..,e As Sys.Win.Forms.P ainteventArgs)