Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The currently open file is not recognizable in the project tree or in the open tabs #339

Open
andrew-sol opened this issue May 22, 2024 · 1 comment

Comments

@andrew-sol
Copy link

Look at the screenshots and try to find the currently open file in the project tree visually (the focus is on the editor pane). It's barely possible because it's grey on grey. The same applies to the open tabs. And those colors are not configurable.

I have the "Always select opened file" setting enabled to be able to find the sibling files to the current one quickly and I always get stuck with this theme.

Please make the colors configurable (maybe via a project file like .onedark) or make those colors more vivid.
What I want to achieve is to find the current file in the project tree within 0.5s or faster.

Environment

  • OS: macOS 14.4.1
  • PhpStorm 2024.1.1
  • Plugin version: 5.11.0

Screenshots

Screenshot 2024-05-22 at 10 51 51

Screenshot 2024-01-18 at 11 20 42

@andrew-sol
Copy link
Author

The workaround I discovered:

  1. Open /Users/<USERNAME>/Library/Application Support/JetBrains/PhpStorm2024.1/plugins/one-dark-theme/lib
  2. Extract the one-dark-theme-5.11.0.jar file
  3. Open one-dark-theme-5.11.0/themes/one_dark_vivid.theme.json (I use the "vivid" theme variant, open one_dark.theme.json if you use the default one)
  4. Find the "ui.Tree" section
  5. Add "selectionInactiveBackground": "#4d78cc"
  6. Save the file
  7. Go back to the .../plugins/one-dark-theme/lib folder, run in terminal:
jar cf one-dark-theme-5.11.0.jar -C one-dark-theme-5.11.0 .
  1. Restart the IDE

Now the inactive selection has the same bright color as the active one.
But will have to repeat the actions after each plugin update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant