Peter, What you're seeing is an artifact of code that was changing quickly. Unfortunately, I'm in the middle of starting a new project and have fallen a bit behind on taking care of Bugzilla.
Hopefully this week... Dave ---------------------------------------------------------------------- Message: 1 Date: Mon, 9 Apr 2007 15:47:21 -0400 From: "Peter Centgraf" <[EMAIL PROTECTED]> Subject: [nebula-dev] [CompositeTable] InternalCompositeTable.currentRow() failure To: "'Nebula Dev'" <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset="US-ASCII" 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 ------------------------------ Message: 2 Date: Tue, 10 Apr 2007 15:56:02 +0200 From: Andr? Dietisheim <[EMAIL PROTECTED]> Subject: Re: [nebula-dev] [CompositeTable] InternalCompositeTable.currentRow() failure To: Nebula Dev <[email protected]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=utf-8 Hi Peter I filled several bugs and patches in the bugzilla and the behavior you describe sounds very similar to the bugs I found an pathed. I made a major refactoring to the whole current-row logic (current row arrive, depart, etc. - bug 173558: 'IRowFocusListener arrive() and depart() inconsistent'). I suggest you apply my patches related to this. It should fix a whole lot of things related to these bugs I found in 0.92. https://bugs.eclipse.org/bugs/show_bug.cgi?id=173558 https://bugs.eclipse.org/bugs/show_bug.cgi?id=173859 https://bugs.eclipse.org/bugs/show_bug.cgi?id=174041 I'd appreciate a lot any feedback when applying my patches and your current work! Regards Andr�� On Mon, 2007-04-09 at 15:47 -0400, Peter Centgraf wrote: > 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 > > > !DSPAM:461a985893472138512278! > ------------------------------ _______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev End of nebula-dev Digest, Vol 13, Issue 3 *****************************************
_______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
