Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

DecoratorManager / DecoratorScheduler sometimes faster than the ThemeEngine creating artifacts

未关闭
#3,926 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
冷清
技术栈
java
领域
desktop

调研方向

Start by tracing DecoratorManager and DecoratorScheduler alongside the JFace ColorRegistry and E4 CSS engine, focusing on how decoration jobs read and cache theme colors during workbench startup. Check how the active theme populates the decorator's color keys and whether the decorators have a reload path. Done means decorations no longer retain a default or null color when the registry is populated after a job reads it.

由索引模型根据 Issue 内容生成。

描述

bug

The JFace ColorRegistry (owned by IThemeManager) and the E4 CSS engine populate their values on parallel paths during workbench startup.

DecoratorManager runs its decoration jobs on a background job thread. If a decoration job computes a DecorationResult before the color registry entries for that decorator's color keys have been populated by the active theme, the decorator gets a default (or null) Color, which is what ends up cached on the TreeItem.

This can be the result:

Image

I believe we need to way to tell the decorators to reload there colors, current implementation is : read onces, never update.

主要语言
Java
星标
124
派生
269
平均合并
2 天 2 小时
30 天内合并 PR
70

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

eclipse-platform/eclipse.platform.ui 的其他 Issue

查看 eclipse-platform/eclipse.platform.ui 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。