+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-877

New Feature defaults (new releases act exactly as left off in prior install)

action_vote_minus_faded.png
5
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

Quote: I think the safest thing for MC to do with new features, is to have the default = OFF.
In other words regarding new features (in almost all cases) they should not replace old features but be in addition to them. This basically means that when a user installs a new release MC should act exactly as it did on the prior release they had installed (traders do not like unexpected surprises in the market nor in the software installs). It should also remember their last option settings. They will know a new feature is in place because they will be tracking it on the bug tracker and get a notice that it is released. I do not think you will find anyone on the planet complaining that they have to turn the new feature on. This procedure is an industry standard I think (if not it should be).
...
As an example, the old standard of execute on the end of bar is the default and the user has to turn on the execute on every tick. If the new execute on big/ask is put in place the original standard of execute on end of bar will still be the default and it will never be lost as a feature of MC.
....
As another example, I have requested that the chart background double click be removable as an option. The default should be as it is now and I have no problem with having to go in and adjust the option so I do not have to repeatedly close that window down during the day. It is not fair on the traders who use this feature to take it away from them then force them to have to turn the feature on that has been there for years already. In some examples the trader will be forced to have to roll back which wastes at least 1 to 2 hours of their time (especially bad if they do not get the unexpected behavior until mid trading day). 
...

Steps to reproduce this issue

These were done incorrectly. _
1/ Option: window right margin - percentage or bar fixed(default) - we are going to implement this. Everything else is not confirmed.
_2/ Option: skipping same price ticks or not (not as default since it is industry standard)

3/ Option: MC_TL/Arw/Text)_GetActive set (default does not really apply here).
4/ Option: Chart trader button: default is hidden, it should be an option to show it.
Regarding #4. Users who do not use the chart trader are often having to close it down (which costs them time). I expect I have to close this down about once a week at least. This is unexpected behavior and the first time they see it especially they have to try and figure out what the heck it is (not good). You can just imagine a trader who is about to take a trade and this window popups up which they have never seen before (and they never want to see it again). You may find that most traders in that situation miss that trade.

Comments (6)
#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Mar 22, 2012 - 09:45

Johnm, do i understand you correctly that you have cancelled the feature request?

#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Mar 23, 2012 - 07:42

Please, review edited "how to reproduce" for further details.

#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Mar 23, 2012 - 09:22

John, at the moment we prefer to leave all new features turned on by default to let new customers know about them + many of new features help to resolve issues from previous versions.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    MultiCharts 8.0 (RELEASED)
  • Status
    Partially Implemented
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
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