Bars value doesn't change every tick, does it? Surely ArrayResize() wouldn't have bigger performance penalty if it resizes to the same size comparing to dedicated bit of code that checks the size separately: void start() { int i, t; double atr[]; t ...

I do. A lot.Sure.That's what they invented computers and created programming languages for! Did this many times myself. Please PM me.No problem as well as soon as you define what 'ZigZag reverses' mean exactly.

Alt-I-L-T for a Trendline. Takes less then half a second even for thick fingers. However this merely switches the pointer to a tool drawing mode. What's the problem with clicking corresponding toolbar button if you'll need to fiddle with the mouse ...

indibufferlike array — double atr[]; ... ArraySetAsSeries(atr, false); ArrayResize(atr, Bars); ArraySetAsSeries(atr, true); ... atr[0] = Bid;

high + spread — Long position enters at Ask price that can be higher than High by spread value.

Looks like vista compatibility issue. Find 'compatibility folder' button in the explorer toolbar or whatever it's called, can't remember exactly.

Yeah. First of all divide OHLC values by 10000. Imported bars replace existing bars hence the number of bars can stay the same.

Well, I can make this indicator all right.

The indicator shows three lines. You're just not able to see two others.No, they don't I'm afraid.Examine these two loops please. You populate the same buffer with the same data. Using i+1 and i+2 idoesn't make any sense and causes 'exceeding array ...

It looks like position exit code is never reached as it's located after return(0) statement. Besides OrderClose(OrderTicket(),Lots,Ask,Ask,Red); doesn't make much sense. Position close price depends on the position type: Bid for long, Ask for short. ...

int bid = Bid / Point + 0.5; int last = bid % 1000; int first = bid / 1000;

What does the log in Experts tab show?

http://tvdata.ru/show/tuva_life_and_traditions/T3S_6_215.jpg/151 Only by a lucky chance I'm afraid. The problem is that the fixed point values are stored in floating point type (double) variables. Sometimes it's not possible to represent a fixed ...

Looks like a tambourine dance - a lot of noise with no sense. Actually the transformation of a fixed point value which represents the price to an integer is as simple as this: int spread = (Ask - Bid) / Point + 0.5;

There is no need to recognise the colours. It would be enough to detect the colour change on the boundary. Here is the script. Inputs might depend on the screen resolution. Default parameters work on my 96dpi display.

Agreedcorrection: Right click -> 'Properties' in the context menu -> 'Common' tab -> remove tick from 'Scale fix' checkbox

It's rather bug fixing actually. Could you elaborate on that 1 you add to the spread points please? int spread = ((Ask-Bid)/Point) + 1; Another problem is in the CountPendingOrders() condition. It ignores OP_BUY orders only counting active sell ...

Yep, much better now. Quite possible to implement. Please check your PM.

This is a tricky one. The problem is that the order is activated by server and the client can learn about the event only afterwards. The activation is triggered by price at arbitrary time that means that you need to know the spread at any time. You ...

BTW, pending order can not be triggered by a timer like 'at 6:15 pm'. It's activated when the bid or ask hits order open price.