-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Minimap: add a alwaysShowViewport
setting
#21784
Comments
related #21810 |
@alexandrudima I added this gif to illustrate the two situations in #21823 Allow a rectangular shadow to indicate where the minimap is, without having to move the mouse. Like Atom. And when it slides horizontally, another shadow will be shown to indicate that I'm going to the side. Like Atom. |
Change file .minimap-slider{opacity:0 --> .minimap-slider{opacity:1 for highlight always |
Is anyone working on this? |
@deltaidea we didn't start on this yet. You can go ahead :) |
|
@alexandrudima How to activate horizontally? The same is not working for me, as in Atom. I put a sample gif in this comment. |
-- Sorry for the English, I used Google Translator -- All right, @alexandrudima . You are doing a job, but I believe that the suggestion I have made has significant votes. 👍 Note: I want to make it clear that horizantal does not need to be done right away. Sorry for the outburst. 🤔 😊 @alexandrudima You may argue, "It's better to track." But the first criterion for you in the vast majority is always number of votes for a new resource, and it would be difficult, in certain moments to get the votes again. I had created another question before, you marked it as duplicate, so you think it will come all at once. Well many question, in some question there is comment similar to this.: "We will expose the ideas in a single case - because it is better to track." It was much better for you to have changed the title of the first question and to inform me thus "Here only the horizontal resource will be traced." Then you say that it is for us to look up the questions before creating a new one (ps: yes, not many suggestive names in the questions until you change them - or the difference of language in my case), but when we suggest something Get votes on this question) you ask to create a new one (or in the case we already created it and it was marked as duplicate and we have to create it again.) You better review the way you deal with these situations, in my opinion. NOTE: This does not include when there is OS difference. One more excuse for the outburst. 😊 😊 I may even be denied the comment or be hated, but I had to write it this. |
@alexandrudima ok, close this one but you also close the other one. So no open issue for this feature. When it will be implemented? |
@magic890 It's already implemented. It's currently available on the Insiders channel. It'll get into the stable release in a couple weeks I think. |
-- Sorry for the English, I used Google Translator -- Yes, @alexandrudima , but I would be happy to contribute. But I have better enough my English, being that is something main here. In addition to having a longer time to study TypeScript. Anyway, thank you very much for implementing the feature. ❤️ ❤️ 👏 👏 👏 But my argument is valid since it was previously marked as a duplicate, and since you ask for a single issue to be tracked, to make it easier, it will soon be interpreted that everything will be done in a single question. That's why I was a little upset. But everything was solved. Thank you one more time. ❤️ ❤️ 👏 👏 👏 |
Verified that the new setting "editor.minimap.showSlider": "always" works as suggested in this issue. |
Currently the user is required to hover over the minimap to see the viewport.
A setting which keeps the viewport visible at all time would greatly improve my minimap experience. Something like:
The text was updated successfully, but these errors were encountered: