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

PowerLanguage Editor Far Too Slow, needs multi-threading

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

When entering text into the powerlanguage editor on a fairly long bit of code (a few hundred lines or so of indicator, signal, etc), it is extremely difficult to use because it often takes 5 to 10 seconds for the keyboard input to show up in the editor and frequently takes over one second (on a 2GHz dual-core system). I believe this is due to the various parsing, error-checking, and tip window processes that are going on apparently on the same thread. The editor needs to be brought up to modern standards with this sort of processing going on in a separate thread or at least with keyboard processing having priority because this speed is painful when coding.

Steps to reproduce this issue

Create or open an indicator or signal with lots of inputs and variables that is fairly long, like a few hundred lines.  Add additional code to the indicator, like new inputs and variables and logic and observe how extremely long the editor frequently takes to respond to keyboard and mouse input.

Comments (0)
There are no comments
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Performance
  • 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
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