+1 888 340 6572 DOWNLOAD
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-1522

Draw trendline based on each tick increment

Go to the next issue (open or closed)
Go to the next open issue

I'd like to draw trendlines that could only be plotted based on each symbol tick increment.
Taking the ES as example, ES moves every 0.25 points. When drawing a trendline it makes no sense having it at 1788.35 since ES will only trades at 1788.25 or 1788.50.

So my request is to have a keyboard key when pressed while drawing the trendline, this would recognize each symbol tick increment and would only plot based on that increment.

Steps to reproduce this issue

Attached is an image showing the trendline box indicating at which price it is at the moment I'm moving it. It's indicating 1793.38. When moving it, it should only move to 1793.25 or 1793.50.

Here is a video I made showing that I'm always forced to go to the trendline properties to have it exactly at the price I want it.


Comments (1)
user-offline.png  arnie (arnie)
Nov 19, 2013 - 14:10

I forgot to add another feature. When drawing a horizontal line, it woiuld be nice to see the actual line and the price at which it will be plotted before we plot it for better viewing. The way it is right now I'm always editing it so it's plotted at the precise price I want it.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Not Reviewed
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
  • Posted by
    user-offline.png  arnie (arnie)
  • 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
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates