distal-attribute
distal-attribute
distal-attribute
distal-attribute

First tab closing without warning when double-clicking

User, date Message
Written by kthanid
3 years ago
Category: General
15 posts since Mon, 30 Jan 12
When double-clicking on whatever the first query tab is (whether that's an open file or otherwise) seems to irrevocably close that tab and replace it with a fresh query tab.

The same behavior in any tab past the first results correctly in a warning about unsaved changes (if any) rather than closing outright.

This is somewhat problematic since it is inconsistent behavior between tabs and makes it a little too easy to accidentally lose unsaved work.

Is there any known setting that addresses this behavior? Thanks.
Written by ansgar
3 years ago
4988 posts since Fri, 07 Apr 06
Ever heard of "Undo" / Ctrl+Z ?
Written by kthanid
3 years ago
15 posts since Mon, 30 Jan 12
While I'd love to reply to your comment with a similarly curt and rhetorical response, let me instead just simply state: Thank you for the functioning workaround.

Yes, I've heard of "Undo", however I do not feel that using "Undo" is a particularly intuitive response to accidentally closing a file without saving your work (yes, having tested it just now it does seem to work - assuming you click back into the Query editor window first) as I cannot think of another widely used application where such undo behavior (recovering a lost file) would be an expected result of pressing Ctrl-Z.

To be clear, I hadn't thought to try and "undo" a lost file, nor would I expect doing so to be an intuitive response from most end users.

Additionally, this still does not address the underlying concern that the behavior between tabs is inconsistent. Double-clicking on any tab other than the first results in a warning if unsaved work is present (and no warning if all work is saved). Users typically expect similar aspects of a piece of software to function consistently (meaning if they hadn't noticed the little asterisk indicating unsaved work and were quickly closing tabs, they may assume that all work was saved when they have closed all tabs, which may not be the case if modified work exists on the first tab).

TL;DR - Tabs should behave consistently. I appreciate your help with a functioning workaround, I still believe the issue is worth noting and addressing.
Written by ansgar
3 years ago
4988 posts since Fri, 07 Apr 06
Sorry for being a bit short, I'm good at giving hints to some obvious thing.

Think you're right - the other tabs warn you about closing a file per doubleclick, while the first tab does not - only it does not close, and that's the reason why it does not warn. I can probably check that. On the other side, why not use Ctrl+Z here - the undo-history is not reset as long as you close the whole application.
Written by kthanid
3 years ago
15 posts since Mon, 30 Jan 12
Thanks for the reply, and my apologies if my own reply seemed a bit abrasive (I didn't exactly mean to come off that way, and realized after posting that your suggestion may have been more of a polite nudge in the right direction rather than a snide rhetorical remark)...

I'm not sure I understand entirely what you mean when you say it does not "close" (but I've only been using HeidiSQL for a very short time so far, like a few hours), but at least visually it appears to (I'm assuming you mean it doesn't actually close in the technical sense).

As a quick example if it helps clarify what I mean, if I open HeidiSQL via double-clicking on a SQL file on my desktop, let's call it "test.sql", if I then make some changes and for whatever reason double-click on the "test.sql" tab (since it's the only tab) I'm left looking at a blank query window titled "Query" (which gives the appearance of my sql file having "closed").

I will certainly use undo for now (and I'm glad to have been informed of the ability to do so). Thank you very much for your help.

I also feel it worth noting that I ran into HeidiSQL while looking for a solid alternative to MySQL Workbench/Query Browser (the former being an application I've grown to mostly despise, the latter being functional but obviously a bit out of date and with annoying functionality I'd rather avoid).

Between the alternatives I've tried so far, HedidSQL is my preferred choice. Receiving such a quick response here further solidifies my feeling that this is probably an application I want to spend some time getting to know.

Thanks again for your help.
 

Please login to leave a reply, or register at first.