+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
Open Feature request MC-1080

Option for confirmation prompt when closing MultiCharts

action_vote_minus_faded.png
9
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
Description

Currently, there is no option for a prompt for confirmation when closing MultiCharts.
Unchecking Do not show "Save Workspace" dialog on exit is no workaround, since I usally have more than 20 workspaces open and would have to confirm the close of each workspace when closing MultiCharts, if this option would be unchecked.
I feel that it is an industry standard that there must be an option to prevent an unintentional shut down of productivity software.
So, in addition to the existing options for confirmation prompt when closing workspaces and windows, a third option "Prompt for confirmation when I want to exit MultiCharts" , or alternatively, "Do not prompt for confirmation when I want to exit MultiCharts"  should be introduced.

Steps to reproduce this issue

 refer to the description above 
 

Comments (3)
#0
user-offline.png  janus (janus)
Sep 24, 2015 - 06:10

This is such a simple but very important request.  I've accidentally closed MC a few times.

#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Jan 20, 2016 - 08:18

Please enable "Save Workspaces" dialog, as it is functioning the same way.

#0
user-offline.png  tepim (Guest)
Jan 20, 2016 - 08:28

Please reconsider the decision to decline this issue. Enabling the "save workspaces" option does NOT have the same function, as I have to confirm the dialogue for EVERY single workspace. This is quite tiresome if you have 10 or 20 workspaces open...

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
    Critical
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates