Community
Participate
Working Groups
I built an 'M2' installation using eclipse-SDK-I20190818-1800-win32-x86_64.zip Using normally, I ran my malfunctioning application to stop at an AssertionError. At line 326 of org.eclipse.qvtd.compiler.internal.usage.QVTcoreDomainUsageAnalysis TypedModel thisTypedModel = QVTbaseUtil.basicGetThisTypedModel(transformation); QVTbaseUtil is an open, recently edited, file. Previously selecting "QVTbaseUtil" and hitting F3 takes me to QVTbaseUtil.java in JDT. Now, hard to believe, F3 invites me to choose the Windows application with which to open the file! Selecting a similar static method QVTruntimeUtil.errPrintln("Missing this TypedModel fixed up for " + transformation); and F3 navigation to QVTruntimeUtil works as before. This is not intermittent in that QVTbaseUtil F3 consistently goes to system, but other F3 consistently work as normal. Trying Ctrl-1, both selections offer the same two rename in file/workspace quickfixes. Both selections offer similar hovertexts so there does not appear to be a novel declaration. Problem persists in Debug Perspective Editor View or Java Perspective Editor View. How is this even possible ??
(In reply to Ed Willink from comment #0) > How is this even possible ?? In the Package Explorer opening QVTbaseUtil.java takes me to the System editor. Somehow, perhaps magic finger trouble, QVTbaseUtil.java has got its editor association tweaked to the System. But, since the editor is open, even if the editor association has been magically corrupted, F3 should go to the open editor anyway.
Ed, does this happen only with qvtd? Anywhere else in platform projects where I can reproduce? Or can you please tell me how to get those projects?
I just put the QVTd details in to refresh my memory if I need to work harder on an obstinate repro. My comment #1 largely explains the problem. Somehow the editor association got broken. Manually breaking the association should provide a repro of the lesser problem that F3 to a declaration in an open JDT file nonetheless goes to the system. The magic editor association breakage can be dismissed as idiot-user finger-trouble until there are more reports. Unfortunately I have very magic fingers and without a video recording of my typing I have never been able to produce a repro for e.g. Bug 82904 despite it still occurring almost daily on at least 5 different computers/keyboards. (My suspicion is that with so many different bindings available, some too-fast key sequences can be debounced in 'hardware'/software as the wrong command sequence.)
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
