Skip to content

Reduce default C++ inlay hint font size to match VS and potentially reduce confusion #9480

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

Merged
merged 3 commits into from
Jun 24, 2022

Conversation

sean-mcmanus
Copy link
Contributor

@sean-mcmanus sean-mcmanus commented Jun 20, 2022

The smaller font size makes it more obvious that the inlay hint is not actual editor text, and hopefully users will realize that the type data shown is the complete type data (existing type data should be ignored) and not intended to be mentally combined with the existing type data on the left, e.g. in the example below, it's not a pointer to a const, but a const pointer to a non-const int:

image
This doesn't affect inlay hints for other languages.

UPDATE: Size 11 seemed slightly too small and the VS UI is in flux, so it seems better to go with 12, which matches the 90% used by editor.codeLensFontSize in VS Code.

@sean-mcmanus sean-mcmanus requested a review from a team June 20, 2022 23:48
@sean-mcmanus sean-mcmanus added this to the 1.11.1 milestone Jun 20, 2022
@sean-mcmanus sean-mcmanus merged commit a268363 into main Jun 24, 2022
@sean-mcmanus sean-mcmanus deleted the seanmcm/reduceInlayHintFontSize branch June 24, 2022 00:33
Colengms added a commit that referenced this pull request Jun 29, 2022
…tentially reduce confusion (#9480)"

This reverts commit a268363.
Colengms added a commit that referenced this pull request Jun 29, 2022
…tentially reduce confusion (#9480)" (#9522)

This reverts commit a268363.
@github-actions github-actions bot locked and limited conversation to collaborators Aug 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants