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.

Sign up for GitHub

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

Jump to bottom

Impossible to change *any* option in Visual Studio after changing the font #4

Open
abelbraaksma opened this issue Nov 20, 2017 · 2 comments
Open

Impossible to change *any* option in Visual Studio after changing the font #4

abelbraaksma opened this issue Nov 20, 2017 · 2 comments

Comments

@abelbraaksma
Copy link

abelbraaksma commented Nov 20, 2017 •
edited
Loading

Not sure what happens here, but I tried changing the font (I chose Segoe UI Light, it had no effect) and then wanted to change it again.

Result: impossible to click anything in the Options dialog, or to click OK. Only Cancel works. Closing / reopening Options doesn't help either.

remarker_comments_breaks_vs_options

PS: I do like how your plugin works, but I need to be able to change font and color, because otherwise it is unreadable on dark styles. Obviously, that it blocks the whole Options dialog wasn't expected. This was in VS 2017 Pro 15.4.4.
@abelbraaksma
Copy link
Author

abelbraaksma commented Nov 20, 2017 •
edited
Loading

After restarting Visual Studio 2017, I can access other settings again. But once I click any of "Remarker" in the tree on the left, it behaves like above (I cannot change a thing, or click OK). Closing / reopening Options does not help. I also tried disabling the extension and re-enabling it again, still same problem, it remembered the font (which isn't the default) and won't allow me to click anything.

Since this makes working with this extension impossible, I had to uninstall it, unfortunately. But I'll happily try it again if you know of a workaround or a fix :).

@jgyo
Copy link
Owner

jgyo commented Jan 19, 2018

Thank you for your report. I'll try to reproduce the problem and investigate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jgyo @abelbraaksma