bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bugs #10026] Gorm doesn't handle changing outlet names well


From: Gregory John Casamento
Subject: [bugs #10026] Gorm doesn't handle changing outlet names well
Date: Wed, 18 Aug 2004 00:23:02 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030821

This mail is an automated notification from the bugs tracker
 of the project: GNUstep.

/**************************************************************************/
[bugs #10026] Latest Modifications:

Changes by: 
                Gregory John Casamento <greg_casamento@yahoo.com>
'Date: 
                Wed 08/18/2004 at 04:18 (US/Eastern)

            What     | Removed                   | Added
---------------------------------------------------------------------------
          Resolution | None                      | Fixed
         Assigned to | None                      | gcasa
              Status | Open                      | Closed


------------------ Additional Follow-up Comments ----------------------------
The issue was in the GormClassInspector.  There needed to be a call to the 
method -[GormDocument removeConnectionsWithLabel:forClassNamed:isAction:] in 
both the data source for the actions table and for the outlets table.   This 
call queries the user to make certain he/she wishes to allow the change before 
replacing the outlet/action in the class and disconnecting existing 
connections.   This is consistent with other functionality in Gorm.  GJC






/**************************************************************************/
[bugs #10026] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=10026>
Project: GNUstep
Submitted by: 0
On: Mon 08/16/2004 at 00:59

Category:  Gorm
Severity:  5 - Average
Item Group:  Bug
Resolution:  Fixed
Assigned to:  gcasa
Status:  Closed


Summary:  Gorm doesn't handle changing outlet names well

Original Submission:  How to reproduce:
  Make a subclass with a couple outlets and set the NSOwner to
that subclass and fill in connections to various objects.  
(I personally had them connected to color wells).

  Then rename one of the outlets on the subclass to 
something else.  Go back to the NSOwner and look at the 
connections list in the inspector.  The connections still 
exist with the old names.  They should either be removed
or even better renamed to have the renamed outlet names.


Follow-up Comments
------------------


-------------------------------------------------------
Date: Wed 08/18/2004 at 04:18       By: gcasa
The issue was in the GormClassInspector.  There needed to be a call to the 
method -[GormDocument removeConnectionsWithLabel:forClassNamed:isAction:] in 
both the data source for the actions table and for the outlets table.   This 
call queries the user to make certain he/she wishes to allow the change before 
replacing the outlet/action in the class and disconnecting existing 
connections.   This is consistent with other functionality in Gorm.  GJC












For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=10026>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/







reply via email to

[Prev in Thread] Current Thread [Next in Thread]