Selecting the `Run As` or `Debug As` options in the menu often results in a long UI block in which possible launcher need to be found. This is especially annoying when one does not want to lauch anything, but just moves the mouse up and down to reach another entry.
I don't know if this problem can be solved at all in Eclipse, because the menu probably requires a list of items instead of a reactive lits of items, but maybe it is at least possible to speed up the computation logic.
I don't know if this problem can be solved at all in Eclipse, because the menu probably requires a list of items instead of a reactive lits of items, but maybe it is at least possible to speed up the computation logic.
Leave a comment
on 2014-10-09 14:44 *
By Iulian Dragos
Unfortunately it is not possible, while staying within Eclipse APIs. Maybe just a smarter implementation. However, the test should be very fast for most files, unless some Java-specific logic is triggered (that would be a regression). We had some weaving, I think, in order to make sure the JDT code doesn't run on Scala code (it would trigger a long chain of structure builder calls, that are usually very slow).
No file chosen
You have an empty file field. Please select or remove it.
Name | Size |
---|