IT Mill Toolkit Forum

Yes. To make it easier for component developers to implement size for their components the Sizable interface is to be removed. Components that has a controllable size will implement HasSize interface and use Size object to store very general size information. Previously all Sizeable components had similar logic in them. Usage example of new component resizing below.

Code:

 
 component.getSize().setHeight(height, unit)

Hm, now (with nightly build and corrected setWidth/height usages) it falls with NullPointerException on this line:

splitter.getSize().setSizeFull ();

, where splitter is a SplitPanel, looks like getSize() in SPlitPanel component returns null or not yet implemented

dll wrote:

Hm, now (with nightly build and corrected setWidth/height usages) it falls with NullPointerException on this line:

splitter.getSize().setSizeFull ();

, where splitter is a SplitPanel, looks like getSize() in SPlitPanel component returns null or not yet implemented

Oops

Yep, that method (getSize() in SplitPanel) was unintentianally left undone (always returns null), but it's fixed now. The next nightly should have it fixed.

I guess this is the drawback of using IDE's like Eclipse, which do most of the coding for you. Or maybe I should check my TODO list more often

Oops

And of course the forum crashed while I was typing the message, and my login information disappeared

Regarding IDEs- yes, that's now almost terrible for me, when I sit to vi for quick fixes and begin expecting from it all those IDE featues like completion, suggestion, autoimorts, etc etc etc