Comments
Sort by recent activity
I definitely unlinked and relinked, but I don't think I committed in between. I've tested it again and I can't replicate exactly what I was experiencing so I think it may have been a temporary wonk. However when testing it I found that (without unlinking) a change is detected on the static data file, but it doesn't pick up the new column name and wants to replace all values in the old (no longer existent) column with NULLs. I think that's part of an existing problem WRT how Source Control deals with renames (and indeed whether it can detect them as renames at all), but the steps you've outlined above definitely suffice in getting the static data file back into shape — I'd forgotten that an unlink actually generates an entry in the next commit to delete the file, so now I've got that straight in my head I should remember for the future. Thanks! / comments
I definitely unlinked and relinked, but I don't think I committed in between. I've tested it again and I can't replicate exactly what I was experiencing so I think it may have been a temporary wonk...
Ah, I thought it was probably something like that; I was fairly sure it disappeared around the time of SSMS 17. Thanks for looking into it! / comments
Ah, I thought it was probably something like that; I was fairly sure it disappeared around the time of SSMS 17. Thanks for looking into it!
Hi Alex Thanks for getting back to me! It was a feature of the product previously rather than something I added myself. The shortcut was Ctrl-Alt-D. I assume that it must have had an exposed command with a shortcut for it automatically created under Environment > Keyboard (like SQL Prompt uses) back then. Nice idea on the toolbar commands, but as you say it doesn't work without the toolbar showing. It's not a huge issue though to be honest, I just figured that the code that did it might have been accidentally commented out or something one release [image] / comments
Hi AlexThanks for getting back to me! It was a feature of the product previously rather than something I added myself. The shortcut was Ctrl-Alt-D. I assume that it must have had an exposed command...
I'd like to add my voice to this — the few seconds you lose each time it happens do add up. Been driving me up the wall for years, it's so annoying to have your productivity tool get in the way of your workflow. The SQL Prompt tooltip appears to work in the opposite way to Microsoft's tooltips, appearing to the left of the cursor instead of the right, so I think the vast majority of instances of this happening could be sorted by just changing the tooltip to appear on the right of the cursor (as SQL is coded LTR, so even if you don't add something to specifically handle display edges the issue would then only occur on an extremely long line that had reached the right-hand side of the display, assuming a maximised/fullscreen SSMS window). Any way you could add a note suggesting this, to at least get just the directionality fixed in the near future (I'd hope it'd be a one-line change) and leave fixing the multiple-displays issue on the backlog? / comments
I'd like to add my voice to this — the few seconds you lose each time it happens do add up. Been driving me up the wall for years, it's so annoying to have your productivity tool get in the way of ...