[aspetner]

Another thing to note: this issue also occurs in a tab that has no query pane at all (e.g. when opening a table in a tab). When switching to that tab, the active cell does not have focus, even though there is (seemingly) nothing else that has focus.

[aspetner]

Yes. But also the same thing for when switching out to another external application and back.

Either way, I think my other idea that the currently selected cell have a different colored border when the query tab has focus would also be good so it is clear when the cell actually has focus.

[aspetner]

Well then, can this be a feature request that in-app or in-tab focus should stay in the pane that last had focus? When I am in middle of working, I don’t want the in-application focus to change just because I had to switch tabs or applications to check something. Often I have to tab between different windows to reference data. Or sometimes I need to email results of certain queries. I copy a cell, paste it into my email, then go back to copy another cell. 

 

Additionally, if I switch focus back to SQLyog by clicking on an actual cell (as opposed to alt-tab or clicking the query pane), then the focus should definitely go to that cell. I should not have to click the cell twice, once to give focus to the app and once to give focus to the cell.

 

Alternatively, can there be some sort of indicator (e.g. the cell highlight color can change) that the cell does not actually have focus? Right now, when focus goes back to the query pane, the cell has the same black border as when it has the focus, which causes me to think that the cell actually has focus and I end up thinking that I am copying something that I am not. Maybe when the result grid loses focus the selected cell border should turn gray?

 

Thanks

Aaron

[aspetner]

This has been partially fixed. SQLyog now capitalizes and highlights these functions, but they still do not autocomplete.

[aspetner]

I personally would like it for all connections, although I can see some users potentially wanting it to be per-connection.

[aspetner]

Just to be clear: my suggestion was to eliminate the need to save each tab as an individual .SQL file (it should still be an option), but rather to treat the entire session as a single “workspace” so that I can close SQLyog with 10 new tabs and not have to save 10 individual files. Is this a part of the next feature?

As for a crash, I was referring to a system crash. However, while I like the fact that you consider an application crash an unacceptable bug, they still may pop up on occasion and as such, it's good to have a contingency plan 🙂

[aspetner]

Sorry I never responded because I didn't realize that I needed to manually check the “follow this topic” checkbox – so I never received your response. I have not experienced this issue since, so I would assume that it has been resolved.

[Author]

Posts