| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This PR updates TMUIPlugin.start() to avoid SWTError: Invalid thread access by deferring image-registry initialization to the UI thread when the Eclipse workbench is running (addressing issue #1010 seen in headless/LSP test scenarios).
Changes:
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
|
@akurtakov do you think a more idomatic solution would be to not initialize the image registry in the start method or async via UIJob but lazy like this? @Override
protected void initializeImageRegistry(final ImageRegistry registry) {
TMImages.initalize(registry);
} |
Sorry, something went wrong.
|
@sebthom Sorry, this one got lost in the amount of notifications. |
Sorry, something went wrong.
This change adjusts TMUIPlugin.start() to not initialize the ImageRegistry, avoiding start-up exceptions when TMUIPlugin.start() is not called from a UI thread. Instead, the ImageRegistry is initialized lazily by overriding: AbstractUIPlugin.initializeImageRegistry() Fixes: eclipse-tm4e#1010
|
Thanks! |
Sorry, something went wrong.
|
Thank you for merging! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This change adjusts TMUIPlugin.start() to not initialize the ImageRegistry, avoiding start-up exceptions when TMUIPlugin.start() is not called from a UI thread.
Instead, the ImageRegistry is initialized lazily by overriding: AbstractUIPlugin.initializeImageRegistry()
Fixes: #1010