MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+1 888 340 6572 GET STARTED
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-623

Intrabarpersist warning and assist at initial variable definition time.

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

Taken from this link
http://www.multicharts.com/discussion/viewtopic.php?f=1&t=7567#p43814
and related to this PM links
http://www.multicharts.com/pm/viewissue.php?issue_no=MC-621
Why not have your compiler give a popup when the user completes their variable definition, It would say "Do you want IntraBarPersist to ensure new ticks do not zero out this variable". It would save them typing and I will admit, I do not like typing IntraBarPersist over and over. I do not care much for having to cut and paste it too even though that is a bit faster. Obviously the compiler needs to know if this study runs as "execute on every tick". The problem with this idea is the TL_new problem. It has no way of knowing if this is the ID for a chart object creation command. Maybe the popup could include "Not recommended for variables that store the ID of TL_New, Text_New, Arw_new".
One last consideration. Consider a shortform for IntrabarPersist such as IBP. Most users will appreciate the reduction in typing.
If this suggestion goes in consider this idea for turning warnings off then on again.
http://www.multicharts.com/pm/viewissue.php?issue_no=MC-495

Steps to reproduce this issue

N/A

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
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