| Reporter |
Alexander Kirsanov (alexander_kirsanov)
|
|---|---|
| Created | Feb 17, 2016 11:15:44 PM |
| Updated | Apr 11, 2018 4:04:42 PM |
| Resolved | Apr 11, 2018 4:04:42 PM |
| Subsystem | Code Analysis - C# |
| Assignee | Alexander Kirsanov (alexander_kirsanov) |
| Priority | Critical |
| State | Fixed |
| Type | Bug |
| Fix version | 2017.3 |
| Affected versions | No Affected versions |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
I attached the gif, just in case of misunderstanding, but hope there's none =)
The problem (and priority) comes from the fact that I've supported this feature in Rider,
so it blinks not only in VS external sources, but everywhere.
I made some changes in the source code while doing it so you need to cherry-pick the
"c5dfbcd29c7ce794866e26b0a447639181a83e52" revision from wave05-ide.
I think the implementation should match the corresponding one for matched string arguments.
I also think the optimization with the visible range in editor is urgent due to possible amount of such highlighters.
Or maybe it's even reasonable to check the ranges in which a caret moving happened,
and don't delete any of highlighters if it's still inside one of previously computed.
Because the using of prolongated lifetimes reduces the blinking but not memory traffic and protocol transportation cost.
The problem (and priority) comes from the fact that I've supported this feature in Rider,
so it blinks not only in VS external sources, but everywhere.
I made some changes in the source code while doing it so you need to cherry-pick the
"c5dfbcd29c7ce794866e26b0a447639181a83e52" revision from wave05-ide.
I think the implementation should match the corresponding one for matched string arguments.
I also think the optimization with the visible range in editor is urgent due to possible amount of such highlighters.
Or maybe it's even reasonable to check the ranges in which a caret moving happened,
and don't delete any of highlighters if it's still inside one of previously computed.
Because the using of prolongated lifetimes reduces the blinking but not memory traffic and protocol transportation cost.