Posts made by fxDreema

Here is how to close a single trade: https://fxdreema.com/shared/1Jqspfcib (I just sent this example to someone else, so I'm using it the same here)

The condition is whatever it needs to be. Maybe you can use "Once per bar" or some other way to limit the execution of these pink blocks.

Is this picture from the last project that you have on the web version? If so, I will suggest few things. The first is - backtest it. Add some "Buy now", set it's MagicStart to 0 and backtest it. If there are issues, they will appear. Then, I'm not sure about the combination of Break even and partial close. Maybe you want to partially close and break even at the same time? If this is the case, why not using the pink "modify stops" somewhere around "close (partially)"

Here are some amazing facts:

1. Input parameters of the EA does not tell what the EA contains. There can be countless versions of EAs with the same input parameters. Again, input parameters means nothing at all and I can't tell what is the problem by looking at some input parameters.
2. People do dumb things. Missed to set some setting, the position of some block is "wrong", wrong block is used, some block is disabled and you don't even know that red-glowing means disabled.... and also many other things.
3. I do dumb things as well! All of these things that I already said, and I do them very often.

What is specific for that one trade that you want to close?

Here is about block numbers: https://fxdreema.com/demo/blocks-execution-order Block numbers matter only when 2 or more connections comes out of the same output. The same as if you drive a car and the road turns into 2 roads.

One parameter is missing from the indicator, because can't understand such definition: http://prntscr.com/6vtz28
You can add some "extern int" to make it work

Here is how to make it better:

//---- input parameters
extern int RSIOMA                      = 14;
extern ENUM_MA_METHOD RSIOMA_MODE      = MODE_EMA;
extern ENUM_APPLIED_PRICE RSIOMA_PRICE = PRICE_CLOSE;

extern int Ma_RSIOMA                   = 21;
extern ENUM_MA_METHOD Ma_RSIOMA_MODE   = MODE_EMA;

extern int BuyTrigger      = 80;
extern int SellTrigger     = 20;

extern color BuyTriggerColor  = DodgerBlue;
extern color SellTriggerColor = Magenta;

extern int MainTrendLong   = 50;
extern int MainTrendShort  = 50;

extern color MainTrendLongColor  = Red;
extern color MainTrendShortColor = Green;

This is the function to modify orders: http://docs.mql4.com/trading/ordermodify
Open Price, SL, TP and Expiration can be modified, but not the Lot size. So... close the order and open a new one.

Well, I don't recommend using OR block. I even want to remove it, but some people use it

The best way is this: https://fxdreema.com/demo/applying-or-logic-method1
And here is how OR can be used, but in this case all the conditions will run. In a sense, OR works like Pass once in this tick.

The best will be when I make it possible to use multiple conditions in a single Condition block, which is very very old idea, but still not true

Because the title is edited directly in the HTML code. In this case new rows can be added and you see the end result directly. What you see is what you get at 100%, no extra input field or textarea is ever created. But I also agree that it's sometimes buggy or not intuitive. Maybe I will add some extra "Save" button, because the Enter is used to move to a new row and this leads to confusion Otherwise, to save the title what you need to do is to click on the block.

Here it is, some example for some EA that I really don't like:
https://fxdreema.com/shared/2k2fI4VRb
http://www.forex-central.net/sure-fire- ... rategy.php

Personally, when I'm trying something, I try some simple things. As a programmer I prefer simple things and I just can't handle complex strategies So my personal tryouts really contain few blocks, nothing special. Some people have strategies with 100s of blocks... which is actually an example of bad programming. I think that anything less than 50 blocks is fine, but it depends.

In the forum you can find some projects here and there. Look for links that contain fxdreema.com/shared. But the best you can do is to play with it a little bit. You can do that absolutely for free, because even 10 connections are enough for many EAs.

I can't say because I don't know your project. If you put it in the web version I will be able to see it

Some log screenshots maybe?
https://app.prntscr.com/en/index.html

Add them manually. The whole idea of adding custom indicators in fxDreema is to ger their input parameters and buffers from the code and nothing more. I don't even store what's uploaded and in future they will not even be uploaded. Unfortunately the .ex4 file is too encoded and I can read this data from there.

Adding data from custom indicators is... when you understand it, it's easy, but you should be careful to put correct number of parameters and correct datatypes. Here is more: https://fxdreema.com/documentation/work ... indicators

This is the Data path (yes, in portable mode it's the same as the terminal path):
C:\Program Files\Ava MetaTrader\

http://prntscr.com/6ufjpv or http://prntscr.com/6ufk0k

Here is how to keep all orders at 20 pips away from the current price, but note that this is too aggressive, orders are modified on every tick and if you don't use some time filter the broker will hate you: https://fxdreema.com/shared/2R7PZiMed

I realized that I can't found make the opposite of "pips away from open price". I wanted to detect when the distance is lower than 19 pips, so I tried with negative values in "pips away from open-price", but nothing worked. As I created this block long time ago, I don't even remember how it should handle this

"Indicator tester" is a block that can be used to visualize values on the chart, similar to indicator. This block is to be used when you don't have an idea what the custom indicator buffers are giving you. It's an alternative to the native Comment for example, but it also prints the history of values as a line. This line is created from multiple small trendlines, so it's not a good idea to use this block in normal situation. Use it only to see what is going on in custom indicators or other values.
After you add a new indicator, reopen the properties window of "Indicator tester"

EX4 files are all that MetaTrader 4 needs to run the expert advisor. This is it's compiled version, it's "executable"... the expert advisor itself. What is needed is to put it in the directory where other Experts are, open MetaTrader 4 and double-click on it in "Navigator" or backtest it.

You can try to add this function CalculatePipValue here https://fxdreema.com/studio/MQL4 and then use it in Value -> Numeric like this: CalculatePipValue(0.1)

http://prntscr.com/6u1x91
http://img.prntscr.com/img?url=http://i.imgur.com/6L0UTrE.png

Orders does not depend on timeframes, charts and so on. There is one single pool with orders and trades. Timeframes are only for calculations, indicators...

Well done, that was really a bug. The code to set Anchor was missing Fixed!