I'd like an option so that invisible plots do not effect chart scaling. As it is now, they do, and the only way to fix it is to remove the plot from the code. Not efficient.
I can see how it may be useful in some cases to leave the result as-is. But, I'd like to add a new option "Invisible+no scaling" for instance to get my desired behavior.

Steps to reproduce this issue

Nothing entered.

Add plots. Make them invisible. If the plot is far enough away from price, it will scale the chart even though it is invisible.

For invisible plots not to affect scaling would be OK (and desirable, I suppose) as an option, but never forget that the primary reason for developers to make invisible plots in the first place is EXACTLY for the purpose of affecting the scaling. So, if you change anything here, be sure not to break it!

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

Code samples are best presented between two "~~~~"-lines. The Bug Genie uses GeSHi for syntax highlighting with support for over 100 languages! (<source lang="php"><?php echo "fu"; ?></source>)
See more formatting tips in MarkdownFormatting.

If you have certain text you don't want to be formatted, enclose it in tags: "'''formatted''' text '''non-formatted''' text.
See more formatting tips in WikiFormatting.

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in MarkdownFormatting.

If you want to put a horizontal line in the document, use four dashes: "----".
See more formatting tips in WikiFormatting.

To auto-link to an existing issue, write "issue", "bug", "ticket" or the issue type (like "bug report" or "enhancement") followed by the issue number (ex: "ticket #3" or "bug report MYPROJ-1"). Enclose sourcecode samples between two "~~~~" lines.
See more formatting tips in MarkdownFormatting.

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

If you have certain text you don't want to be formatted, enclose it in tags: "'''formatted''' text '''non-formatted''' text.
See more formatting tips in WikiFormatting.

Actually, I imagine the most common reason for invisible plots is to provide additional information to the user in the data tips / data window, such as slope measurements and other convenient calculations.

Don't worry about URLs - they will automatically be transformed to links.
See more formatting tips in MarkdownFormatting.

The Bug Genie uses an enhanced flavor of the markdown syntax, which makes each newline count. If you want to add a linebreak, add a new line and it will be presented just like you type.
See more formatting tips in MarkdownFormatting.

To create a bulleted list, start one or more lines with a star ("* bulleted list item"). You can create a numbered list by using the hash/pund sign instead ("# numbered list item").
See more formatting tips in WikiFormatting.