There appears to be a pretty basic bug in the current (as of today) download of CompositeTable. InternalCompositeTable.currentRow() is attempting rows.get(-1) in a variety of circumstances. The currentRow variable is getting set to -1 somehow, and this state is not being handled properly. This can be easily reproduced with any of snippets 2-6 in one click (on the down scroll arrow). I'm using Eclipse 3.3 M6 on Windows XP SP2.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=181651 I'm disturbed that such an obvious problem would be in a download marked as a "beta". Is this an artifact of the new nightly build process? Is there a way to get back to an older, more stable version of a Nebula component? -- Peter _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
