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 8970 - View | Source Editor menu item disabled for some object types
Summary: View | Source Editor menu item disabled for some object types
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P3 normal (vote)
Assignee: Vitezslav Stejskal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-12-21 15:08 UTC by Jan Chalupa
Modified: 2008-12-22 20:46 UTC (History)
1 user (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 Jan Chalupa 2000-12-21 15:08:17 UTC 
The View | Source Editor menu item is supposed to be enabled when the Source
Editor window is open. However, the item is disabled when the window displays
only panes with the following file object types:

Ant Project Files
Image objects
Properties objects
Textual objects

The item is enabled if there is at least one file of type Java or HTML open in
the Source Editor.
Comment 1 Jesse Glick 2000-12-24 14:24:59 UTC 
I believe this is fixed in the trunk, please verify.
Comment 2 Jan Chalupa 2001-01-09 11:10:59 UTC 
It seems to be fixed for Ant and Text files. For Image and Properties files the
Source Editor menu item is still disabled. [NetBeans-dev-99]
Comment 3 Jan Zajicek 2001-01-10 14:54:59 UTC 
Verified, fixed in trunk (Dev version Build 100), works in the FFJ20 too, so
I'll close this bug.
Comment 4 Jan Zajicek 2001-01-10 15:06:59 UTC 
My apologize for confusion, the bug still remains for Image and Properties
files!
Comment 5 Jesse Glick 2001-01-15 11:52:59 UTC 
org.netbeans.core.actions.EditorViewAction looks for opened instances of
CloneableEditor. Image files will never qualify, and I am not sure they *should*
be opened by this action (it is not the Editor, is it?). I'm not sure why
*.properties would not work, unless WMImpl.reactivateWhatever(Class) looks for
exact instances and not subclasses (properties module subclasses
CloneableEditor).
Comment 6 Jan Chalupa 2001-03-12 09:36:12 UTC 
Version: 'Dev' -> 3.2
Comment 7 David Simonek 2001-04-02 11:04:56 UTC 
Reassigning to Vita.
Vita, this problem may be hard. (and it's in core = hardcore :-)
reactivation is done via core.windows.WindowManagerImpl.reactivateComponent.
WMImpl has a machanism to keep map of components that were activated and their
classes (methods registerComponent, unregisterComponent).
Error appears only for properties and images.
Editor view action is represented by core.actions.EditorViewAction.
Comment 8 Vitezslav Stejskal 2001-04-04 20:03:29 UTC 
Map of last activated components was removed, instead of it there are
functions findContainer(mode, workspace) looking for the TopComponentContainer 
associated with given mode and workspace. Then findContainer is used
in EditorViewAction and ExecutionViewAction to recall specified
window from current workspace (if exists). If the window doesn't exists in 
current workspace it is searched on other workspaces. EditorViewAction is 
enabled if there is at least one Source Editor window on any workspace.
ExecutionViewAction is always enabled and always docks ExecutionView component 
into the EXECUTION mode.

fixed in 3.2, dev
Comment 9 Jan Chalupa 2001-05-05 20:55:10 UTC 
Target milestone 3.2
Comment 10 Quality Engineering 2003-07-01 16:46:35 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.