+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Bug report MC-412

Arrow Point Centering

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

Most of the arrow styles (especially the wider ones) are out of center. For users who make trades based upon multiple levels of waves and they mark those wave tops and bottoms with arrows which are found on the chart via binary searches for input into their programs it creates a problem (a problem because they must be placed accurately and if the point is out of center it is easy to miss place the arrow).

In the picture attached, you can see that the wider arrow is shifted the other way in MC 7.0 (the point of the arrows is to the right of the bar rather than pointing exactly at it dead on). In the prior releases it was actually shifted the other side of the bar. The smaller arrow is perfect now (in the prior releases it was out of center on the left a tiny bit). In the prior release it was only the up arrows that had the problem. For me it creates a bit of a problem because I am forever going back to see if I have the arrow positioned properly so I get the correct information I want for that particular bar submitted into my program logic. If I visually misread it it creates a problem. I have in the past had the logic try and find the top or bottom but that creates a problem so I decided to change it back so I have to get it dead on manually. So essentially this problem slows me down. So for TSS to test this you have to zoom in on the bars so it is very easy to see and when the arrow snaps to the bar (because of the very wide zoom) you can very easily see that the graphics has to be redone. I added a second arrow of the same style from a different bar size and this arrow is pointing down. The shift is the same (to the right).

Steps to reproduce this issue

Revised for Beta 5 after some sort of attempt at a fix was made and released:

Note: I can see there is some sort of problem instantly when I put an arrow on the chart with no zoom. I just can not tell exactly what is wrong until I do this new procedure which now has the addition of the magnifying glass to inspect it.

==Faster Method to see the problem:================================
These instructions are also in the attached picture called "MagnifyGlassExample"
The best way to see the misalignment is to:
**put an arrow shown in the picture on the chart.
**put it above a bar that sticks out.
** zoom the chart way way in.
**Go a step farther and get a magnifying glass.
**Put the cross hair up so it runs direclty through the price bar.
**notice that the line of pixel dots the cross hair runs through on the arrow.

**You will see that the cross hair runs through the wrong line of dotes.

==Slower Paint Brush  Method to see the problem========================
NOTE: These instructions are also in the picture called "BMP StretchScewExample"
NOTE: My png examples can be converted to BMP by choosing edit.
**In MC zoom the chart where the arrow is.
**Place the down arrow close to the top of the bar (invert for an up arrow).
**Save the picture in BMP format (make sure arrow is in top left of the chart area).
**Pull the bmp picture up using MS paint brush.
**Use Menu Stretch/Scew and adjust Horizontal and Vertical up to 500.
**Again in Paint Brush use Menu, View, Zoom, Large Size then inspect the arrow.
**Also in Paint Brush (after Large Size Is Selected) set Menu View, Zoom, Show Grid.
**It is clear that the dots that make up the arrow are not lined up with the price bar.

Comments (1)
Issue basics
  • Type of issue
    Bug report
  • Category
  • Targeted for
    MultiCharts 7.0 (RELEASED)
  • Status
  • Priority
    Not determined
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
  • Reproducability
    Not determined
  • Severity
Attachments (6)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates