Community
Participate
Working Groups
Currently we have 200 ms delay for the code assist auto activation. I find it a little bit annoying and feel more comfortable when setting the delay to 0 ms. We've done a lot of performance improvements. This 200 ms is noticeable and may be unexpected by users (including me). I believe that the auto activation delay had its role in the past when computers were slow and excessive code assist ruined the typing experience. This is not the case anymore nowadays. Note that JDT already switched to 0 ms delay. I think it is a good moment to do this change early in the release cycle.
New Gerrit change created: https://git.eclipse.org/r/75225
We should be careful with this option :) We did many performance improvements but I'm not sure if enough. But I agree that now it's the best time to test it.
JDT have auto activation delay = 0 together with activation chars (especially after "."). On larger projects (many types), PDT can often froze UI. Especially for instance creation (exception is slowest), method calls etc... For those we still need delay (try s| on symfony project or z| on zend project). But 0 delay for sequences like "->", "::" will help a lot !
Can we have bugs opened for all cases where 0 ms delay causes troubles? And mark these bugs as blocking this one. It does not make sense to apply this change, if we know it will cause troubles. But it would be helpful to know what issue needs to be resolved. I've got feedback from people switching from Zend Studio to alternative products because of the performance. Some of the pointed the noticeable delay in code assist as the main issue. Hence, I really want to get rid of this delay :)
Safer will be help with bug 251156 (bug 458335 for PDT) and calculating completion outside UI thread ;) Anyway, I'm adding potential blockers.
PDT 6.0 introduces, to make 0ms delay for assist, we need small modification in Platform. In auto-activated mode, selection should be empty (as in netbeans, VS code etc..). Without this user (or just me :P) will be angry if accidentaly use enter without esc.
