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 40506 - Frames are not executed by internal executor
Summary: Frames are not executed by internal executor
Status: VERIFIED FIXED
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@guibuilder
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-02-26 07:52 UTC by Jiri Skrivanek
Modified: 2004-02-26 12:10 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 Jiri Skrivanek 2004-02-26 07:52:55 UTC 
It started to happen from build 20040225-1956 that
frames created in IDE cannot be executed by
internal executor. It seems IDE started execution
but frame is not shown. By external executor it is
normally shown. To reproduce:

- create a JFrame from template
- add some components (but you don't need to)
- change executor to "Internal Execution" (in
properties of frame node or in Options)
- call execute action on frame node => class name
is displayed in the execution window but nothing
else happens, i.e. no frame is shown

Assigning P1 priority because in breaks the commit
validation suite.
Tested in build 20040225-2155, JDK1.4.2_03, WindowsXP.
Comment 1 Tomas Pavek 2004-02-26 09:22:30 UTC 
Fixed. Issue 32199 reverted.
Comment 2 Jiri Skrivanek 2004-02-26 12:10:11 UTC 
Verified in build 20040226-0952.