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.

Bug 35524 - IDE becomes unusable after this exception happens
Summary: IDE becomes unusable after this exception happens
Status: RESOLVED INVALID
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P3 blocker (vote)
Assignee: Martine
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-20 21:42 UTC by vanob
Modified: 2003-09-01 11:16 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
ide.log (48.29 KB, text/plain)
2003-08-20 21:43 UTC, vanob 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description vanob 2003-08-20 21:42:51 UTC 
Hello

I created some class. Tools/Add to component palette.
When I tried to drop this control on a panel. exception 
window poped up and it does not want to close.

attaching ide.log
Comment 1 vanob 2003-08-20 21:43:39 UTC 
Created attachment 11386 [details]
ide.log
Comment 2 Tomas Pavek 2003-08-21 08:53:17 UTC 
I guess this is caused by the first NullPointerException from your code:
de.haufe.arbeitsmittelverzeichnis.MainFrame.getText(MainFrame.java:87)
...

Due to it, OverlayLayout of form editor initilizes improperly and then
throws the other eceptions again and again.
Comment 3 vanob 2003-08-21 09:02:23 UTC 
I agree with you 
but I think that IDE must be more stable to developer errors.

Supposed Behaviour should be to throw an exception and don't repeat it
infinitely.

Reopening
Comment 4 vanob 2003-08-21 09:04:38 UTC 
Further If you close the IDE and reopen it,
this exception continues to appear if you open form editor.
As a netbeans user I don't know which files should I delete in my
userdir to correct this porblem.
Comment 5 Tomas Pavek 2003-09-01 10:12:54 UTC 
To correct the problem, you need to close the form causing the
problems (its java file in the source editor). That should be possible
even if there are some exceptions.

The IDE must be robust to handle errors in user components, but it is
possible only to certain level. E.g. validating and painting happens
completely in Swing/AWT direction, so the form editor has not much
chance to influence it. If a component is not even able to paint
itself then we can hardly do anything reasonable with it...
Comment 6 vanob 2003-09-01 11:16:36 UTC 
Thank you for the workaround. That's what I wanted to know.