+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Closed Feature request MC-1214

File -> Close Workspace sometimes saves the workspace (but should not)

action_vote_minus_faded.png
1
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
icon_info.png This issue has been closed with status "Declined" and resolution "Not determined".
Description

When prefs are set to:
"Do not show Save Workspaces dialog on exit"  and
"Save Workspaces" 

http://www.multicharts.com/discussion/download/file.php?id=5698

the workspaces are in fact silently saved when the user selects F4, aka File -> Close Workspace.
IOW, under these conditions, F4 and Ctrl-S (aka  File -> Close Workspace, and File -> Save Workspace) behave exactly the same.
IMO, it is illogical for F4 and Ctrl-S to behave the same, and they should not behave the same, ever.

Steps to reproduce this issue

Configure prefs as indicated.   Load a workspace.  Mess it up.  Decide to discard your messed up workspace via F4.    You will find upon reopening the workspace from disk that your messed up workspace was saved despite your instruction (via F4) to discard it.

Comments (2)
#0
user-offline.png  Harvester (harvester)
Jan 10, 2013 - 08:37

I configured the settings as described, and was able to reproduce this.  Agreed - exit should be exit without saving, and save should be save.

#1
user-offline.png  MultiCharts Support (MultiCharts)
Aug 18, 2017 - 20:54
It is not saving a workspace, in case you have "Do not save workspaces" selected in File -> Preferences -> Workspaces tab.
History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates