MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+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-2633

PLEditor "Editor Options" - Add Background Color

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 highlighting style editor that pops up when one selects Tool -> Editor Options allows the user to set the foreground and background color for text, keyword, comment, documentation comment, string, and number items.

You cannot set the overall background of the editor. If you set the text background to black, only characters that exist have black backgrounds. The overall space is fixed as white and cannot be changed.

If this behavior was changed to use the text background color instead of a hard-coded white background, this would be useful to me. Otherwise it is kind of pointless as a feature.

I don't mind if I have to reload the entire editor after setting the text background color, just so long as I don't have to do it every time. I would appreciate being able to use a black background when coding.

I know I can get this with Visual Studio, but since I have to use PLEditor to compile, that work flow is really inconvenient.

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