Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
When workspace is restored at startup, also restore the contents if they are not associated with a file.
Niels and Tariq wanted this feature during development.
The first and second initial End-user also requested this.
Lets keep track of how many users want this feature to evaluate for 11.0.
Here is the third request ...
"I'm submitting this enhancement request based on my knowledge of how the save workspace function currently works (maybe I have it set up incorrectly). Right now if you have a Query Analyzer window that is new and have the save workspace function turned on, it still prompts you to save all documents in an unsaved state. However, a very slick function would be for ADS to do the save 'behind the scenes' to a hidden temp file and do not prompt the user. This way, when the user launches ADS next time, you call the temp files back up so the user doesn't see any difference. When the session is restored, the Analyzer window(s) would still be named 'Untitled' to signify that the window is still in an 'unsaved' state (even though technically you created an instance of the file in a hidden location)."
How does it interact with "Do not prompt to save for new scripts" option?
How does it interact with "Do not prompt to save for new scripts" option?
Also, we could store a modified editor contents if it has no file associated, but what happens when there is a file associated? Since the user may or may not want to save changes, we must present the prompt - and what happens when the user selects 'Save All', but we are in the middle of a shutdown and half the editors are already closed and quietly saved to hidden files?
Also, we could store a modified editor contents if it has no file associated, but what happens when there is a file associated? Since the user may or may not want to save changes, we must present the prompt - and what happens when the user selects 'Save All', but we are in the middle of a shutdown and half the editors are already closed and quietly saved to hidden files?
Missing Requirements :
1. We require to store the temp window data in separate files then any configuration file. Preferably a separate folder for the temp data, and a separate file for each window.
2. We require to make sure that we don't have orphand temp files which never get deleted even after a user closes the tab window.
Functionality to discuss for the first implemenation :
1. If I click to close one window which has text in it, it doesn't prompt to save. We indicated that if we close the application we would not prompt, but we didn't discuss what if the user just closes one tab.
Missing Requirements :
1. We require to store the temp window data in separate files then any configuration file. Preferably a separate folder for the temp data, and a separate file for each window.
2. We require to make sure that we don't have orphand temp files which never get deleted even after a user closes the tab window.
Functionality to discuss for the first implemenation :
1. If I click to close one window which has text in it, it doesn't prompt to save. We indicated that if we close the application we would not prompt, but we didn't discuss what if the user just closes one tab.
editors contents is stored in .datastudio/workspace.dat in plain text.
editors contents is stored in .datastudio/workspace.dat in plain text.
How is the multiple file text stored in workspace.dat? how is the data separated? If the user closes ADS, but then can't restart, how can he retrieve the contents?
How is the multiple file text stored in workspace.dat? how is the data separated? If the user closes ADS, but then can't restart, how can he retrieve the contents?
workspace.dat is a java Properties file. it gets overwritten quite often and contains no user-editable data: this is a part of system.
I am against storing multiple files because file operations take a long time (on a regular HDD), and these files will be saved quite often.
workspace.dat is a java Properties file. it gets overwritten quite often and contains no user-editable data: this is a part of system.
I am against storing multiple files because file operations take a long time (on a regular HDD), and these files will be saved quite often.
1. Open two Frame Windows
2. Open 1 text, html, xml and query window in each
3. Type something in each
4. Close Frame Window on one of them, and you will be prompted to save. choose Discard for each window
5. Close one tab on the still open Frame, and it will not prompt you to save. [This is a BUG]
1. Open two Frame Windows
2. Open 1 text, html, xml and query window in each
3. Type something in each
4. Close Frame Window on one of them, and you will be prompted to save. choose Discard for each window
5. Close one tab on the still open Frame, and it will not prompt you to save. [This is a BUG]
1. Open ADS
2. Open two Text Editors, and add text into each
3. Right mouse click on tab and choose "Close All" ... it closes all without prompting [This is a BUG]
1. Open ADS
2. Open two Text Editors, and add text into each
3. Right mouse click on tab and choose "Close All" ... it closes all without prompting [This is a BUG]
Niels please look in this issue which was already logged. It says the above mentioned behaviour you described is a new requirement ?? https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/6060
Niels please look in this issue which was already logged. It says the above mentioned behaviour you described is a new requirement ?? https://www.aquaclusters.com/app/home/project/public/aquadatastudio/issue/6060
nope, this exact scenario is a bug. I am afraid this legacy code must be finally re-designed.
nope, this exact scenario is a bug. I am afraid this legacy code must be finally re-designed.
Verified the issue logged today - will need to test entire scenario again before closing
Verified the issue logged today - will need to test entire scenario again before closing
Made a change to fix another problem which occurred with 3 open windows. Please test.
Made a change to fix another problem which occurred with 3 open windows. Please test.
Issue #5887 |
| Closed |
| Fixed |
| Resolved |
Completion |
| No due date |
| Fixed Build 10.0.0-rc-13_13 |
| No time estimate |
Here is the third request ...
"I'm submitting this enhancement request based on my knowledge of how the save workspace function currently works (maybe I have it set up incorrectly). Right now if you have a Query Analyzer window that is new and have the save workspace function turned on, it still prompts you to save all documents in an unsaved state. However, a very slick function would be for ADS to do the save 'behind the scenes' to a hidden temp file and do not prompt the user. This way, when the user launches ADS next time, you call the temp files back up so the user doesn't see any difference. When the session is restored, the Analyzer window(s) would still be named 'Untitled' to signify that the window is still in an 'unsaved' state (even though technically you created an instance of the file in a hidden location)."