Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
The quick fix icon blinks when moving the caret with the arrow keys. This is very distracting: http://screencast.com/t/BJgVeptd0tt7
Maybe MD should only do the analysis when the caret stays in one place for > 2s or so. This would also help perf when typing/navigating. In order to make the context menu and quick fix keybinding work correctly, they would have to force the analysis to run immediately.
I do wonder whether we need the icon at all. Most of the time it's not necessary, it's just visual noise. The user will *know* that MD can perform a particular transformation, or fix a particular underlined/highlighted problem, so they will use the context menu or alt-enter, at which point we can force the analysis in order to present the valid options.
The icon is nice as a hint, I know. But the important things will be underlined, and the user can discover less important things via the context menu (just like they have to do for rename, go to definition, etc), or learn about alt-enter.
There are many users that don't know or use context menus. The feedback & feature requests told that - we had users that didn't know that MD can do rename, implement interface etc.
We can't rely on context menus for that reason. We've many functions only available via context menus - and that's an usability issue of MD. We need to improve the main menu and esp. the functions in the pads.
Therefore we need an icon. Esp. with the actions the user can't know that MD can perform a transformation because there will be too many - that's a learning process for the user.
However I wanted to use a code rush like icon there, it's much better than reshaper. The reshaper icon is too far away from the caret & it's a bit too intrusive.
Maybe the icon needs to be done different, since that approach is very slow on mac. (Like many gtk operations that are very slow there :( )
You know that I've stopped developing the refactoring stuff atm - when there is higher demand for that I'll maybe get some time to improve this feature.
FWIW, i don't think the perf issue is GTK+ related. Backtraces seem to indicate it's caused by some number of TPL threads doing analysis.