Closed andreasdc closed 1 year ago
Please show a screen shot so we can understand what you see and what you expect.
For example I have 1 project in my workspace. I use this project in the another one, and I click F3 to view the source. The "source" because it shows compiled something, opens from the referenced libraries, not from the workspace.
Please show a screen shot. It's very easy. You can simply copy the image (Snip & Sketch on Windows) and paste it into the entry field.
Screenshot of what? Referenced libraries?
Yes, of this huge tree you are seeing in the IDE and what the open editor looks like. I assume you have link-with-editor enabled, but a picture of your IDE is worth 1000 words of describing what you see in it.
It just opens the class inside the library from the referenced libraries, instead of pointing directly to the workspace.
Less words, more pictures.
You don't know what referenced library look?
Well, I expect it to look like this:
But the "huge tree" only shows because I have link-with-editor (button underlined in red) enabled. Presumably you do too, but I can't tell because it's not in your picture. Also you can see that the editor that's opened is for a *.class file, but I can't tell in your case because that's also not part of your pictures.
But in my case there is no PropertyTest.java in the workspace. So I'm wondering about your assertion that there is a workspace .java file as opposed to only a .class file from a library with attached source. I'm a bit doubtful because workspace dependencies look like this:
They are not expandable so if you have a dependency on another project, F3 will navigate to the project.
That's the issue. Link with editor button causes that. Thanks. Do you have idea for my issue with windows when dragging mouse on every class?
When you try to get the source of the file, it opens the file from the referenced libraries, creating huge trees of packages and classes, instead of just redirecting you to the file from the workspace project.