+1 888 340 6572 GET STARTED

Open Feature request MC-911

MC restart option in addition to the shutdown option.

Votes

- No additional actions available

Description

I remember reading somewhere recently that in order to restart MC properly we should use the task manager to make sure all related programs/processes have finished running. If this is actually the case then it would make sense to have a feature in MC that does this for us automatically. In other words we would choose restart and a popup list of steps would come up and show us with a check mark on the left side the steps as they were being completed. Once they were completed the restart would automatically kick in. This would both do it faster than we could ever do it and ensure it was done correctly. Maybe there would be a button on this popup that would allow us to change our mind and shutdown instead of restarting.

Steps to reproduce this issue

N/A

Comments (1)

Toggle system-generated comments

MultiCharts Support (MultiCharts)

MultiCharts Support
Last seen online at Apr 15, 2024 - 17:28
Show user details

Apr 28, 2012 - 12:55

This issue's status has been changed to 'Under Review'.

John Bowles (bowlesj3)

John Bowles
Last seen online at Mar 17, 2014 - 03:31
Show user details

May 02, 2012 - 15:54

I just closed down MC and waited until all MC related processes finish before I ran the updater for the strange backfill spikes. I had a list of processes shown below. I think that if this feature is put in it would be even better if the actual processes that need to be checked for and that are still being waited for are listed (the ones below). Maybe the word "Waiting to terminate" could be put in front so the user knows. My thinking is that by having the list the user will be better aware of these processes. In the past I always closed MC and brought it up very fast not realizing these would be running. In the case of running the updater I sill needed to know they were clear before I could run it so even the full shut down process could list them and I personaly would make use of this.
MultiCharts.exe
MessageCenter.exe
QuoteManager.exe
tsServer.exe
PLEditor.exe
StudyServer.exe
TradingServer.exe
atCenterServer.exe
TPserver.exe
Fixserver.exe

Edit comment #0

Comment visibility (whether to hide this comment for "regular users")

Comment

Selected syntax: Markdown ▼

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

The Bug Genie uses an enhanced flavor of the markdown syntax, which makes each newline count. If you want to add a linebreak, add a new line and it will be presented just like you type.
See more formatting tips in MarkdownFormatting.

You can use simple formatting tags for underlined text () or strikethrough ().
See more formatting tips in WikiFormatting.

or cancel

Reply to comment #0

Comment visibility (whether to hide this comment for "regular users")

Selected syntax: Markdown ▼

'''John Bowles wrote:'''
>I just closed down MC and waited until all MC related processes finish
> before I ran the updater for the strange backfill spikes. I had a list of
> processes shown below. I think that if this feature is put in it would be
> even better if the actual processes that need to be checked for and that
> are still being waited for are listed (the ones below). Maybe the word
> "Waiting to terminate" could be put in front so the user knows. My thinking
> is that by having the list the user will be better aware of these
> processes. In the past I always closed MC and brought it up very fast not
> realizing these would be running. In the case of running the updater I sill
> needed to know they were clear before I could run it so even the full shut
> down process could list them and I personaly would make use of this.
> MultiCharts.exe
> MessageCenter.exe
> QuoteManager.exe
> tsServer.exe
> PLEditor.exe
> StudyServer.exe
> TradingServer.exe
> atCenterServer.exe
> TPserver.exe
> Fixserver.exe
>

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

Code samples are best presented between two "~~~~"-lines. The Bug Genie uses GeSHi for syntax highlighting with support for over 100 languages! (<source lang="php"><?php echo "fu"; ?></source>)
See more formatting tips in MarkdownFormatting.

If you want to put a horizontal line in the document, use four dashes: "----".
See more formatting tips in WikiFormatting.

or cancel

History

Issue basics

Type of issue

Feature request Unknown issue type
Issue label

No label set
Category

Usability Not determined
Targeted for

Not determined
Status

Under Review

Status not determined
Progress
Priority

Not determined

Affected by this issue (3)

Other
Unknown
- Set status
- Not a bug
- Testing / QA
- Postponed
- Confirmed
- Released
- In Progress
- Partially Implemented
- Can't Reproduce
- Declined
- Won't Fix
- Need Details
- Under Review
- Not Reviewed
- New
- Investigating
- Please wait...
Unconfirmed
7.4
Unknown
- Set status
- Not a bug
- Testing / QA
- Postponed
- Confirmed
- Released
- In Progress
- Partially Implemented
- Can't Reproduce
- Declined
- Won't Fix
- Need Details
- Under Review
- Not Reviewed
- New
- Investigating
- Please wait...
Unconfirmed (7.4.0)
8.0
Unknown
- Set status
- Not a bug
- Testing / QA
- Postponed
- Confirmed
- Released
- In Progress
- Partially Implemented
- Can't Reproduce
- Declined
- Won't Fix
- Need Details
- Under Review
- Not Reviewed
- New
- Investigating
- Please wait...
Unconfirmed (8.0.0)

People involved

Posted by
John Bowles (bowlesj3)

John Bowles
Last seen online at Mar 17, 2014 - 03:31

Show user details
Owned by

Not owned by anyone
Assigned to

Not assigned to anyone
Subscribers

0 subscriber(s)

Click here to show the list of subscribers

Times and dates

Posted at

Apr 08, 2012
Last updated

May 02, 2012
Estimated time

Not estimated
Time spent

No time spent

Click here to see time logged against this issue

Issue details

Resolution

Not determined
Reproducability

Not determined
Severity

Normal Not determined

Attachments (0)

There is nothing attached to this issue

Commits (0)

There are no code checkins for this issue

Child issues (0)

This issue does not have any child issues

Duplicate issues (0)

This issue does not have any duplicates