|
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
|
|
|
|
|
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
|
|
|
|
|
GOT IT!!!!! Thank you all for your input. The trick is to set the DialogResult to None in properties.
Also, I sure hope you all work out this smal argument. 
|
|
|
|
|
Excellent.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
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
I'm not yet studying c# so you may conclude I'm beginner 
|
|
|
|
|
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.
|
|
|
|
|
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 />
}<br />
<br />
else if(txt1.Text != null)<br />
{<br />
}
|
|
|
|
|
_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
only two letters away from being an asset
|
|
|
|
|
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...
|
|
|
|
|
Beginners, yes. However, by your own admission you do not even know the language. You can't comment on things you don't know!!
only two letters away from being an asset
|
|
|
|
|
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...
|
|
|
|
|
|
Very simple... Both, I know c# but I'm not yet studying it at school. Or is that too difficult for you to umderstand?
|
|
|
|
|
I'm still waiting for your explanation.
only two letters away from being an asset
|
|
|
|
|
I'm not online all day long 
|
|
|
|
|
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.
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
|
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..
|
|
|
|
|
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.
|
|
|
|
|
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...
|
|
|
|
|
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
}
}
|
|
|
|
|
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.
|
|
|
|
|
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.
--
Kein Mitleid Für Die Mehrheit
|
|
|
|
|
Hello all!This is my first post here.
I'm comp.engineering student making a project for company having about 1600 PCs, my task in this software is to collect client PC hardware info and then send it to server,compare ,then to database.
I have already made a console application which extracts hardware info through c# . Now I'm making a GUI based app which would be running on server.
Well I'm thinking of asynchronous sockets for accepting incoming connections would that be OK ?
Also how should i enclose the info from client and send it to server where it is compared to data from SQL server and then committed if relevant . Is XML used for this purpose ?
And yeah also the company people say that need a feature on server that would allow the server to pick this hardware info from any client(s) at that particular instant . Would that require a listener on client side as well ? as i plan to disconnect client as soon it sends the relevant data ?
I'm sorry for my noobish questions as I'm new to this type of software as i have been bit more on hardware side Thanks in advance !
*EDIT* i forgot important thing! and that is the software would not be connected to internet in anycase! whole thing is on the network
modified on Monday, October 26, 2009 3:16 PM
|
|
|
|