Prompt first before clicking a different radio button?

Question

1.00/5 (1 vote)

See more:

I have this snippet of code:

C#

if (!cboModel1.Text.Equals(string.Empty) || !cboVBrand1.Text.Equals(string.Empty) || !txtVType1.Text.Equals(string.Empty) || !cboChassis1.Text.Equals(string.Empty) || !lblPlate1.Text.Equals("### ###") || !txtVColor1.Text.Equals(string.Empty) || !cboSType1.Text.Equals(string.Empty) || !txtSPrice1.Text.Equals(string.Empty))
            {
                DialogResult change = MessageBox.Show("Discard entries and select an old vehicle?", "PROCEED?", MessageBoxButtons.YesNo);

                if (change == DialogResult.Yes)
                {
                    clearDisable_Old();
                    rdoOld.Checked = true;
                    rdoNew.Checked = false;
                }

                else
                {
                    rdoOld.Checked = false;
                    rdoNew.Checked = true;
                }
           }

I have two Radio Buttons: Old Vehicle and New Vehicle.
Initially the user has to select one of the radio buttons first before entering some data in the fields.
What I want to happen is when the user has clicked a radio button and entered some info in at least one field, when he suddenly clicks on the other radio button (suppose he changed his mind), there will be a prompt first so all the data he has entered won't be immediately cleared. What would be the event fit for this?

Posted 26-Jul-15 2:10am

kmllev

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Answer 1 · 2015-07-26T09:55:00

Solution 2

If this is Windows Forms I would use Validating[^] event since you need the ability to cancel the operation based on the user input.

The CancelEventArgs[^] has a property Cancel which can be set to true to prevent the radio button from changing it's state.

Posted 26-Jul-15 9:55am

Wendelius

Sergey Alexandrovich Kryukov · Answer 2 · 2015-07-26T06:08:00

None. That is actually one of the worst design ideas I ever heard of. But, what's about an event? First of all, it's apparent that you cannot do any handling just "before clicking", just because the "clicking" had not yet happened.

In practice, there are always some events preceding a click. For example, before you click something with the mouse you invoke the "mouse enter" event and few "mouse move" events. But the use can "click" without a mouse: the "click" event is purely functional, this is an action performed in different ways: mouse, keyboard, even programmatical one (which I would not recommend). You can handle "got focus" event (you mentioned something similar), but it's possible to "click" a control without focusing it.

More importantly, all those events cannot be used in principle, because they all may not lead to an actual click: the user can just play around with the mouse and the control focus. This possibility is the fundamental user right, you should never take it out. Say, on all changes on focus or, say, selections, you can show different information on status line, or something similar, but never anything modal; same goes about moving the mouse. Breaking this simple rule will drive the users crazy, people will never agree to use your software.

If you want some design advice, you have to formulate your ultimate goal. It should really be ultimate, that is, you should not put any events and similar technical detail in the formulation of your problem.

—SA