Bug 559927 - Improve message when resource is opened in Java Editor instead of type
Summary: Improve message when resource is opened in Java Editor instead of type
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.13   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-07 12:42 EST by Gunnar Wagenknecht CLA
Modified: 2024-01-19 15:53 EST (History)
0 users

See Also:


Attachments
error dialog (71.84 KB, image/png)
2020-02-07 12:42 EST, Gunnar Wagenknecht CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gunnar Wagenknecht CLA 2020-02-07 12:42:28 EST
Created attachment 281744 [details]
error dialog

Steps to reproduce:

- any project with a .java file which is *not* on any classpaht
- open file with Cmd+Shif+R
- place cursor within file to any element that would be a target for "Open Declaration" (F3)
- press F3

An error dialog pops up saying:

> Problems opening an editor.
>
> <projectname> does not exist
>                                     OK


This is causing a lot trouble within our user based. It's unclear what the problem is.

I suggest a rewording to at least explain that the file is not part of a Java project and the action does not work. The user should try to use Cmd+Shift+T for opening the type in an editor.

Also, I was wondering if the Java editor should make it more clear that the user is editing a Java file but not a type. Because another part of the confusion - which we get asked about - is that a lot of things don't work as expected (eg., hover, etc.).
Comment 1 Gunnar Wagenknecht CLA 2020-02-07 12:47:00 EST
To emphasize, the culprit is confusing (lack of knowledge) between Cmd+Shif+R and Cmd+Shif+T. Long term a single "open thing" dialog might be a solution. But short term a rewording of the error message with a recommendation to use "Cmd+Shift+T" for finding/opening the type should be sufficient.
Comment 2 Eclipse Genie CLA 2022-01-28 12:57:57 EST
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.
Comment 3 Eclipse Genie CLA 2024-01-19 15:53:57 EST
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.