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 196396 - Copied elements disappear
Summary: Copied elements disappear
Status: RESOLVED INVALID
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Natural Layout (show other bugs)
Version: 7.0
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords:
: 203781 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-03-07 12:48 UTC by asenk
Modified: 2011-10-18 16:01 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description asenk 2011-03-07 12:48:25 UTC
Start IDE with clear userdir. Create new project, Java Application (e.g. MyApplication) and create a new form (e.g JFrame) containing several components. 
1. Create second JFrame form and copy (using ctrl+c, ctrl+v) into it some elements (e.g JButton, JLabel)
2. Drag some new element from palette
Result: While you draging a new element the copied elements disappear. When you put a new element into form, you can see the copied element again.
Comment 1 Jan Stola 2011-09-08 15:57:44 UTC
While this seems strange at the first sight it is as designed. There is no way to specify the location of the pasted component. That's why they are pasted into a special layer independent of other components. The user is expected to drag the component into the desired location just after pasting.

If you paste several components then all of them are placed into the mentioned special layer. They remain there until they are dragged/moved into their desired location. When a component is being moved from the special layer then the remaining components from this layer are hidden to show just the "finalized" content. The component being moved from the special layer is not allowed to snap to/align with the remaining components in the special layer. So, we hide them to clarify their different status.
Comment 2 Jan Stola 2011-10-18 11:53:01 UTC
*** Bug 203781 has been marked as a duplicate of this bug. ***
Comment 3 Jan Stola 2011-10-18 16:01:45 UTC
The described behaviour is as designed, but it seems to be a bit confusing. I have filled an issue covering potential enhancements in this area. See issue 203917.