bugGNUstep - Bugs: bug #16587, Deleting subclass of NSWindow when...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #16587: Deleting subclass of NSWindow when it is assigned as the custom class for a window causes issue

Submitted by:  Nikolaus Waxweiler <madleser>
Submitted on:  Mon 15 May 2006 05:29:02 PM UTC  
 
Category: GormSeverity: 3 - Normal
Item Group: BugStatus: Fixed
Privacy: PublicAssigned to: Gregory John Casamento <gcasa>
Open/Closed: Closed

(Jump to the original submission Jump to the original submission)

Wed 17 May 2006 12:26:57 AM UTC, comment #6:

Yes, the detachObjects: method is recursive. It finds the child objects for a given object and removes them from the document.

Thanks for finding this problem and testing the fix. :) Closing.

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Tue 16 May 2006 03:13:39 PM UTC, comment #5:

Works (SVN revision 22938), even with buttons and NSBoxes with buttons in them. I presume it works recursively. If not, does the interface leak buttons? :O

Nikolaus Waxweiler <madleser>
Tue 16 May 2006 03:04:30 AM UTC, comment #4:

This is corrected in the latest SVN. Please try it now. The correct behavior for this is to remove the window from view if the class it is currently set to is removed (upon comparison with IB). It works this way for Gorm now as well. Please test it.

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Tue 16 May 2006 01:16:34 AM UTC, comment #3:

The workaround for this is to simply set the class back to NSWindow for the object and then delete the class from the classes view.

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Tue 16 May 2006 01:15:31 AM UTC, comment #2:

In the above replace "window controller" with "window class".

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Tue 16 May 2006 01:09:34 AM UTC, comment #1:

Confirmed. Thanks for finding this.

Gregory John Casamento <gcasa>
Project AdministratorIn charge of this item.
Mon 15 May 2006 05:29:02 PM UTC, original submission:

1. New Application.
2. Drag something in the "Window" window (e.g. a matrix of buttons).
3. Subclass NSWindow and set the new class as the window controller (Custom class inspector).
4. Delete the new class (you might need to click something else first and then click NewClass again to activate the "Remove" entry in the "Class" menu).
5. Click the matrix of buttons -> segfault. In other cases, it doesn't crash but you can't drag'n'drop anything or reset the window controller.

Gorm SVN (May 15 18:41), gnustep-back-0.10.3, gnustep-back-art-0.10.3, gnustep-base-1.12.0_1, gnustep-gui-0.10.3, gnustep-make-1.12.0, gcc 3.4.4

Nikolaus Waxweiler <madleser>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 7 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Wed 17 May 2006 12:26:57 AM UTCgcasaStatusReady For Test=>Fixed
  Open/ClosedIn Test=>Closed
Tue 16 May 2006 03:04:30 AM UTCgcasaStatusConfirmed=>Ready For Test
  Open/ClosedOpen=>In Test
Tue 16 May 2006 01:15:31 AM UTCgcasaSummaryAbility to delete currently active window controller provokes crash/wierd behavior=>Deleting subclass of NSWindow when it is assigned as the custom class for a window causes issue
Tue 16 May 2006 01:09:34 AM UTCgcasaStatusNone=>Confirmed
  Assigned toNone=>gcasa

Back to the top


Powered by Savane 3.1-cleanup1