Create an option to position the intellisense parameter info top or bottom.

[rhyek]

Currently the parameter info tooltip is always placed above the cursor. This is often quite annoying since it completely blocks code in the above lines and you sometimes need to look at your context to know what values to give the parameters.

Example:

[znorman-harris]

Here's a great use case for exactly why this would be beneficial: My company has a commercial programming language that we sell which is complete with documentation for all of our routines. The routines can have a lot of documentation containing multiple examples (like you would expect from some open source projects as well) and sometimes is very lengthy (>100 lines). I was trying to use this documentation as hover help, but it is just way too much.

I almost think you need one of a few things to add more options for hover help:

1. Have docs show up in designated area
2. And/or allow a user to open up documentation in a separate pane/tab within VSCode. That way you could quite literally have a one-stop editor with your code and information rich documentation all in the same place
3. Maybe an ability to separate hover help content into tabs (i.e. by examples, arguments, keywords, classes, etc)

[jsolbrig]

Seriously, how is this not fixed yet? This issue is three years old in 5 days.

Parameter hints get in the way of the function call that you're trying to write if you're formatting things correctly (i.e. not putting everything on the same long line). The way that I work, parameter hints are basically unusable and I'll be turning them off even though I would like to have them.

[yvvt0379]

The dev team has forgotten this issue?

[stedben]

Eh, I don't believe the dev team has forgotten this issue, per se, it's just that the people in this multi-year thread don't constitute enough of a percentage of the general user base to warrant any action.

We can get huffy, but the 42 of us in this thread will never amount to a hill of beans when it comes to the workload of the Super-Professional MicroSoft Super-Coders who have a hand in the development of the end product: Super VS Code. It would be trivial to offer us a shockingly-simple solution, but these MicroSoft Super Engineers have a job to do. And a Job to keep.

I think we should never forget that MicroSoft is a for-profit company, and a SEVERAL! frustrated users will never sway the Power-That-Is to make a MicroScopic change.

I stay in this thread to remind myself that monolithic companies have Job #1, and the rest of us just get to use the product.

[NicolasGoeddel]

We can get huffy, but the 42 of us in this thread will never amount to a hill of beans [...]

In fact there are 190 people liking the initial post, 99 subcribers and 155 comments. That's not a minority in my opinion.

[one-jones]

please please please - this window drives me crazy

[Fred-Vatin]

please please please - this window drives me crazy

Turn it off and create a shortcut to call it if needed. There is an extension to place it in the sidebar along the files.

[nahuel]

@freMea what's the name of the extension?

[Fred-Vatin]

@freMea what's the name of the extension?

Docs View

[Fred-Vatin]

Does disabling this option help ? I will reenable tooltip and test it for the next days.

[Fred-Vatin]

How this issue is different from #30797 ?

It seems commenters complains about the same thing in both.

[Fred-Vatin]

This is still driving me crazy.

Can not read my code above.

Solution from @swilkewitz works for me.

That plus switching to a shortcut to get parameter hints should make things a lot nicer for most people: "editor.parameterHints.enabled": false

I think the shortcut is ctrl + shift+ space by default. The shortcut id is editor.action.triggerParameterHints

So I disabled the parameter hints and calls it when I need it with Ctrl + shift + space and get rid of it with escape if needed.

[sandipchitale]

See: Signatures View

[exse2]

"editor.parameterHints.above": false,

when?

Or just let it react on

"editor.hover.above": false,

To quote a redditor from 3 years ago: "If you scroll down so the line you're working on is at the very top, the tooltip DOES appear below the line, but of course you still can't see the line above it! So it is possible, just needs a boolean/tickbox "always show below""

[Hezakai]

"Working as intended" /thread

[dillydadally]

All I want is to be able to move the entire tooltip popup into a panel. Bonus points if there's an option to make the panel update on mouse hover rather than just cursor position.

I've tried both the Docs View and Signature View extensions. While I'm grateful for them, they both lack the following:

• an option to update on mouse hover rather than just cursor position.
• the code highlighting/coloring that the tooltip has.
• most importantly, error information like the tooltip has.

This is probably the biggest issue with VSCode for me. Is it really that hard to move a tooltip window into a panel instead? I feel like this should have been how it was done to begin with. A popup covering your code on every single token is kind of crazy.

[znorman-harris]

@dillydadally I have been playing around with this for my extension and I ended up using notebooks because they apply your theme colors to rendered markdown (for code blocks with non-standard languages). This is a substitute for not having a dedicated panel and isn't great, but is better than nothing.

It would be nice if we could have something similar to "open in editor" or something like that.

Here's what I have using notebooks as a workaround:

[starball5]

Related on Stack Overflow: VS Code intellisense in the way

[rpm5099]

I don't understand the pushback to addressing this issue. The logic that seems to be - only a total of 217 users seem to think the inability to move parameter/intellisense popup placement is an issue, so it can't be that big of an issue. This is wrong and insulting to those who took the time to bring attention to the problem. The number of users who hate this feature of VSCode, or lack thereof, has to number in the millions. In fact I'm guessing that many people struggle with this issue for about 10 minutes and then just permanently turn off those features and fail to get the benefit of them at all.

[beresfords-referrals]

It's a lot more than 217 - there are various issues logged requesting much the same thing in different ways. A whole slew of issues could be closed by actioning this . Pretty Please ;-)

33752 - open 6 plus years

15667

149270

95784

