Ed Merks

@iloveeclipse @akurtakov I wonder if it's possible that SWT can detect configurations that are known not to work and inform the user? After all, an issue like the following one...

I don’t think anybody will care whose fault the problem is. If I can’t tell whether a menu item in my Eclipse application is checked or not then my perception...

Probably everyone uses the staging view and this is how it looks for me with Windows 10:  I'll ask Eike to show how it looks for him.

This pretty much makes such things unusable. I'll be holding off updating to Windows 11 for a bit longer for sure. The folks I know generally are not involved in...

This is how it looks now:  This is what it looked like before:  How it looks now seems way too much space. How it was before looks compact...

I tried it locally a few minutes ago and checked if existing uses would get a warning about missing the close. New warnings that suggest close must be called would...

No, but I wasn't sure if that's because of some preferences. E.g.,  I'll test some more...

Here is a self-contained example:  So yes, an auto closeable that isn't closed is considered a resource leak and depending on how a project configures the compiler preferences, this...

I fully understand the common/general use case of a GC needing to be disposed within the block of code in which it is created and see significant value in the...

Builds before this fix have a problem with split packages with inconsistent signatures: https://github.com/eclipse-equinox/equinox/pull/685  I'm not sure what SWT is build against/with. The last build with the problem is...