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:

[yume-chan]

In Visual Studio, hold Ctrl for a while, the tooltip will dim down to let me see through it.

I think it's better than changing the position via a config.

[rhyek]

Thanks. I never need it to be above the cursor. Pressing ctrl every time sounds unnecessary.

[rhyek]

I seriously have to hit Esc every time this tooltip pops up. It is probably the most annoying thing to me about VSC.

Do you know if there is a way a plugin could fix this?

[joaomoreno]

The problem with positioning it down is what happens to Intellisense? Should it then go up?

The Ctrl idea is something that we've brought up every now and then, we should just implement it.

@rhyek Most people how are annoyed by it simply disable it.

[rhyek]

I have never seen an instance where both tool tips are shown at the same time. Once you pick a method from intellisense, it is hidden and parameter info appears.

…

On Sep 22, 2017 4:17 AM, "João Moreno" ***@***.***> wrote: The problem with positioning it down is what happens to Intellisense? Should it then go up? The Ctrl idea is something that we've brought up every now and then, we should just implement it. @rhyek <https://github.com/rhyek> Most people how are annoyed by it simply disable it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33752 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAq5yryjXGI6krrtllRWSogjqHsXt06Wks5sk4ksgaJpZM4PLPTK> .

[joaomoreno]

When parameter hints is open, simply trigger Ctrl Space.

[vscodebot]

This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.

[rhyek]

Seriously? On Oct 2, 2017 1:52 AM, "vscodebot[bot]" <[email protected]> wrote: Closed #33752 <#33752>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#33752 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAq5ylAgUCpPbqYYPVunkcQHfw2xz3sWks5soJYfgaJpZM4PLPTK> .

[rhyek]

Can this please be re opened? It had activity 7 days ago and I'm not sure what additional information is needed. Probably just and over eager configuration on the bot.

[joaomoreno]

The issue was closed because you didn't reply to my last message:

When parameter hints is open, simply trigger Ctrl Space.

You also didn't address my point about disabling. Why don't you simply disable parameter hints?

Ultimately, you can imagine the solution isn't as simple as changing the positioning; no matter where it will be positioned, it will overlay text. You happen to give more importance to the text above the cursor; others to the text below it. And text isn't even the biggest problem. It's other widgets, as I already mentioned above.

[rhyek]

@joaomoreno, sorry. I addressed the ctrl suggestion earlier.

You also didn't address my point about disabling. Why don't you simply disable parameter hints?

I don't want to disable them, because they are useful to me sometimes.

no matter where it will be positioned, it will overlay text. You happen to give more importance to the text above the cursor; others to the text below it.

Yes, but the IntelliSense tooltip shows below the cursor by default and this is very common among code editors and IDEs with code hinting capabilities. Why should the parameter info tooltip be different?

I am asking for an OPTION to modify its placement, not to place it below for everyone.

The reason for my preferring the tooltip to be below is:

• IntelliSense is already shown below
• You write code from top to bottom. You don't want a huge tooltip covering up your context. The most useful context that will help you keep track of what you are doing is probably going to be correlated by the order of execution of your program (usually top to bottom).
• Some examples of what context I mean:
  • What was the name of the variable I needed to pass as a parameter here?
  • If I am writing my parameters in a multiline format, I want to look at what parameters I already gave.
  • What method am I calling on what object?
  • Where am I at currently?

[rhyek]

In the image I gave as an example, the tooltip completely covers up three previous lines of code. It often feels like I'm writing code blind when this happens.

[chriseppstein]

As I suggested in issue #35596, other possible UI solutions exist other than anchored to the text.

Other possible config options or solutions might be to have the pop up displayed in a fixed location when triggered by typing (E.g. the upper right corner of the editor window) because sometimes I need to refer to the code below as well :)

or you could even imagine a documentation pane that can display contextual documentation without any overlay at all, such a thing could take precedence vs the overlay, if open.

[cantiero]

This is also an issue for me. My impression is:

1. I don't need to see parameter hints all the time. (Does anyone do?)
2. If showing all the time, anywhere you show will be invasive and distracting. (Unless you put in the footer of the editor, maybe?)
3. Why not just allow users to disable them and have a keyboard shortcut to show a hint only when needed? In that case, it wont matter if it is above or bellow.

[jprichardson]

This is an issue for me. Just recently started experimenting with VSCode from Atom. While I really enjoy using VSCode, this annoys the heck out of me as it covers all the code above and doesn't feel consistent with the method intellisense. I'd love to see an option to place this below the current line. Thanks for your hard work!

[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 which was created by a Vscode team member supposedly 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?

[l0hn]

This problem is so annoying that I've been considering going through the pain of switching to nvim.

For now I have used the "be5invis.vscode-custom-css" extension to load a css file to override the position of the parameter hints popup:

Before:

After:

It's not a nice solution but at least the popup is no longer directly on-top of the code I'm trying to write.

Link to the extension for anyone else that's suffering with this daily: https://marketplace.visualstudio.com/items?itemName=be5invis.vscode-custom-css

Css Used:

.parameter-hints-widget>.phwrapper {
    max-width: 100% !important;
    width: 100% !important;
}

.parameter-hints-widget {
    position: fixed !important;
    border-width: 2px !important;
    border-radius: 12px !important;
    padding: 10px !important;
    width: 70% !important;
    top: unset !important;
    bottom: 0px !important;
    margin-bottom: 40px !important;
    border-color: rgb(144, 104, 176) !important;
    background-color: rgb(43, 43, 43) !important;
    left: 15% !important;
}

[rpm5099]

Wow, a totally separate extension to fix a bug/deficiency in another extension that has had an open issue for 7 years with 200+ comments from 100+ users.

[SonicZentropy]

Thanks l0hn for doing what the entirety of Microsoft couldn't manage in 7+ years! This workaround is fantastic

[rpm5099]

This problem is so annoying that I've been considering going through the pain of switching to nvim.

For now I have used the "be5invis.vscode-custom-css" extension to load a css file to override the position of the parameter hints popup:

Before:

### After: It's not a nice solution but at least the popup is no longer directly on-top of the code I'm trying to write.

Link to the extension for anyone else that's suffering with this daily: https://marketplace.visualstudio.com/items?itemName=be5invis.vscode-custom-css

Css Used:

.parameter-hints-widget>.phwrapper {
max-width: 100% !important;
width: 100% !important;
}

.parameter-hints-widget {
position: fixed !important;
border-width: 2px !important;
border-radius: 12px !important;
padding: 10px !important;
width: 70% !important;
top: unset !important;
bottom: 0px !important;
margin-bottom: 40px !important;
border-color: rgb(144, 104, 176) !important;
background-color: rgb(43, 43, 43) !important;
left: 15% !important;
}

This is great, but is there any way to move the window away from the cursor so it's not blocking code I am trying to look at? Now it just blocks whatever is below the cursor. This would be a reasonable compromise for a smartphone screen.

[l0hn]

@rpm5099 The workaround is definitely far from ideal, it has to be reloaded whenever vscode updates and will break if the class names change in the future.

Personally I would like it to show below the line being edited, or docked in a panel, or well.. just anywhere except ontop of what I'm trying to read. I expect you could set the position in relation to the curser using JS.

I'm not sure why there's a reluctance to fix this for people.