Community
Participate
Working Groups
M6 See Bug 107925. if an invalid image is used we are not handling the exception with the red x like we should.
Kindly update us on the status of this defect.
If we intend to fix a bug for a particular release we mark it in target milestone.
Please feel free to submit a patch
would it be ok to catch exceptions from ImageDescriptor.createImage()? Another solution is to delegate createImage to some registry or utility (I don't know which exactly) which will handle any exceptions. As there seem to be an unknown number of exceptions, that createImage might throw, not only java.lang.NegativeArraySizeException which started this bug.
Another error case to address
below i submit a patch with catching exceptions and processing them by StatusManager, however it still might not be very strightforward, because only errors not handled by SWT will be processed. i.e. if some errors will cause that SWT return a default image (well known red square), nothing is logged. But if SWT will fail with exception, then there is no image at all (like the product had not configured any) and status is logged. similarly with features buttons, which also might have invalid images.
Created attachment 56624 [details] handlind inv.images
I have run out of time. To address in 3.5.
Removing 3.5 target milestone. We are in the end-game now. Please have a look and decide if this should be targeted at 3.6.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
