-
Notifications
You must be signed in to change notification settings - Fork 29.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feature-request: possibility to change the size of description popup #29126
Comments
I'd like to add that wrapping in the popup is also a problem and should be avoided (overflow should be horizontally scrollable). |
cc @Microsoft/vscode for thoughts |
It seems like the problem is that to read long descriptions, you need to scroll. One way to solve that problem without requiring intervention from the user would be to resize the popup dynamically based on the content it needs to display. If we were able to do this, we could make long descriptions more readable without requiring the user to either scroll through the description or to drag out the size of the window to make the content more readable. We currently set the height dynamically, perhaps we could also look at dynamically altering the width to accommodate larger content? While there would probably still be cases where there simply isn't enough room to show all of the content this would be the preferable solution for me since it allows most users to keep their hand on the keyboard and means that we don't need to worry about what to do with the popup after the user has resized it, then dismissed it (do we keep it at that size, even if it is way too big for the next piece of content, what happens then when the user returns to the same content that caused them to resize etc etc). I also agree that wrapping inside the popup doesn't seem like the right thing to do since it alters the readability of the content. So if resizing the width of the popup still means content is outside of the viewport, we should add a scroll bar as @mike-lischke suggests. |
The scrollbar solution is worth pursuing |
Large descriptions that usually come as part of a well documented sample code will be easy to read if we put a button to open the entire description in new tab. |
I'd love to get a possibility to "resize" this window. Prefered solution would be a setting alike "editor.SuggetionsHeigth" and "editor.SuggetionsWidth" which could be set in pixels. |
Like I said in my other issue: Please add one or more of the following:
And while we're at it:
This should be for autocompletion, intellisense and debugging popups (I'm unsure if those are the correct names for vscode). They are all too narrow, and they all wrap. It should be like in regular Visual Studio - we shouldn't have to debate it, just copy what already works. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
when the import package path is very long , the suggestion window width not fit the long length, characters are truncated!!! |
I'd like this feature too - I have to use large font size in my editor, but it makes the popup window dramatically too small in relation to the text size, rendering it ugly/useless. |
Interesting point: one of the most compelling reasons IDEs became popular was that they are aware of what you're doing - i.e. intellisense. And vscode ALREADY HAS this available (and it's very good!), it's just unusable. So right now, it's hard to say that using vscode is better than using notepad. Since intellisense is already implemented and working, I don't understand why it isn't made pretty so it becomes usable. This is a very old issue, and affects everyone. |
After using VSCode for Java for a few months, one of the things I find missing is a better parameter info. When there is a rather large function (long function name or parameters), it gets hard to navigate through the window because they ending part get cut, as seen on the attached picture: In the next example, it also shows how hard it is to know what parameters the function accepts, since you can only see the first parameter. Having an adjustable window, or even a configured fixed size width, would improve code navigation alot. |
OMG it looks like this is getting some attention. Hell yes hell yes hell yes! Super excited for this now. |
Ok, so this is the plan
|
This sounds like an amazing improvement! What happens if it's too big for the window? Details fall down below completions? |
FYI - I have merged the first cut into master (#109094). This means next insiders (tomorrow) will have this. There might still be rough edges and bugs but I want to get feedback rather sooner than later. 👉 try this in https://code.visualstudio.com/insiders/ 👈 |
@jrieken these updates are 🔥 . Should there be a min-height on the description that caps where the text ends? This feels a bit odd: Also, it appears that the description height doesn't persist even though all others do? |
It's possible for the text to be extremely tall, so a min-height couldn't be based on that. Any chance this update could also give us an option to control the size of the text in these boxes separate from everything else? |
There are these settings: |
This comment has been minimized.
This comment has been minimized.
This is done. Will ship with next stable and is already available in insiders. Please file bugs for further work and polish |
wooo! been following this for 3 years, excellent news ;) |
Will the ability to resize the window also apply to the tooltip/hover window that is used by Hover providers? |
This feature is incredible and works perfectly. Thank you very much @jrieken for developing this 😍 |
Hello, I am creating a snippet for VS Code with long descriptions. I have noticed that the description popup window in VS Code has a scrollbar, but it would be greater if I can enlarge the window. This seems not to be possible in the current version (1.13.1). It would be better if one can either set the height and width in the preferences or change the size of the popup with mouse dynamically.
Regards steff
The text was updated successfully, but these errors were encountered: