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 21959 - a buffer opened in XEmacs with openflag as true is not installed in built-in source editor
Summary: a buffer opened in XEmacs with openflag as true is not installed in built-in ...
Status: RESOLVED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: externaleditor (show other bugs)
Version: 3.x
Hardware: Other Other
: P3 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on: 20910
Blocks:
  Show dependency tree
 
Reported: 2002-03-29 02:45 UTC by Melih Ovadya
Modified: 2002-07-19 15:19 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Melih Ovadya 2002-03-29 02:45:51 UTC
When one opens a document in external editor and wants to 
mount it to the IDE, the created JEditorPane for that 
document is never installed in built-in editor window. 
That creates several problems:
* inconsistent with the behavior when one opens a document 
from IDE
*since the JEditorPane is not installed, actions cannot be 
invoked on them (i.e. toggle breakpoint)

There is a possible solution for this which depends on two 
currently open issues:issue
#20910 and issue #7551.
Here are the steps:
1)Assuming issue #7551 is fixed, we can ask the IDE  to
select a node in the explorer
2) This will mount the filesystem (if not mounted), expand 
the filesystem-tree, select the file
3)we can get that node and invoke the OpenAction on that 
file
3) Assuming issue #20910 is fixed, IDE calls  the 
VetoableOpenListener in our EditorKit.
4) Our listener function returns false, and this  should 
abort the Open. The EditorKit would then create a 
JEditorPane for the external file and ask the Editor to 
display that instead.

At that point, it will act like a file opened by IDE.
Comment 1 Melih Ovadya 2002-04-17 00:17:15 UTC
With the latest changes, we now get the original DataNode, 
call the OpenCookie action on it and initialize the 
ExtEdDocument with the content of the external editor 
buffer's.  This fixes this problem.