C# Discussion Boards - CodeProject

Re: Checking required fields in a second Windows Form

Not Active27-Oct-09 14:50

Not Active

27-Oct-09 14:50

The application is behaving exactly as planned. You are calling ShowDialog twice.

public void GetForm2()
{
  Form2 qForm = new Form2();
  qForm.ShowDialog(); <---- Form2 opened. Not needed

  if (qForm.ShowDialog()== DialogResult.OK) <------ Form 2 opened again
  {
    CaseNo = qForm.CaseNo;
    Reason = qForm.Reason;
    MessageBox.Show("Form2 Exists" + " " + CaseNo + "  " + Reason);
  }
  qForm.Dispose(); <----- Not needed
}

only two letters away from being an asset

Re: Checking required fields in a second Windows Form

JTRizos28-Oct-09 5:57

JTRizos

28-Oct-09 5:57

Thank you ... that handled Form2 popping up twice and I learned something. I thought the first one opened the form and the second was just a check.

However, the check for an empty textbox now just drops through even if a textbox is empty and the message appears. Am I missing something on how Form2 is processed versus how Form1 is processed? Maybe which form is the primary form? I would expect for the process to stay within the if/else until the textboxes are no longer empty. That is what similar code in Form1 does.

Almost there.

Thanx again

Re: Checking required fields in a second Windows Form

Not Active28-Oct-09 9:20

Not Active

28-Oct-09 9:20

I would suggest you maybe email me what you have. That way I can take a look at the whole problem and maybe be better able to help you at this point.

only two letters away from being an asset

Re: Checking required fields in a second Windows Form

JTRizos29-Oct-09 11:19

JTRizos

29-Oct-09 11:19

GOT IT!!!!! Thank you all for your input. The trick is to set the DialogResult to None in properties. Big Grin | :-D

Also, I sure hope you all work out this smal argument. Sigh | :sigh:

Re: Checking required fields in a second Windows Form

Not Active29-Oct-09 11:29

Not Active

29-Oct-09 11:29

Excellent.

I know the language. I've read a book. - _Madmatt

Re: Checking required fields in a second Windows Form

_Madmatt28-Oct-09 6:09

_Madmatt

28-Oct-09 6:09

Mark Nischalke wrote:
As you are having difficulties understanding, I'll try to make this very clear, again.

I'm so sorry, my English isn't that good.

If Form1 creates Form2, Form2 can check its own textboxes. When those boxes are empty, you just display a message. If the textboxes are valid, Form2 closes itself and Form1 can still acces the textbox.Text properties. You may not Dispose Form2 for that Wink | ;)

I'm not yet studying c# so you may conclude I'm beginner Smile | :)

Re: Checking required fields in a second Windows Form

JTRizos28-Oct-09 6:35

JTRizos

28-Oct-09 6:35

Thanx _Madmatt, your English is good, no problem. I understand what you are saying but am confused on the HOW. I am also new to C# and am getting used to the gotchas. I am sure the problem is with how the Dialogresult is handled, just not clear on how I need to handle it.

Thanx again for your suggestions.

Re: Checking required fields in a second Windows Form

_Madmatt28-Oct-09 9:02

_Madmatt

28-Oct-09 9:02

You're welcome!

Maybe you can show your Form2 just in a form and not in a Dialog. Then you just check if your textboxes are empty like this:

if (txt1.Text == null)<br />
{<br />
// TextBox1 is empty<br />
}<br />
<br />
else if(txt1.Text != null)<br />
{<br />
// TextBox is not empty do something with the text ;)<br />
}

Re: Checking required fields in a second Windows Form

Not Active28-Oct-09 9:25

Not Active

28-Oct-09 9:25

_Madmatt wrote:
I'm so sorry, my English isn't that good.

I don't buy this excuse

You still have not answered the question, why is doing it in code better? But no matter, not worth continuing based on below.

_Madmatt wrote:
I'm not yet studying c#

Then you absolutely should not have answered in the first place Mad | :mad:

only two letters away from being an asset

Re: Checking required fields in a second Windows Form

_Madmatt28-Oct-09 9:33

_Madmatt

28-Oct-09 9:33

Mark Nischalke wrote:
Then you absolutely should not have answered in the first place

You don't give beginners a chance? Ow that's pretty nice...

Re: Checking required fields in a second Windows Form

Not Active28-Oct-09 10:18

Not Active

28-Oct-09 10:18

Beginners, yes. However, by your own admission you do not even know the language. You can't comment on things you don't know!! Mad | :mad:

only two letters away from being an asset

Re: Checking required fields in a second Windows Form

_Madmatt28-Oct-09 20:59

_Madmatt

28-Oct-09 20:59

Mark Nischalke wrote:
you do not even know the language.

I know the language. I've read a book. But I'm still at secundary school, so I've not studied c# yet at high school. I surely know the language, otherwise it would be stupid to wate my time on it...

Re: Checking required fields in a second Windows Form

Not Active29-Oct-09 11:37

Not Active

29-Oct-09 11:37

http://www.codeproject.com/Messages/3252116/Re-Checking-required-fields-in-a-second-Windows-Fo.aspx[^]

_Madmatt wrote:
I'm not yet studying c#

_Madmatt wrote:
I surely know the language,

So which is it? Do you know the language or not? Are you confused or just a liar?

But hey, thanks for giving me a new sig Laugh | :laugh:

I know the language. I've read a book. - _Madmatt

Re: Checking required fields in a second Windows Form

_Madmatt29-Oct-09 20:44

_Madmatt

29-Oct-09 20:44

