Bug in split view

• 
  Thanks Eric, and sorry this is causing you issues. We've had awful problems trying to support split windows in SQL Server Management Studio. Just stopping SQL Prompt from chucking exceptions was hard enough due to the way the split window is architected, however I will raise this as an issue and see if we can improve the situation further. For now though, I'd definitely recommend steering clear of the split window view when using SQL Prompt if at all possible.
  
  
  Many thanks,
  Bart

  Bart Read December 22, 2006 08:56

  - 0 +
• 
  Thanks for replying so quickly.
  
  A workaround I am using is to deactivate SQL Prompt when working in split view (I absolutely need split view sometimes). This brought a simple thought: the enable/disable could possibly be available in the toolbar which is easier to access than the menu (if you have access to adding your stuff in the toolbar of SSMS).
  
  BTW, possibly because I haven't become familiar enough, I always prompt SQL Prompt manually with Ctr-space. The default Enter configuration was driving me mad because it was inserting stuff all the time when I was simply trying to format my code. Using Ctr-Space does not bother me but I am curious of the default behavior: what am I missing? How can we use Enter normally (I tried shift-enter and other variations but the auto-complete was always triggered)?
  
  Thanks,
  
  Eric

  Eric December 22, 2006 09:19

  - 0 +
• 
  Hi Eric,
  
  
  I think we probably can add items to the toolbar in SQL Server Management Studio at least, although this would obviously be much trickier in Query Analyzer. It's really just a question of how, but SSMS is basically a stripped down version of Visual Studio so all the VSIP APIs are in there, or at least most of them are; the odd bit has been hidden away so you do have to do some extra legwork to get things working.
  
  As far as the popup behaviour goes I'd say it's currently still a wee bit too aggressive, and hence your problem with ENTER, whereas sometimes it still doesn't appear quite when it should (e.g. after a '.'). The best thing I can suggest is playing around with the options on the Candidates tab in the Options dialog for Completion Keys. You could also try tweaking the popup delay: I'd suggest in your case maybe an increase to 600 - 700 milliseconds might help. This at least means you wouldn't have to hit CTRL+SPACE all the time.
  
  I think it really goes to show how different people work because I only have ENTER enabled as a default completion, and I guess I probably just hit ESC without thinking if the popup appears when I don't want it, or something anyway because I very rarely end up with things inserted at the end of the line that I don't want. On the other hand I find using SPACE or TAB as completion keys unbelievably annoying for the same reason that you dislike ENTER, whereas quite a few people like using SPACE and TAB. So I think the best thing I can suggest is have a tinker and see what works best for you: there's no harm to be done by fiddling around and you can always hit "Restore Defaults" if it all goes wrong.
  
  
  Thanks,
  Bart

  Bart Read December 22, 2006 09:42

  - 0 +

Add comment

Please sign in to leave a comment.