How can we help you today? How can we help you today?

Must become less intrusive

I think that the problem I am having with the tool in general is when I am not using it, it becomes a real annoyance, and none of the activation keys can be used in normal coding.

The window popping up isn't an annoyance, I really like it, but, it should take a keystroke of some sort to activate my usage of the stuff in the dropdown. I think a down arrow would be fine, and possibly using esc to escape out of the window, but one way or another, the stuff that intellisense gives you should be available if desired, not in the way. You have to figure that your guess will be useful almost never when a person starts typing, and if I hit:

A <tab>

It is probably unlikely that I want to alter cube using a macro. I was typing Create table A to answer a question in the MSDN forums at the time :)
drsql
0

Comments

6 comments

  • emails4me
    Yep, second that.

    I kinda like the way it works with Query Analyzer : it only appears when I invoke it. In Management studio, I often find I'm hitting the esc key to get it out of the way when I know what I want to type.

    emails4me
    emails4me
    0
  • Sylvain Lafontaine
    Yeah, I second that too.

    We should have the option to specify on which conditions the intellisense should popup automatically.
    Sylvain Lafontaine
    0
  • drsql
    I don't mind it popping up, or even guessing what thing I might want to use. The problem is that if I don't use it, it shouldn't get in my way. So far it seems very fast, my only real interface usability issue is that it gets in the way when I don't need it, and it should be benign, requiring me to make use of what it is doing.
    drsql
    0
  • Tilman
    Hi,

    Thanks for all the comments. I'll try and answer them all.
    The window popping up isn't an annoyance, I really like it, but, it should take a keystroke of some sort to activate my usage of the stuff in the dropdown. I think a down arrow would be fine

    This has been suggested before. Personally, i don't think it should work that way, but i suppose we could make it an option.
    using esc to escape out of the window

    It should be doing that at the moment.
    I kinda like the way it works with Query Analyzer : it only appears when I invoke it. In Management studio, I often find I'm hitting the esc key to get it out of the way when I know what I want to type.

    You can turn off the auto-popup in Management Studio on the options dialog. Eventually Query Analyzer will have the auto-popup (and the option to turn it off), aswell.
    We should have the option to specify on which conditions the intellisense should popup automatically.

    I'm afraid this is probably too difficult to do.

    Regards,

    Tilman
    Tilman
    0
  • amachanic
    I agree, it needs some work in this area. I've already filed a suggestion that I think would fix most of the issues: just don't auto-select a candidate by default. That way if the user keeps typing and does not select something, the intellisense will just get out of the way...
    amachanic
    0
  • CWuestefeld
    I have to disagree. I'm working in Query Agonizer, where it doesn't pop up at all.

    I'm not a DBA; most of my work is in .Net code, but I do a ton of DB work as well. I'm used to the way VS.Net's intellisense pops up, which is intrusive. Like it or not, this is the mode that most users like me will be used to.
    CWuestefeld
    0

Add comment

Please sign in to leave a comment.