[PiscesHunter]

I need to hide the a form using a button from my current active form. let see for example there is two form open and I am using form2 and then form1 was inactive. i want to hide the form1 using the button from form2..could give me a hint on how to do it guyz//..ty

here is my code

namespace windowsAppication1
{
 public partial class Form2:Form
 
 public Form2()
 {
  initializeComponent();
 }
 private void button1.click(object sender, EventArgs e)
 {
  Form1 f1 = new Form1();
  f1.hide();
 }
}

[h4nnib4l]

Write all that code yourself? Seriously, if you don't even have the forms yet, let alone the button to close it, how have you even tried to accomplish this yourself?

You'll have to set the form's visibility attribute in the button's click event handler. Something like:

protected void MyButton_Click(object sender, EventArgs e)
{
    myForm2.Visible = false;
}

EDIT: First comment was before any code showed up in the OP beyond namespace windowsApplication1{}.

This post has been edited by h4nnib4l: 11 December 2012 - 03:28 PM

[PiscesHunter]

here is my code sir.. i misenter the button so that's why i didnt finish my post..

namespace windowsAppication1
{
public partial class Form2:Form

public Form2()
{
initializeComponent();
}
private void button1_click(object sender, EventArgs e)
{
Form1 f1 = new Form1();
f1.hide();
}
}

This post has been edited by Skydiver: 11 December 2012 - 06:26 AM
Reason for edit:: Put code in codetags. Please remember to do this in the future.

[Skydiver]

Your post #3 still looks very much like post #1. Both of which will fail to compile.

Once you do get your code to compile, you will still run into an issue because your line 11 creates a new instance of Form1. You won't be affecting the existing instance of Form1 that you want to make invisible.

h4nnib4l has the correct solution.

[tlhIn`toq]

Quote

 private void button1.click(object sender, EventArgs e)
 {
  Form1 f1 = new Form1();
  f1.hide();
 }
}

Your code does exactly what you are telling it to do.
You make a NEW INSTANCE of a form, of type Form1.
Then you hide the new instance.

The real problem here is not the code as much as it is your understanding of the fundimentals of the language and objects. It seems clear that you do not yet understand that you make instances of objects. You can make 100 new instances of the Form1 type for example. They are all unique and unrelated. Like making 100 Dodge Ram pickups that are all identical in model/color and features. But they are still 100 unique instances of the blueprint.

My first suggestion would be to stop and re-read the intro chapters of whatever book you are working through because you missed some important stuff.

Secondly: From my FAQ list...

[*]Q: ...get Form 'A' to make a change or talk to Form 'B'

NOTE: Don't try to access GUI controls across forms. Its wrong. Nobody will hire you if you do this sort of crap. It violates every guideline for 'black box' programming, Separation of Responsibility, loose binding of components, and event driven programming. Read the tutorials and learn to do it right the first time so you don't develop bad habits that you just have to un-learn later.
A:

• See this thread for the simplest of example code between two forms.
  
  The tutorials below actually teach and explain it further.
  
• Passing values between forms/classes
  
• Bulding an application - Part 1
  
• Building an application - Part 2
  
• Quick and easy custom events
  
• Delegates, Lambdas and Events
  
• http://www.codeproje...g-Windows-Forms

[h4nnib4l]

I honestly deleted my next reply before I posted, because I knew that whatever I was going to try to explain was most likely explained better in one of tlhIn`toq's tutorials. I got distracted while looking for it, and never found/posted it. Knew I'd seen one about two forms communicating.

[PiscesHunter]

h4nnib4l, on 11 December 2012 - 03:27 PM, said:

I honestly deleted my next reply before I posted, because I knew that whatever I was going to try to explain was most likely explained better in one of tlhIn`toq's tutorials. I got distracted while looking for it, and never found/posted it. Knew I'd seen one about two forms communicating.

sorry sir for my senseless post, i am just a newbie in c# i just got interested on it so i don't know much more about it...thanks for you replies

[PiscesHunter]

tlhIn`toq, on 11 December 2012 - 08:47 AM, said:

Quote

 private void button1.click(object sender, EventArgs e)
 {
  Form1 f1 = new Form1();
  f1.hide();
 }
}

Your code does exactly what you are telling it to do.
You make a NEW INSTANCE of a form, of type Form1.
Then you hide the new instance.

The real problem here is not the code as much as it is your understanding of the fundimentals of the language and objects. It seems clear that you do not yet understand that you make instances of objects. You can make 100 new instances of the Form1 type for example. They are all unique and unrelated. Like making 100 Dodge Ram pickups that are all identical in model/color and features. But they are still 100 unique instances of the blueprint.

My first suggestion would be to stop and re-read the intro chapters of whatever book you are working through because you missed some important stuff.

Secondly: From my FAQ list...

[*]Q: ...get Form 'A' to make a change or talk to Form 'B'

NOTE: Don't try to access GUI controls across forms. Its wrong. Nobody will hire you if you do this sort of crap. It violates every guideline for 'black box' programming, Separation of Responsibility, loose binding of components, and event driven programming. Read the tutorials and learn to do it right the first time so you don't develop bad habits that you just have to un-learn later.
A:

• See this thread for the simplest of example code between two forms.
  
  The tutorials below actually teach and explain it further.
  
• Passing values between forms/classes
  
• Bulding an application - Part 1
  
• Building an application - Part 2
  
• Quick and easy custom events
  
• Delegates, Lambdas and Events
  
• http://www.codeproje...g-Windows-Forms

thanks sir for this link you've posted i'll read all about it and learn how to properly understand more about c#.