This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The Exception window is able to show information for multiple exceptions that have occurred. To switch between exceptions, the buttons "Previous", "Next", and "Cancel" are available. In the current implementation, buttons are hidden rather than disabled when the option isn't available. For example, when viewing the first exception the Previous button is hidden. The dynamic visibility is causing a number of problems, all of which can be resolved by using a disabled state rather than hidden visibility for the buttons whose actions are not available. 1. When 3 (or more) exceptions are displayed and the first is showing, then "Next" and "Cancel" buttons are the same size. When the user presses "Next", the "Previous" button appears and all three buttons resize to fit the word "Previous". This is especially problematic if the user pressing on the Next button twice to move forward 2 items - the resizing will result in inadvertantly clicking "Cancel". 2. When 3 (or more) exceptions are present, and the user presses "Previous" to move back 2 items, the user will actually press "Previous"-"Next" due to an extra button appearing under the cursor.
passing to platform, since this dialog is a level below exception reporter.
(In reply to comment #1) > passing to platform, since this dialog is a level below exception reporter. The exception reporter shows/hides the Previous button, does it not?
(In reply to comment #2) > (In reply to comment #1) > > passing to platform, since this dialog is a level below exception reporter. > > The exception reporter shows/hides the Previous button, does it not? I don't think so Standa (but might be wrong) ... I had removed ER from the IDE and risen an Exception -> the behaviour decribed by reporter was there as well. I would really vote for switching from shown/hidden to enabled/disabled buttons. Another problem is that sometimes (in this case just with ER in), when you'll get >1 exceptions at once (in Unexpected Exception) dialog at once, and this dialog comes for the first time -> it's too small (not all buttons fit into the layout), so some of them are screwed-up. I think it was already reporterd, but I can't find the issue.
(In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > passing to platform, since this dialog is a level below exception reporter. > > > > The exception reporter shows/hides the Previous button, does it not? > > I don't think so Standa (but might be wrong) ... I had removed ER from the IDE > and risen an Exception -> the behaviour decribed by reporter was there as well. Exception reporter doesn't use Wizard API so the previous/next buttons are provided by the exception dialog. It doesn't use any Dialogs API for that. > I would really vote for switching from shown/hidden to enabled/disabled > buttons. +1 > > > Another problem is that sometimes (in this case just with ER in), when you'll > get >1 exceptions at once (in Unexpected Exception) dialog at once, and this > dialog comes for the first time -> it's too small (not all buttons fit into the > layout), so some of them are screwed-up. I think it was already reporterd, but > I can't find the issue. I think it's just another manifestation of this problem. Call Swing API from EDT only and it should be fine.
the dialog is o.n.core/src/org/netbeans/core/NotifyExcPanel.java and it belongs to ide/logger probably