Posts made by fxDreema

If you are not gonna add this indicator to fxDreema (by uploading it), have a look at the last 3 pics here under "Without uploading": http://fxdreema.com/documentation/proje ... indicators

It is also possible to upload other indicator's content instead of this one, the only thing is the name of the file and the number of buffers. Uploading indicators for use in fxDreema is only because of their names and buffers, their logic is not important.

Also, it is very good idea to check "Levels tester - visually check buffers of custom indicators (and other tools)" example here: http://fxdreema.com/examples

Andy, http://fxdreema.com/chat is with free access to all registered and guests, this is not a private club. It can be, but now it is free for all. This guy is a guest and I don't know him. Can you skip such children behaviour? I can skip "complete arsehole" words.

When I'm testing it, it seems to work Do you get some error messages?

http://fxdreema.com/shared/uAvoexc9b

This will wait for buy or sell condition, and when the condition is ok and the time is between 00:05 and 16:00, we enter in buy or sell. In one day, one buy and/or one sell can happen.

Everything will work if we are not care what is expected to happen. I can't see what is the expected result from this, so my answer is... why not?

You can tell me the project name or ID if it exists on the web version and I will be able to see it directly, there is no need to describe things in such a way.

It matters if "Condition" is before or after "Once a day". If "Once a day" is before "Condition", then the condition will be checked once a day at 0:00 and that's all. If "Once a day" is after "Condition", then the condition will be checked all the time, but only when it is true "Once a day" will pass once. And it can happen in 0:00, 2:53, 7:32 or any time...

Just follow the logic. Each block is either passing or not passing, depending on what it is designed to do. And the name of the block normally describes why it exists. It is a good idea to give the blocks better names if needed, so the whole strategy can be followed from the top to the bottom step by step.

http://fxdreema.com/shared/99a4SgY3c

Block "test" is only to draw line of the lowest values for you to see it, it is not to be used as indicator.
This project will work on web version only, because now I made some changes in the way lowest/highest values are calculated. Also I set it up that when the "End" hour is still in the future (so we are between 0:00 and 5:00), the block ("Condition")will not pass at all.

In .mq4 code, there is a function named BuyNow (or SellNow for sells):
http://fxdreema.com/documentation/colle ... ql4/buynow
http://fxdreema.com/documentation/colle ... l4/sellnow
Somewhere at the middle of the code there is a "OrderSend" MQL4 function.

if (IsBrokerECN()!=false || ticket==-1)  {
      ticket=OrderSend(symbol,OP_SELL,lots,bid,slippage, 0, 0,comment,magic,0,arrowcolor);

see where "slippage" parameter is? Between "bid" and "0". This is int parameter, following this:

int OrderSend( string symbol, int cmd, double volume, double price, int slippage, double stoploss, double takeprofit, string comment=NULL, int magic=0, datetime expiration=0, color arrow_color=CLR_NONE) 

They say that this parameter is in point format, for example 3 (when broker is 0.0001 type). I presume that it is internally converted into 0.0003 when 3 is used.

I have to be honest, I never take care of slippage and I don't know for sure how it should be used. And I think my broker is not a slippage maniac. So you can play in MetaEditor by replacing "slippage" with values in different format to see what works. And if you find the correct format and it is not as in their example (see "3" between "Ask" and "Ask-25"):

ticket=OrderSend(Symbol(),OP_BUY,1,Ask,3,Ask-25*Point,Ask+25*Point,"My order #2",16384,0,Green);

please, tell me

Yes, they should be used that way. In any event workfield (I mean, Init, Tick, Trade, Timer, Deinit), when there are more than one independent logical trees, they are all executed, one after another.

See this example here: http://fxdreema.com/demo/using-trade-event-tick

I can see you are trying with placing pending orders in grid, which is a good decision I think. Some progress?

In Local version, no "Save as..." dialog will appear, because files are written directly to "exports/" folder of MT4. In fxDreema Global options you should write where MetaTrader 4 is located, but it's parent directory, where "terminal.exe" is located. For examlpe "C:\Program Files\MetaTrader 4", which is the default value actually.

When pending order opens, it becomes trade and total number of trades is incremented with +1.

This sounds to me like when a new bar is created, you can check if the body size of the previous bar is greather than 100 pips.
In "Condition" there is a "Candle data" where you can find "Bull candle body size (pips)" for example. In this case, this can be compared with value like 100.
If you compare two values, you can also write for example "+100pips" in Adjust field to add 100 pips to the value.

About 100 pips size in 1 minute timeframe. If you are working with 0.00001 format, then 100 pips are 0.0010 and it is possible to have bar with such size. By default fxDreema projects are using 0.0001 format where 100 pips are 0.0100 and in this case it is near to impossible to have candle with this size in M1 timeframe. Check "Options -> Current project options -> Point format" and write the format you desire.

Same thing, another approach:
http://fxdreema.com/shared/ZQJOcQgJc

Here "Trade" event is used, and when 5'th trade is created, block 6 passes and block 7 executes as many times as many other trades are existing. No "Formula" blocks here, because in block 8 parameters of the trade that caused the event are used.

Last trade seems to be important, many people are interested in it

http://fxdreema.com/shared/S3cqf4tE
In this example:

• Some trades are created, 1, 2, 3, 4... and when 5'th trade is created... (we go to the yellow output of block 2)
• 5'th trade is loaded using block 4 and in blocks 5 and 6 SL and TP level of 5'th trade are saved for later use. "Formula" block is used, which creates a global variable (Result) in fxDreema and saves value in it. "lastSL" and "lastTP" results are created.
• Now one by one, all trades are selected using block 7. They are modified using block 8 - every stop-loss becomes "lastSL", take-profit becomes "lastTP".
  In this example in blocks 4 and 7, only Buy type of trades are allowed. Well, depending on where is the last trade's SL and TP and open prices of older trades, there can be problems to modify SL and TP is SL is above open price or TP is below open price.

How to find the type of the last trade:
Start trades loop (set "1" for the last parameter inside) -> (in loop) Check trade/order type

This is something I heard about before. Sounds to me that MetaQuotes should make this possible in MetaTrader, but I guess it will not going to happen, at least with MT4. It's somehow ridiculous for me to make things to "hack" MetaTrader and change the way it work, but when it stays the same and some of the things can be better, I can think of how to make that possible. I have an idea to make a whole independent window, page or whatever, containing information of some important things happened. Something like better version of normal tester report. But I don't know when.

Maybe you are talking about Input (extern) parameters. It is possible to define a list with what I call Constants. Open "Options->Set Constants" to see what's in there.

Unfortunately, I can't set Slippage or other currency pair dependent parameter as a global parameter, because any block can be used for any pair.

What means to do it manually?

It's double now

__
why I dont have only blank sites when I click on the help tab ?
I work with the local version
[/quote:1wz7sb2e]
I have blank sites too, I need to check that. But all these links are available in the main menu in fxdreema.com, so you can always check them using normal browser.

Less than "n" trades are running in "Manage trades/orders count" category

If you try to modify MQL4 code generated using fxDreema it will be hard to do, and I think - with no reason. It's better to make modifications in fxDreema itself and leave MQL4 as is. Think of MQL4 code here like a black box.

There is a block named "Condition". Connecting two "Condition" blocks one after another makes them to work in AND logic.

Some things are demonstrated here: http://fxdreema.com/examples