Best posts made by PhiLykia

Hello friends, there are often questions in the forum about how to use the color change of an indicator as a signal.

As you know, the color change is created in the indicator as a result of a calculation. If we can assign this calculation result as a value along with the color to a separate buffer (although it already exists but is not available as a buffer), you can use it as you wish.

Let's now examine how to do this.

(First of all, be sure to save your indicator under a different name. We don't want to lose its original state.)

First, let's open the indicator with IDE.

Let's add buffer with a new name to the buffer definitions under OnInit. I used the name buffer_value as an example. Use the sequence number when adding a new buffer.
(the following number is 3 in the example).

We increase the number of available buffers by one. Along with this, we also increase the number of buffers to be displayed by one.

In addition to the existing buffer definitions, we add a newly named buffer definition.

Our buffer definitions are finished. Now let's make this buffer get a value:

Again, we determine the name of the INDICATOR_COLOR_INDEX buffer in the buffer definitions under OnInit. In this example "valc"

We go to the calculation section in OnCalculate and find the valc calculation (assignment).

What we are looking for is here, the result of Level Up and Level Dn:
((val[i]>inpLevelUp) ? 1 : (val[i]<inpLevelDown) ? 2 )

Compile the code you edited and start using it. While there was only one buffer listed before, two buffer options will appear after these operations.

If the buffer value = 1, you can use it as an increase, and if it is 2, you can use it as a decrease.

Unfortunately, I could not get any comments or solutions from the relevant people regarding the "Compilation errors" problem in FxDreema.

It was up to me to come up with a solution:

If there are "enum" inputs in the indicators you use and FxDreema does not support this, you will receive this error. All you do is use the indicator without implementing enum variables.

However, using the indicator without enum variables often leaves the indicator meaningless.

This is the error you will get in FxDreema if you use enum variables:

Let us solve the problem that FxDreema cannot solve ourselves. Save your project without enum variables and open your saved project with the IDE editor.

Here are the enum options in our code:

Manually define your enum in input fields:

This is what the variables for your indicator look like:

Also change the enum variable as follows:

Save your project and open it in Metatrader Strategy Tester. Here are the enum variables that you cannot create with FxDreema.

@Nathan2018 @tec-nacks https://fxdreema.com/shared/yMrG9iJMd

As a result of my studies, I saw that some indicators are indicative and some are supportive. How does?
I have studied hundreds of indicators and oscillators over time. I would like to explain how I elaborate on the indicators and oscillators that I have studied, and how I use them in an EA. Maybe my goal is to give someone a clue.
(Sorry for my English, I will have mistakes, forgive me)

Let's start with a random indicator, for example the WSO&WRO indicator.When we apply it to the chart, we see this:

What should the indicators be doing for us? should show the entry and exit points of the position perfectly.
Here are the points I want in this indicator:

What dots do these dots correspond to on the indicator? I see that when both buffers meet at the same point (0 and 100) it should generate a signal to me.

If the two buffer outputs are at the same level, close in case of open position opposite.
https://fxdreema.com/shared/cUCaIgHic

this is the result of this EA:

Here is the trading report:

when we remove the "no trade/position" block from this EA:

If we apply a grid system, the EA is like this:
https://fxdreema.com/shared/Bn9S4PwEd

As a result, the WSO&WRO indicator is a "decisive" indicator. but it cannot produce a perfect trade report by itself. in this case we need to develop this indicator with "supporting" indicators.
Separate your indicator pool in these breakdowns, it will be of great benefit.

I tried to briefly explain the determining indicator, I would like to talk about supporting indicators in my next post.

Hello, It is positive that updates are made to the application and that it continues to be developed. I am sure that the stable operation of the application is very important for all of us. It is undesirable for an EA that is currently working to not be working after development. We are ready to provide testing support in this regard, if necessary.

Among the indicators, Moving Avg, Price Type, Time Frames, etc. are included in the standard library. It is important that we also use the special parts we coded.

This is a problem for me if I am going to update the code that I have compiled in FxDreema on the IDE. I hope the developers resolve this quickly or suggest alternative solutions.

@Nehemiah7 @Nathan2018
https://fxdreema.com/shared/lcxWYJ3Vd

Let's see if we can achieve the "perfect" Expert Advisor using the indicator we took as an example.

In this indicator, there are 6 zones with a range of 16.66. Let's see, what happens if you open a high lot BUY on R0B5, a low lot BUY on R1B4, a low lot SELL on R4B1, and a high lot SELL on R5B0?

Positions will only be opened at these levels, and outside this level is close position.

@fxDreema Problems continue, especially in compiling multi-time frame indicators. Can you provide an explanation or solution suggestion on this issue?

Example of the problem: In codes containing MTF, it is necessary to define this as a variable to call the data of the time frame. But since we cannot use this variable, we cannot work with these indicators.

#define _mtfCall iCustom(_Symbol,timeFrame,getIndicatorName(),0,inpx,inpy)

@danyz1989 (it doesn't matter though. pineconnector runs a pinescript.) magic number ok, so group name/number, does it match? Did you sync using "strategy.group()" included in Pinescript?

// Open Order
if condition
strategy.entry("Buy", strategy.long)
if bar_index % 2 == 0
strategy.group("Buy", group1) // Add Group 1
else
strategy.group("Buy", group2) // Add Group 2

Hi @jstap,
Thanks for your interest. The problem is not being able to update or design a new one using the indicators we were actively working with before. In other words, we are no longer able to use the service we received.

Although we provide support to identify the problem, it is sad that there is a lack of interest.

We need to work with time frame variables, especially in MTF indicators, you know. In this case, instead of using the ENUM_TIMEFRAMES structure, we need to give the variable a different name and switch to its standard structure (with the code block below) at the last stage.

ENUM_TIMEFRAMES timeFrameGet(int period)
{
int _shift=(period<0?MathAbs(period):0);
if(_shift>0 || period==PERIOD_CURRENT) period=_Period;
int i; for(i=0;i<ArraySize(X);i++) if(period==Y[i]) break;

return(X[(int)MathMin(i+_shift,ArraySize(Y)-1)]);

}

Again in the same example, at the beginning of the code;

_tf = inpTimeFrame;
ENUM_TIMEFRAMES timeframe;

draw_begin = inpPeriod; // initial PLOT_DRAW_BEGIN value

//---
timeframe=_Period;
if(_tf<=timeframe)_tf=timeframe;// if the TF is less than or is equal to the current one, set it to PERIOD_CURRENT
pf=(int)MathFloor(_tf/timeframe);// calculate coefficient for

I can't do this part with "input ENUM_TIMEFRAMES = PERIOD_MX".

I'm not sure if I explained it.

You may ask, if you can do these things and compile them in the code editor, why use fxDreema?

For me, there is only one reason: time. I can do it much faster with fxDreema.

I made all the candle templates, here:

https://fxdreema.com/shared/fkB9cvcZd