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

make once keyword persist thru reloads & symbol changes

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

Please change the operation of the "Once" keyword to only execute the one time it is called per use in the current MultiCharts process instead of every time data is reloaded.

I understand "Once" needs to adhere to the EasyLanguage legacy meaning from where it originated, however:
1. It is trivial to program that same logic functionality of executing one time per new symbol or data reload (without "Once") using existing PowerLanguage boolean flags.
2. It is currently impossible to run a "CommandLine" statement in indicator code which will reload data on the chart without repeating in an infinite loop.
once CommandLine(".rld int = 1 day"); // executes constantly in indicator code, so why have it?
3. The intuitive lexical meaning of the word once does not contain a bunch of clauses where it is allowed to repeat after certain actions. Once means literally one time only.
4. There is no other way even using Global variables that will save state after chart reload or symbol change.
5. Making this change to "Once" is the easiest way to have variable memory persistance without having to add a whole new data type or other difficult change.

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
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