SaveAsCapability: For Editor Mode Only
By Geertjan-Oracle on Jul 13, 2010
Hence, unless the Node is displayed in a TopComponent in "editor" mode, the SaveAsAction will never be enabled. That's a bit unfortunate. The assumption seems to have been that the SaveAsAction can only be relevant to documents. However, in this case, I'd like to use the "Save As" dialog for a changed Node. Once the explorer view rendering the Node is in a TopComponent in "editor" mode, everything is fine—by adding the SaveAsCapable to the Node at the time when the Node had changed, I am able to enable the SaveAsAction.
Maybe I should create an issue for making the SaveAsCapable relevant to other modes too. Or I will need to create my own Action that is sensitive to SaveAsCapable.