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 40427 - Need API for SaveAction to find name of node to save
Summary: Need API for SaveAction to find name of node to save
Status: RESOLVED DUPLICATE of bug 77210
Alias: None
Product: platform
Classification: Unclassified
Component: Actions (show other bugs)
Version: 3.x
Hardware: All All
: P4 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords: API
Depends on:
Blocks: 36616
  Show dependency tree
 
Reported: 2004-02-24 16:47 UTC by Jesse Glick
Modified: 2011-04-07 06:14 UTC (History)
2 users (show)

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 Jesse Glick 2004-02-24 16:47:26 UTC 
So as to avoid the hack in issue #36616. See
suggestions in that issue, e.g. SaveCookie.Named.
Comment 1 Jiri Rechtacek 2004-04-23 10:50:07 UTC 
Assigned to new owner.
Comment 2 _ tboudreau 2006-01-01 22:05:25 UTC 
A couple thoughts on revisiting this rather old issue:

1.  "File(s) saved" is probably good enough and forget the whole issue of 
needing the name of the file

2.  IntelliJ doesn't even have a Save action;  only Save All.  I tend to think 
that's the way we should go - I can't think of any situation where I want to 
save just one file but not the other modified ones...
Comment 3 Jiri Rechtacek 2008-11-21 16:11:54 UTC 
Not in current plan to fix it
Comment 4 Quality Engineering 2009-11-02 10:56:43 UTC 
NetBeans.org Migration: changing resolution from LATER to WONTFIX
Comment 5 Jesse Glick 2009-11-23 13:52:43 UTC 
We still have SaveAction.getSaveMessage which reflectively calls DataObject.getNodeDelegate rather than relying on a proper interface.
Comment 6 Jaroslav Tulach 2010-11-11 10:22:06 UTC 
Will be fixed as part of bug 77210.
Comment 7 Jaroslav Tulach 2011-04-07 06:14:30 UTC 
The current branch created for bug 77210 contains solution for this problem. I guess it is safe to mark this issue as duplicate now.

*** This bug has been marked as a duplicate of bug 77210 ***