Comments
Sort by recent activity
There will be differences of opinion, which I understand. But, it would seem to me that you do not want suggestions in a comment section - we're typing verbage to describe the code to make it easier to understand what the SQL Object actually does and how; not trying to type literal SQL code. The idea of a whole select statement in the description is overkill; Pseudo-code is more realistic or even a Technical Specification Document. But, this is a debate that doesn't belong here.
My main point is that if I'm spending a good deal of money on a software product to make my programming easier, I do not want to have to Hot-Key or click-here-and-there just to make the software stop doing something and then click-here-and-there to make it work again; this software was supposed to make my job easier. I don't want to stop in mid thought and focus to turn off and then back on an ability for the software to do its job; that's counterproductive. / comments
There will be differences of opinion, which I understand. But, it would seem to me that you do not want suggestions in a comment section - we're typing verbage to describe the code to make it easi...
The Hot Key idea would work, but this program is so smart, I would hope it could tell it was between /* */ or after a -- on a line and stop suggesting. I don't recall this issue with version 2; I only remember it capitalizing key words as I typed within a comments section, which I generally wanted it to do most of the time anyway. / comments
The Hot Key idea would work, but this program is so smart, I would hope it could tell it was between /* */ or after a -- on a line and stop suggesting. I don't recall this issue with version 2; I ...