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 91456 - Gui: performing action does not show right message screen
Summary: Gui: performing action does not show right message screen
Status: RESOLVED DUPLICATE of bug 76587
Alias: None
Product: java
Classification: Unclassified
Component: JUnit (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Marian Petras
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2006-12-22 06:18 UTC by abonnema
Modified: 2007-09-20 13:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
about screen containing platform information (19.84 KB, image/png)
2006-12-22 06:25 UTC, abonnema 		Details
Screenshot of message window single compile obscured. (222.21 KB, image/png)
2007-01-06 06:57 UTC, abonnema 		Details
messages.log file from ~/.netbeans/5.5/var/log (23.48 KB, text/plain)
2007-01-06 07:00 UTC, abonnema 		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 abonnema 2006-12-22 06:18:45 UTC 
Hi guys,

When I perform any action that outputs to one of the message screens, the 
system does not show the results of the action. The message screen is created, 
but the current message screen when issuing the message remains current.

F.i. when I compile, the compile message screen tab is created, but the screen 
remains obscured. You must click on the right tab to show the compile results.

Seems like a bug to me.
Can anyone corroborate this?

I will print my about screen that includes platform in an attachment.

Guus Bonnema, Leiden, The Netherlands.
Comment 1 abonnema 2006-12-22 06:25:59 UTC 
Created attachment 36891 [details]
about screen containing platform information
Comment 2 Milos Kleint 2007-01-02 12:58:46 UTC 
can you attach a screenshot of the obscured output tab?
als please attach the ~/.netbeans/5.5/var/log/messages.log file that could
provide additional info.

thanks a lot.
Comment 3 abonnema 2007-01-06 06:53:46 UTC 
apologies for the delay.

Attached is the screenprint plus message.log as requested.
Also a description of *when* the error occurs:

1. I start editting, compiling: everything looks fine.
2. I perform a test using JUnit testsource and the key-combi shift-f6.
3. Switch to a regular source, edit, compile (f9).

What happens then, is that I -- very briefly -- see the compile screen, but 
almost immediately it switces back to the JUnit message screen with 
testmessages on it. 

Well, hope this helps.

Guus.
Comment 4 abonnema 2007-01-06 06:54:22 UTC 
apologies for the delay.

Attached is the screenprint plus message.log as requested.
Also a description of *when* the error occurs:

1. I start editting, compiling: everything looks fine.
2. I perform a test using JUnit testsource and the key-combi shift-f6.
3. Switch to a regular source, edit, compile (f9).

What happens then, is that I -- very briefly -- see the compile screen, but 
almost immediately it switces back to the JUnit message screen with 
testmessages on it. 

Well, hope this helps.

Guus.
Comment 5 abonnema 2007-01-06 06:55:01 UTC 
apologies for the delay.

Attached is the screenprint plus message.log as requested.
Also a description of *when* the error occurs:

1. I start editting, compiling: everything looks fine.
2. I perform a test using JUnit testsource and the key-combi shift-f6.
3. Switch to a regular source, edit, compile (f9).

What happens then, is that I -- very briefly -- see the compile screen, but 
almost immediately it switces back to the JUnit message screen with 
testmessages on it. 

Well, hope this helps.

Guus.
Comment 6 abonnema 2007-01-06 06:57:35 UTC 
Created attachment 37105 [details]
Screenshot of message window single compile obscured.
Comment 7 abonnema 2007-01-06 07:00:25 UTC 
Created attachment 37106 [details]
messages.log file from ~/.netbeans/5.5/var/log
Comment 8 abonnema 2007-01-06 07:06:29 UTC 
Additionally, I just saw that F11 (a fresh build) has the same behaviour, 
following a testrun. Pushing F11 the second time *does* produce the right 
message window.

Hope this helps.

Guus.
Comment 9 Milos Kleint 2007-09-20 12:31:49 UTC 
AFAIK this is intended behaviour. when junit is run by ant, the junit window shows the test results.
reassigning to junit for evaluation.
Comment 10 Marian Petras 2007-09-20 13:21:27 UTC 
You probably encounter issue #76587 ("JUnit results window often reopens itself"), I fixed in NetBeans 6.0 Milestone 1.
So I mark this issue as a duplicate of that bug. Feel free to reopen this bug if you think it differs from issue #76587.

In recent milestones of NetBeans 6.0 (e.g. in NetBeans 6.0 Beta 1), the test results window is not opened until the
tests finish.

*** This issue has been marked as a duplicate of 76587 ***