Need Broader Space within Top and Bottom of Chart Window

Rounder1

#1

6/12/2014 3:30 PM

How would one view/create more real estate within the top and bottom area of a chart window?

The stock name and description ribbon at the top of the chart window often obscures candlesticks when values reach the upper limit of the frame (bullish trend). Also, more chart real estate would be useful for drawing and viewing stop limits where resistance levels and converging trends are dynamically off scale and beyond the current "Y" axis boundary by barely a percentage grade.

To view this chart real estate for drawing symbols (head-shoulder or stop limits) requires compression of the timeline, but the chart detail then becomes too small to work with.

I've searched the forum and user manual, but can find no help for adjusting the "Y" axis for a better boundary work area.

Eugene

#2

6/12/2014 4:57 PM

Font size trick:

Remove PricePane label?
Get Rid of Label on PricePane

SetPaneMinMax:

Is it possible to extend the height of a chart?
Margin at Chart Top

Cone

#3

6/13/2014 5:18 AM

On a deficiency note, when using semi-log scale, the automatic scaling does not provide adequate headroom. It can be solved worked around with SetPaneMinMax() however.

Rounder1

#4

6/13/2014 11:25 AM

The code for SetPaneMinMax would be most functional -- adding 10% of the highest value. But after compile, it throws system warnings and "bar" definition conflicts when used with CMO strategy. I've pasted the strategy below along with the SetPaneMinMax code.

Thanks...

CODE:
Please log in to see this code.

Size:

Color:

The code for SetPaneMinMax would be most functional -- adding 10% of the highest value. But after compile, it throws system warnings and "bar" definition conflicts when used with CMO strategy. I've pasted the strategy below along with the SetPaneMinMax code.

Thanks...

[code]using System;			
using System.Collections.Generic;			
using System.Text;			
using System.Drawing;			
using WealthLab;			
using WealthLab.Indicators;			
			
namespace WealthLab.Strategies			
{			
    public class CMOSignalsWithProfitTarget : WealthScript			
    {			
			
		StrategyParameter oversold;	
		StrategyParameter overbought;	
		StrategyParameter cmoPeriod;	
		StrategyParameter profitTarget;	
			
		//Pushed indicator StrategyParameter statements	
		private StrategyParameter slider1;	
		private StrategyParameter slider2;	
        public CMOSignalsWithProfitTarget()			
        {			
			//Pushed indicator CreateParameter statements
			slider1 = CreateParameter("SMA_Period_1",50,2,200,20);
			slider2 = CreateParameter("SMA_Period_2",200,2,200,20);
			oversold = CreateParameter("Oversold", -50, -70, -40, 10);
			overbought = CreateParameter("Overbought", 50, 40, 70, 10);
			cmoPeriod = CreateParameter("CMO Period", 20, 5, 10, 1);
			profitTarget = CreateParameter("Profit Target", 10, 5, 10, 1);
        }			
			
        protected override void Execute()			
        {			
			int b = ChartStyle.LeftEdgeBar;
			int bar = Bars.Count - 1;
			double top = Highest.Value(bar, High, bar - b);
			SetPaneMinMax(PricePane, Close[bar], top * 1.1);
			
			PadBars( 10 ); // Leave 10 bars of blank space on the right of the chart
            int lastBarBought = 0;			
            PlotStops();			
			
            //Get parameter values			
            int period = cmoPeriod.ValueInt;			
			double target = profitTarget.Value / 100.0d + 1.0d;
            int oversoldLevel = oversold.ValueInt;			
            int overboughtLevel = overbought.ValueInt;			
			
            //Create and plot CMO indicator			
            CMO cmo = CMO.Series(Close, period);			
            ChartPane cmoPane = CreatePane(40, true, true);			
            PlotSeriesOscillator(cmoPane, cmo, overboughtLevel, oversoldLevel, Color.Green, Color.Red, Color.CadetBlue, LineStyle.Solid, 1);			
			
           //Trading system loop			
            for (int bar = period + 1; bar < Bars.Count; bar++)			
            {			
                //Buy when CMO crosses above oversold level			
                if (CrossOver(bar, cmo, oversoldLevel))			
                    if (LastActivePosition == null || LastActivePosition.EntryBar > Bars.Close[bar])			
                        if (bar >= lastBarBought + 9)			
                        {			
                            BuyAtMarket(bar + 1, "CMO Oversold");			
                            lastBarBought = bar + 1;			
                        }			
                //Exit rules			
                foreach(Position pos in Positions)			
                    if (pos.Active)			
                    {			
                        if (CrossOver(bar, cmo, overboughtLevel))			
                            SellAtMarket(bar + 1, pos, "CMO Overbought");			
                        else			
                            SellAtLimit(bar + 1, pos, pos.EntryPrice * target, "Profit target");			
                    }                			
            }			
			
			//Pushed indicator PlotSeries statements
			PlotSeries(PricePane,SMA.Series(Close,slider1.ValueInt),Color.FromArgb(255,0,128,64),LineStyle.Solid,2);
			PlotSeries(PricePane,SMA.Series(Close,slider2.ValueInt),Color.Red,LineStyle.Solid,2);
			
        }			
    }			
}			
[/code]

Eugene

#5

6/13/2014 12:08 PM

Yes it conflicts - this is what one gets for a simple copy & paste act. To fix, you can:

1. either use a different variable name for your "bar" variable

CODE:
Please log in to see this code.

2. or turn the now conflicting 2nd definition into an assignment:

CODE:
Please log in to see this code.

Try to read the warnings that compiler is throwing at you, notice the line number, Google the error message to get more information from MSDN and other sources. Since this is programming 101 (not even C# specific), please consider starting by e.g. resources quoted in this FAQ: How do I start with C# ?

Rounder1

#6

6/14/2014 12:53 AM

Thanks, Eugene,

Sigh... I'm out of my depth here, and I apologize. Fidelity suggested this program as an excellent tool for testing and charting 'out-of-the-box' strategies. It works more than well enough as is despite the lack of padded real estate at the top and bottom of the chart window.Tech support recommended I post the question here since the tech, himself, wasn't knowledgeable as a programmer/developer either. This squawk is a minor issue I can live with.

Cone

#7

6/14/2014 1:30 AM

No problem Rounder1. If you need some help with code, you're at the right place. :)

Eugene

#8

6/14/2014 2:03 AM

Got your point John. Simply change your code like that:

CODE:
Please log in to see this code.

Rounder1

#9

6/14/2014 4:50 PM

Thanks, Eugene!

Worked perfectly.

If you find yourself pulling eight sustained G's, in full burner, with a bogie at your six lighting you up with a tracking solution for a high PK splash -- I'm your man. I'll get you out-of-there. I've hurled this body at better than twice the speed of sound and tortured it with countless multi-dimensional hard G tactics in a fighter sporting 138 computers with double-triple redundancy. But if I have to write code for any one of those things to save my life... Just line me up with a blindfold, a cigarette, and lets get it over with.