30797

to shout out just a few

[starball5]

@beresfords-referrals your #1 is a circular link to this issue ticket. Your #2 is about hovers, but my understanding is that this issue ticket is about parameter hints. Same with #5, which is about hovers and already resolved. Your #3 and #4 and different requests- for a dedicated panel or view, which are already resolvable via extensions.

[beresfords-referrals]

You are totally right. This is computers and there are always 10 solutions to every problem in the computer world. The point is there is one problem, which is the hints keep getting in the way.

[ilmatic]

I don't understand the pushback to addressing this issue. The logic that seems to be - only a total of 217 users seem to think the inability to move parameter/intellisense popup placement is an issue, so it can't be that big of an issue. This is wrong and insulting to those who took the time to bring attention to the problem. The number of users who hate this feature of VSCode, or lack thereof, has to number in the millions. In fact I'm guessing that many people struggle with this issue for about 10 minutes and then just permanently turn off those features and fail to get the benefit of them at all.

💯

Literally found this trying to disable intellisense. It's something I deal with every single day that I code. I start calling a function and 2-3 characters in I have no clue what I'm typing cuz there's a massive intellisense popup in the way. It's been a drip drip drip water torture for years. So disappointing to find that y'all have aware of this issue since 2017 and it's still open.

[surfingdoggo]

It's been a drip drip drip water torture for years.

THIS! I finally was in an impatient enough mood just now to get distracted enough by it blocking my code to look up what it was even called to try to find a solution 😿

I did find

• this issue to make it transparent, which doesn't help much, but these settings at least give it some color to make me happy along with irritated at the same time (click the color box to change opacity):

  "workbench.colorCustomizations": {
      "editorSuggestWidget.background": "#124da770",
      "editorInlayHint.parameterBackground": "#ff0000",
      "editorHoverWidget.background":  "#00ccff6c",
      "editorHoverWidget.foreground": "#00ff226b",
      "editorHoverWidget.border": "#3700ff",
  }   

• a comment from a blessed saint saying the following:

  
  "editor.parameterHints.enabled": false,

ctrl + shift+ space brings it up when needed

* [Docs View](https://marketplace.visualstudio.com/items?itemName=bierner.docs-view) which was [created by a Vscode team member supposedly](https://stackoverflow.com/questions/70955635/how-to-change-reference-popup-tab-position-in-vs-code) that brings up another popup on the side.

> So disappointing to find that y'all have aware of this issue since 2017 and it's still open.

Frlz. I wonder how hard it is to make a plugin myself.

[rpm5099]

I don't understand the pushback to addressing this issue. The logic that seems to be - only a total of 217 users seem to think the inability to move parameter/intellisense popup placement is an issue, so it can't be that big of an issue. This is wrong and insulting to those who took the time to bring attention to the problem. The number of users who hate this feature of VSCode, or lack thereof, has to number in the millions. In fact I'm guessing that many people struggle with this issue for about 10 minutes and then just permanently turn off those features and fail to get the benefit of them at all.

@starball5 - you gave this statement a thumbs down, can you please elaborate and explain why?

[starball5]

@rpm5099 I don't think the logic in your last sentence is necessarily wrong. That guess may very well be fairly accurate. But I thought it was unnecessary to paint the maintainers' comments here as "wrong and insulting". What I see is a maintainer soliciting design discussion. I can just barely categorize it as "pushback", and the issue ticket was reopened after being closed. VS Code has tons of users and tons of feature-requests. Microsoft can do whatever they want and they don't need to listen. But to a large extent, they do. And with the huge backlog of feature-requests, they need a way to prioritize (and they look at the number of thumbs up reactions). It leaves a bad taste in my mouth when I read comments that give off the vibe of complaining. I rather like seeing comments that weigh in on design questions, or just not seeing comments at all.

[Raydir]

hey there Just stumbled over this issue here. I do have several snippets in my language extension with long names (sadly) and long descriptions about the params of those snippets.

For me a parameter to let the snippet-preview be fixed at the bottom of the suggestionpanel would be just splendid...

atm the panel opens every now and then like this:

If we could have a setting to fix the position at the bottom it would show the complete infobox without problems:

[kmarmet]

@freMea what's the name of the extension?

Docs View

THANK YOU!!!!! IT HAS BEEN DRIVING ME ABSOLUTEY INSANE!!!!

[Hanibachi]

i can't believe this issue still exists since 2017!!!! like what the actual hell LMAO

[Ian-T-Price]

How about adding an option to place it in the side bar menu as an accordian? It's easy to observe on the side or close it up if people don't want to be distracted by it

[saminton]

How about adding an option to place it in the side bar menu as an accordian? It's easy to observe on the side or close it up if people don't want to be distracted by it

That's actually what I've been using for a while now, using this extension -> https://marketplace.visualstudio.com/items?itemName=bierner.docs-view

[CodingMarkus]

i can't believe this issue still exists since 2017!!!! like what the actual hell LMAO

This problem is a very good example of what often goes wrong with large, popular projects. Their maintainers think it's more important to implement a super complicated, 5000 line feature that they think is super cool and that will keep them busy for 3 months before it works reasonably reliably, but that nobody ever asked for and that very few people will ever really need, than to fix an open feature request that's been open for over 6+ years and that hundreds of people have asked for and that's probably a 50 line fix and get it done in a single day. After all, why implement the things people care about when you can implement the things nobody cares about?