Very simple... Both, I know c# but I'm not yet studying it at school. Or is that too difficult for you to umderstand?

Re: Checking required fields in a second Windows Form

Not Active28-Oct-09 1:16

Not Active

28-Oct-09 1:16

I'm still waiting for your explanation.

only two letters away from being an asset

Re: Checking required fields in a second Windows Form

_Madmatt28-Oct-09 6:10

_Madmatt

28-Oct-09 6:10

I'm not online all day long Wink | ;)

Re: Checking required fields in a second Windows Form

EliottA29-Oct-09 6:53

EliottA

29-Oct-09 6:53

Surely you could have just answered his question instead of writing "I'm not online all day long"?

I wouldn't argue further, your logic isn't correct, and you might want to reread those books of yours.

Check out the CodeProject forum Guidelines[^]
The original soapbox 1.0 is back![^]

Re: Checking required fields in a second Windows Form [modified]

_Madmatt29-Oct-09 7:05

_Madmatt

29-Oct-09 7:05

I don't know if you can read, but I've already answered... Read the whole topic before you say stupid things like that.

EDIT: What I said was just a suggestion about how he COULD do it. I've ABSOLUTELY NOT said "this is the best solution". It's the solution how I should do it with my skills and my understoodings about his issues. But if there are better solutions, no problem for me! I have still to learn, but it's not needed to slap me down. Everybody here has ever started with something where there were better solutions for? Or was you a pro from the first day on?
Last but not least a quote from the rules: "Let's work to help developers, not make them feel stupid.."

modified on Thursday, October 29, 2009 1:15 PM

Re: Checking required fields in a second Windows Form

EliottA29-Oct-09 8:29

EliottA

29-Oct-09 8:29

Funny, I don't see that in the rules[^].

Plus, I'm not the one who looks stupid here.

And you did say it was the easiest method, and you where asked how and ignored it. If anything, you proved your own stupidity, not mine.

Check out the CodeProject forum Guidelines[^]
The original soapbox 1.0 is back![^]

Re: Checking required fields in a second Windows Form

_Madmatt29-Oct-09 9:23

_Madmatt

29-Oct-09 9:23

Are you blind???

Apologies for the shouting but this is important.

When answering a question please:

1.Read the question carefully

2.Understand that English isn't everyone's first language so be lenient of bad spelling and grammar

3.If a question is poorly phrased then either ask for clarification, ignore it, or mark it down. Insults are not welcome

4.If the question is inappropriate then click the 'vote to remove message' button

Insults, slap-downs and sarcasm aren't welcome. Let's work to help developers, not make them feel stupid..

Re: Checking required fields in a second Windows Form

EliottA29-Oct-09 9:27

EliottA

29-Oct-09 9:27

Again, you never asked the question, so that really doesn't apply to you. If someone asks a question, and another gives an answer that is wrong, or clearly not what is desired, then a 'slap-down' is necessary. You didn't ask for the help, so there is no help for you given. I'm not making you feel stupid either, I think you are accomplishing that on your own.

Check out the CodeProject forum Guidelines[^]
The original soapbox 1.0 is back![^]

Re: Checking required fields in a second Windows Form

_Madmatt29-Oct-09 9:34

_Madmatt

29-Oct-09 9:34

Again, I've replied, but my answer was wrong. Okay, I really accept it...
I've answered wrong.
I've answered wrong.
I've answered wrong.
I've answered wrong.
I've answered wrong.
I'm soooooooo sorry. Man, everyone has to learn...

Okay, I said it was the easiest method to do it, but that was following my skills. I've already said I accept another solution. But no, again someone has to start a discussion...

Synchronous socket and WaitHandle/WaitAny confusion

Jerry Evans26-Oct-09 8:05

Jerry Evans

26-Oct-09 8:05

Struggling to adapt a C++ pattern to C#. How do I get a WaitHandle from an IntPtr, which is the underlying socket handle to use in the socket thread as outlined below? I know there are Aysnc socket varieties but I'm keen to reuse this if at all possible. *** indicates the problem area in code

Thx++

Jerry
//
AutoResetEvent evtHalt = new AutoResetEvent;
//
Socket socket = new Socket(...);
//
WaitHandle handles = new WaitHandle(2);
// set up handles
handles[0] = evtHalt;
// *** Nope *** conversion problems -
handles[1] = socket.Handle;
//
while (true)
{
Int32 ret = WaitHandle.WaitAny(handles);
if (ret == 0)
{
// cancelled as evtHalt was signalled
break;
}
else if (ret == 1)
{
// socket signalled ... do something
}
}

Re: Synchronous socket and WaitHandle/WaitAny confusion

Gary R. Wheeler29-Oct-09 12:57

Gary R. Wheeler

29-Oct-09 12:57

Why don't you want to use the built-in .NET socket stuff? It's so easy it's downright sinful.

We have a proprietary client/server protocol and a diagnostic tracing facility built on top of TCP/IP sockets. The original code, written in C++, probably has close to a man-year of time on it. I replicated both of them in C# in a couple of weeks.

Software Zen: delete this;
Fold With Us![^]

Re: Synchronous socket and WaitHandle/WaitAny confusion

Jörgen Sigvardsson28-Mar-10 19:50

Jörgen Sigvardsson

28-Mar-10 19:50

Sometimes you want to wait for other things than socket handles. It's common to have EventWaitHandles for signalling conditions to threads. If a thread needs to monitor both sockets and events, then one must find a way to do it the "C++ way". Still looking. Frown | :(

--
Kein Mitleid Für Die Mehrheit

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.