The JADE 2022 release meets tomorrow’s business demands.
Is it possible to improve the performance of F11 when the selected cannot be resolved? e.g. If I press F11 on selected code that isn't a property, local variable or a method the Escape takes a bit of a hammering. No idea why I press Escape?
The latest example is when generateMethodStub failed and I wanted to check the method was created.
One idea is telling us that the selected item could not be resolved and it is going to take a while, should Jade proceed?
We consider this as a fault and have created PAR 69047 to cover this.
sounds like a fault, bro. Hop over to Parsys.