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 196144 - Undo/Redo problem in Design form
Summary: Undo/Redo problem in Design form
Status: RESOLVED INVALID
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Natural Layout (show other bugs)
Version: 7.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: issues@guibuilder
URL:
Keywords: RANDOM
Depends on:
Blocks:
 
Reported: 2011-03-01 08:40 UTC by asenk
Modified: 2011-09-08 16:12 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 asenk 2011-03-01 08:40:25 UTC 
Product Version: NetBeans IDE Dev (Build 201102280001)
Java: 1.6.0_24; Java HotSpot(TM) Client VM 19.1-b02
System: Linux version 2.6.32-24-generic running on i386; UTF-8; en_US (nb)
 

Start IDE with clear userdir. Create new project, Java Application (e.g. MyApplication) and create a new form (e.g MyJFrame).

         1. Layout - Change Layout to AbsoluteLayout.
         2. Add - Add two JPanels, add several JButtons and other components to JPanel1,JPanel2,top container.
         3. Layout - Change Layout in JPanel1 to GridBagLayout.
         4. Resize, move - resize and move JPanel1, JPanel2. 
         5. Add some other components and change their properties
         6. Undo - undo all changes.
         7. Redo - redo all changes. - in inspector is everything ok, all changes are going back. In Design form are some Redo changes missing (some buttons or labels aren't added etc.)

This bug is random.
Comment 1 Jan Stola 2011-09-08 16:12:35 UTC 
I am sorry, I am not able to reproduce this issue and the description gives no clues what can be wrong. If you are still able to reproduce this bug, please, try to provide as much additional information as possible. Also check for potential exceptions being thrown during Undo/Redo. I am closing this issue as not reproducible for now.

BTW, I doubt that this issue is random. All algorithms that we are using are deterministic and since almost all relevant code runs in one thread there is also just a minor chance of this bug being caused by some race condition. More probably there is some additional necessary condition (that is maybe hard to spot/identify).