see attached example.
![]() |
450 B
This gets a bit complicated in the presence of changes in the package editor. To avoid successive dialogs asking to save or discard the changes, and to avoid possible user confusion with opening file in the editor or body editor depending on how many statements are in the file, we are going to do this:
1. add a separate button "Open Package File"
2. if changes were made to either package editor or package body editor, the action will fail with something like 'save your changes first, dummy', but also provide [Disard Changes] button
3. if the file being opened contains 0,1, 3 or more statements, place all of it into package editor, CLEARING the body. If it contains just two statements, place the first one into package editor, the second statement into the body editor REGARDLESS of the actual contents (I assume it is possible to have body statement as a first one).
Issue #4005 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
No fixed build |
No time estimate |
This gets a bit complicated in the presence of changes in the package editor. To avoid successive dialogs asking to save or discard the changes, and to avoid possible user confusion with opening file in the editor or body editor depending on how many statements are in the file, we are going to do this:
1. add a separate button "Open Package File"
2. if changes were made to either package editor or package body editor, the action will fail with something like 'save your changes first, dummy', but also provide [Disard Changes] button
3. if the file being opened contains 0,1, 3 or more statements, place all of it into package editor, CLEARING the body. If it contains just two statements, place the first one into package editor, the second statement into the body editor REGARDLESS of the actual contents (I assume it is possible to have body statement as a first one).