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

TL_Persist, Text_Persist, Arw_Persist

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

The Regular TL_New, Text_New, Arw_New commands (and the _s versions etc) all keep deleting the object until BarStatus = 2 becomes true. Once BarStatus=2 becomes true the line stays there. This is extremely confusing to new MC programmers especially if you grad the ID created from these commands and think you can use it to delete the object later. You can't because you can never be sure if this ID will hold until the BarStatus=2 is true. Not only that it is an error to use IntraBarPersist on the ID because it could retrain the number even though it will later change at the BarStatus=2 point (this is hard to explain and I am not even sure I understand it but I tried using IntraBarPersist and all of a sudden my study stopped working).
So for sure the original commands have to be kept as it (kind of obvious). However new commands as I show in the subject line that retain the object even if it is created mid bar would be very helpful for the new programmers. The documentation needs to explain the difference between the old and new commands and explain the tricky problem that is created with the old commands. Of note, the new commands need to some how force a compile error if the ID does not have IntraBarPersist on it. This is because if the object is held and it has submitted an ID number back to a variable for later deletion that needs to be held just like the object is held. If IntraBarPersist is not there the next tick will set that ID back to value zero and this will really cause problems for the programmer. Again this needs to be explained properly in the help.

Steps to reproduce this issue

I think this like has some code to help reproduce the problems in the old commands.
http://www.multicharts.com/discussion/viewtopic.php?f=1&t=6785&hilit=bowlesj3
If not I may be able to find another one that does.

Comments (4)
#0
user-offline.png  Yves BENOIT (Yves BENOIT)
Dec 06, 2012 - 01:39

At minimum, information should be added to help, wiki, etc... saying that:
TL_New... and Arw_New... commands are not functional intrabar,
They work only if they are launched when BarStatus=2.
I spent hours trying to understand why arrows and texts did not appear on the chart.

#0
user-offline.png  Guest user (guest)
Dec 06, 2012 - 15:39

I guess I should update the Wiki with these two links.
. . 
http://www.multicharts.com/discussion/viewtopic.php?f=1&t=10571

. . 
http://www.multicharts.com/discussion/viewtopic.php?f=1&t=6785

. .
I updates the IntraBarPersist if I remember but never thought to update the TL_new etc. It is on the todo list.

#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Jan 28, 2013 - 16:10

[RecoverDrawings = false] should help

#0
user-offline.png  John Bowles (bowlesj3)
Jan 28, 2013 - 17:14

Thanks Andrew. I will have to download the beta 2 and check it out. Most of my code in MC is finalized but every so often I put a new drawing object out. I will see if I can find something on my todo list to test it with so it will be a long term test.

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targetted for
    MultiCharts 8.5 (RELEASED)
  • Status
    Released
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
    Normal
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