Skip to content
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

DiagnosticInfo Sometimes appear extra small. #15

Open
pushqrdx opened this issue Oct 28, 2018 · 4 comments
Open

DiagnosticInfo Sometimes appear extra small. #15

pushqrdx opened this issue Oct 28, 2018 · 4 comments

Comments

@pushqrdx
Copy link
Contributor

There's this issue when sometimes the diagnostic info appears so small. Firstly, I thought that it's happening because text length but recently /i found that it's kinda random.

Here's a picture
image

@eberthold
Copy link
Owner

That's already fixed on the master. I surely need to work on my branching strategy ;)
Commit: 061cb44
Reason for that is: I initially used a ViewBox to shrink the info, so they never break out of it's bounds. That could happen if extensions like "shrink empty lines" were installed. But that also means that, if the line of code is very long, the info also gets very small. And because I reuse the UI containers that problem stays on reused items too, because the ViewBox seems to never increase it's bounds only decrease seems to work properly.

I will close this issue when I get the current master to release

@pushqrdx
Copy link
Contributor Author

pushqrdx commented Oct 29, 2018

@eberthold Glad that you already fixed that. Regarding Steroids, I have multiple additions in mine that i am willing to try and contribute them (the marker bar is one of them) and i wonder if you'd be interested in a collab :).

PS, It really bugs me that the extension is named SteroidsVS, I mean why not just Steroids 😅, the name is too good on it's own and can pack so many features that makes it a one stop shop!

Edit: I just confirmed that the issue happened with my own fork which already contained the fix you mentioned. So it looks like the fix didn't work and issue persists as reported above.

@eberthold
Copy link
Owner

Hey, feel free to contribute 🙂 Any help is appreciated as I don't have that much time to code in my free time as I'd love to have. But be aware the endpoints of Visual Studio are sometimes poorly documented and a decompiler like ILSpy/dnSpy will become your best friend 😃

For the name: I originally thought to port this extension to Visual Studio Code in the future which then may should have VSC as suffix. But thats just a personal preference. I'm open for ditching the suffix 🙂

For the issue itself: I will have another look at it in the coming days. Currently I'm focusing to finish the keyboard handling problem to bring the master branch back to a state it deserves.

@pushqrdx
Copy link
Contributor Author

@eberthold Alright then, I'll be waiting for the keyboard handling fix you're doing then i'll start cherry picking a list of features that are suited for Steroids and if you like them we might start introducing them :)

For the time being, here are the ones i am planning to try and add as soon as possible

  • Marker Bar.
  • Resharper style parameter info (might be hard to implement but i'll fiddle around).
  • Focus usages. Hover over a variable or method and hold a shortcut to fade out all text except for places where the it's used.
  • Add multiple break points at once <- there's an extension that does this but packed with other useless things.

TBH, Steroids is the reason i ditched Resharper in the first place. That list along with the latest additions to Visual Studio 2017, Hopefull, I think Resharper will be useless.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants