Kbase P126353: Cannot open section editor for a new Window in Architect
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/22/2007 |
|
Status: Unverified
FACT(s) (Environment):
Windows
OpenEdge 10.x
SYMPTOM(s):
Cannot open section editor for a new Window in Architect
Editor perspective doesn't open when clicking Edit Code in the AppBuilder for new window
Cannot see code for new windows in the AB in Architect
CAUSE:
When a new object is created in the AppBuilder perspective, in OE Architect, you cannot access its code sections, or source code for the object, until you've initially saved it.
This happens because the editor in OpenEdge Architect requires a resource file for most of its functionality. The Eclipse approach is that you create a resource in a project then you edit it. This approach is different than the one presented by the AppBuilder and the Procedure Editor.
If the new file is saved as a project file in the corresponding project, then the file is opened in the editor and file synchronization can be done (changes in the editor are reflected in the window window in the AppBuilder and vice versa).
If the file is not saved in the project associated with the AppBuilder then the file is considered external and an editor is not opened.
Even though this limitation can be resolved by using a temporary file (the editor is no longer limited to project files) or using a string buffer instead of an actual file for input to the editor, implementing this behavior would not be consistent with the Eclipse approach.
A more consistent approach is to create actual files in the project and then edit them in the AppBuilder.
FIX:
Save the file to a temporary filename in the project and if you later want to discard or rename it, remove the temporary copy.