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 93574 - Dialog for new action has bad inicial position in a scope of screen
Summary: Dialog for new action has bad inicial position in a scope of screen
Status: VERIFIED INVALID
Alias: None
Product: guibuilder
Classification: Unclassified
Component: App Framework (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Joshua Marinacci
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-30 15:02 UTC by Jana Maleckova
Modified: 2007-08-29 09:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
screen shot (142.92 KB, image/png)
2007-01-30 15:03 UTC, Jana Maleckova 		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 Jana Maleckova 2007-01-30 15:02:42 UTC 
NetBeans IDE Dev (Build 070130)
1.6.0-rc; Java HotSpot(TM) Client VM 1.6.0-rc-b104
Windows XP version 5.1 running on x86
en_GB (nb); Cp1252

Description:
============
invoke action editor (on e.g action property of jButton)a and try to create new
action. Dialog for new action jump to top left corner of screen. See screenshot

second note:
it's about dialog for new action
right margin is very closed to jTextField (Method name) and to jButton (Create).
There should be preffered space between components and right edge of dialog.
Comment 1 Jana Maleckova 2007-01-30 15:03:33 UTC 
Created attachment 37831 [details]
screen shot
Comment 2 Joshua Marinacci 2007-01-30 18:34:21 UTC 
I have switched to using the DialogDisplayer. Can you confirm that this bug still happens with the latest 
builds? Thanks.
Comment 3 Jana Maleckova 2007-01-31 12:13:38 UTC 
now dialog has correct position when is invoked, but wrong alignment of
jTextField and JButton remains on the dialog's right margin.
Comment 4 Joshua Marinacci 2007-04-17 01:19:18 UTC 
This dialog no longer exists so this bug is now invalid.
Comment 5 Jana Maleckova 2007-08-29 09:29:26 UTC 
verified