Prevent focus change from textbox

Question

1.00/5 (1 vote)

See more:

, +

I have a textbox and a datagridview with some results. I am looking for a way in which if the user is typing something in the textbox and in between, he uses his mouse and clicks on the datagridview, the focus should not leave the textbox means it should stay in the textbox. Now, the evil part of the problem is datagridview also has a cellcontentdoubleclickevent which I want to behave normally. This means that the cursor should be in textbox and if the user double clicks on the cell of datagridview, it can execute.

What I have tried:

C#

private void dataGridView1_CellContentDoubleClick(object sender, DataGridViewCellEventArgs e)
      {
          if (dataGridView1.Rows.Count > 0) // datagridview must
                                               // have anything
          {
              dataGridView1.Visible = false;
              textBox4.Text =
              dataGridView1.SelectedRows[0].Cells[1].Value.ToString();
              dataView.RowFilter = null; // resets the filter to
                                         // its starting state
              sale_purchase_datagridview1.Focus();
          }
      }

Posted 25-Oct-23 1:38am

Ankit Goel

Updated 6-Nov-23 4:03am

Deeksha Shenoy

v2

Add a Solution

Comments

PIEBALDconsult 25-Oct-23 10:05am

Maybe re-think your life choices.

Ankit Goel 25-Oct-23 10:08am

That's exactly what i was waiting for . A nonsense comment. thanks

PIEBALDconsult 25-Oct-23 14:49pm

Glad to be of service.

Member 15627495 25-Oct-23 11:49am

you have to catch the event click and the tab option of your componants.

because those two are access to interact and get focus on your componants.

on a first time, you will filter { is the click or focus is on textbox, or datagrid }
then re-focus to the texbox, or keep the focus on the datagrid.

look close at Form event for click, you have a global case dedicated.

[no name] 25-Oct-23 14:51pm

That's a "mode"; and users have to be able to "escape" a mode ... without smashing the keyboard.

Maciej Los 4-Nov-23 14:40pm

Why? This functionality seems to be unfriendly to the UI.

1 solution

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)

CHill60 · Answer 1 · 2023-11-08T02:27:00

Quote:
That's exactly what i was waiting for . A nonsense comment. thanks

Not really nonsense though is it?

As Maciej says in his comment, it's "unfriendly to the UI" and Gerry says "without smashing the keyboard". At the very least it's counter-intuitive behaviours from your UI.

Try to see it from a Users perspective - I'm typing away but will suddenly double-click something else (i.e. remove my hand from the keyboard to grasp my mouse), then what? Carry on typing in the original text box?

What if I started typing in the textbox but it's now the EOD and I want to leave the program entirely. Can't because I'm still stuck in that text box.

It sounds like you need to do something in the Validate event for the text box, but watch out for that last scenario - not insurmountable see Allow Form to close when invalid data is present[^]