#3004 Code completion pops up when HeidiSQL is activated without main form focused

[Anonymous]

Originally created by: woutervannifterick

When you have the session manager active, and you switch to another application to search for a password for example, heidiSQL sometimes crashes (A/V) when you return.

What exact steps will reproduce the problem?
1. Start HeidiSQL and connect to a database;
2. Go to the query editor, and enter the following query: "select 1";
3. Press ctrl+space to invoke code completion;
4. Dismiss the code completion list by clicking somewhere in the editor;
5. Either stay in the query tab, or go to the data view.
5. Open the session manager, and leave it open without connecting;
6. Switch to another application (alt+tab);
7. Switch back to HeidiSQL

What was the expected output?

Session manager active, everything as it was before we left.

What happened instead?

Suddenly the code completion list shows up, even when you're not in the query tab. It's focused and drawn over the session manager form.

In normal situations you can just dismiss it with ESC or by clicking on the session manager, so then it's just a cosmetic issue.

However, in certain situations you enter a loop of access violations, because every time you dismiss the eurekalog form you activate HeidiSQL, which is where the problem seems to be triggered. Sometimes that means the only way to get out is by restarting HeidiSQL, losing all querytab texts.

Unfortunately I couldn't really reproduce these a/v's, but I get this problem regularly (since a long long time ago.. just never bothered to report it yet, sorry about that).

Suggested fix (optional)?

Perhaps check if a SQL editor is active (query tab, stored procedure or view editor) before actually popping up?

Version used?
HeidiSQL revision: Must be the latest build for reporting issues. If not,
the report will be ignored!
MySQL Server version:
Operating system:

[Anonymous]

Originally posted by: a...@anse.de

See issue #2640

Mergedinto: 2640
Status: Duplicate

[Anonymous]

Originally posted by: woutervannifterick

Yeah, that's the same issue!