When will it be updated? icons for macos 26 tahoe
请先确认以下事项
- [x] 已仔细阅读了 README
- [x] 在 issues 页面搜索过(包括已关闭的 issue),未发现类似功能建议
- [x] Easydict 已升级到 最新版本
- [x] 我理解并认可上述内容,并理解项目维护者精力有限,不遵循规则的 issue 可能会被无视或直接关闭
功能描述
使用场景
mac
实现方案(可选)
No response
是否愿意提交 PR 实现该功能
- [ ] 我愿意提交 PR 实现该功能
We plan to release a new version this weekend.
icons for macos 26 tahoe
Do you mean the new Easydict logo?
Thanks for the reminder — we do need a new logo for macOS 26 Tahoe.
But that's uncertain, because I am not able to make a new logo; we may need to ask other teammates for help.
@Keldos-Li Hello, we're planning to update the Easydict logo for macOS 26 Tahoe. Do you have time to help?
Do you have time to help?
Sure! I'm ready to use Icon Composer. But maybe you could wait for a few days? (I've been rushing to finish a report these days 🥲)
ok, it isn't urgent, you can arrange the time yourself.
Thank you!
I submitted the icon update in #956 😃
The new icon needs to be packaged and released using the latest Xcode 26 to be compatible with macOS 26.
However, when packaging and releasing version 2.15.0 using Xcode 26, serious memory leaks and issues with the input cursor were encountered: https://github.com/tisfeng/Easydict/issues/970
We haven't had time to fix the above two issues yet, so the 2.16.0 version will temporarily use the old icon.
thx
@tisfeng Hi, I noticed that the previous memory issue has been resolved, maybe #956 needs to be merged again? The current icon is still the old one.
I previously packaged and released version 2.15.0 using Xcode 26 beta, and there may be problems with this version of Xcode, which could be causing the two issues mentioned above.
I'm not sure if this is an Apple bug, but later we will try to republish a version using an older version of Xcode.
I'm very sorry, but if we want to use the new icon, we must package it with the new Xcode 26, which unfortunately leads to memory and other issues https://github.com/tisfeng/Easydict/issues/970 😓
I previously tried to investigate this problem but couldn't find the root cause, so the only temporary fix was to package it using the old Xcode 16.
I will continue to slowly investigate this issue, but I expect it to be quite challenging.
Another approach is for us to rewrite Easydict using Swift/SwiftUI. This would fundamentally solve some very complex problems, such as memory leak issues.
This will be a long and slow process, and I've already started making slow progress on it: https://github.com/tisfeng/Easydict/pull/1035