[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #16587] Ability to delete currently active window controller provok
From: |
Nikolaus Waxweiler |
Subject: |
[bug #16587] Ability to delete currently active window controller provokes crash/wierd behavior |
Date: |
Mon, 15 May 2006 17:29:03 +0000 |
User-agent: |
Opera/8.54 (X11; FreeBSD i386; U; en) |
URL:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=16587>
Summary: Ability to delete currently active window
controller provokes crash/wierd behavior
Project: GNUstep
Submitted by: madleser
Submitted on: Monday 05/15/2006 at 17:29
Category: Gorm
Severity: 3 - Normal
Item Group: Bug
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
_______________________________________________________
Details:
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
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=16587>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #16587] Ability to delete currently active window controller provokes crash/wierd behavior,
Nikolaus Waxweiler <=