Next Data field edit with Tab key

Hello to the communitiy.

Sorry, for the maybe dump question: I work with HeidiSQL since about 10 years. Now I have it installed at my new PC. Earlier it was able to go to the next data field with the tab key and edit this field. Now at the new installation I have to double click, to edit the next field. I have searched, but found no Option for this.

This is an issue in v11, not sure what I did to break it. However, you can star issue #937

Thanks for repley

I this new behavor an Error or new "Feature"?

Will this be fixed?

I also have this problem and miss this functionality very hard. Is there a fix?

version 12.3.0.6654 and the problem persists still

No problems here, neither with 12.3.0.6654 nor 12.3.0.6589.

Still an issue on 12.3.0.6655

Let me guess, you all have nvidia VGA?

Radeon RX 570 here and not working. Not working on a laptop with Nvidia as well

Maybe the same Error again in the new Versions?

I have some time ago updated to version 11.1.0.6116 and here HeidiSQL stays in Edit Mode.

I get a noticable screen update when trying to tab to the next column. Its as if some other process is attempting to update the display of the subesquent table entries. Curiously, you'll see that the 'update' extends beyond the field definition area as I try to tab from a table field in the lower part of the screen.

Hi folks,

I have seen this behaviour after upgrading from 12.0.0.6468 to 12.3.0.6589. The same version Rikai.Design used and he failed also but TTSneko had no issues. Strange. Ansgar mentioned, this is an issue of v11 but as v12.0 worked for me and 12.3 not, there might be a new regression or any side effect caused by ... OS? By the way, I used HeidiSQL on HP Notebook with up-to-date Windows 10 and nVidia Quadro P600. Downgrading to 12.0.0.6468 solved the issue on the HP Notebook.

A quick Test on a Lenovo Notebook with W10 and nVidia Gforce RTX 2060 showed the same problem with 12.1.0.6537. Upgrading to 12.3.0.6589, same problem. Downgrading to 12.0.0.6468 and the problem was solved.

In short words, at least for me it looks like a regression between 12.0.0.6468 and 12.1.0.6537. I did not check any nightly.

Hopefully, this helps to discover the issue.

Thanks for this incredible piece of software, I (not only) should really think about donating.