Posts made by fxDreema

When you type the new block title, click on it to confirm (this works as some invisible button "OK" is clicked). When the name is edited successfully you should see new event in Actions History and also a message up there, below the menu.

Here is some example that I created some days ago: https://fxdreema.com/shared/dEwPXVl7c

Depends, it can be a position, it can be as a pending order... different ways. And it also depends if it is MT4 or MT5.

I can confirm, it doesn't work now. The problem is the handle function that is now used. In the past it was start() for both, EAs and Scripts, now it's OnTick() for EAs and OnStart() for scripts. Well, in the generated files it's still start() and it should work, but for some reason it does not work when the file is compiled with fxDreema (and it uses the same compiler that MT uses). It works if you generate the output .ex4 file with MetaEditor. So I guess I should do something to overcome this issue... I don't know when will I be ready with it.

Many strategies are possible If then is the "Condition" block.

I guess so. Basically scripts are EAs that runs once and exit, so any file that is exported should work as a script if placed in Scripts directory. But in fxDreema there is no way to tell the program to export the file in there, this is something I need to do

The real symbol name looks to be EURUSD.e

The code I posted above was to be used as a custom block via https://fxdreema.com/studio/MQL4, not within "Custom MQL4 code". The "Custom MQL4 code" does the code that is written inside and it passes always, so it's not suitable to make a condition. While in the studio (https://fxdreema.com/studio/MQL4) the keywords ~next~ and ~inext~ connects the block with the next blocks... I already wrote that above. Just try it

https://fxdreema.com/shared/DXBa7Rlrb

Partial close of 1 lot in steps:

• 0.2 fixed lot
• 20% of initial (1 lot) volume
• 50% of the current volume (what is left from it)

The result is this: http://prntscr.com/3gdvve

• 0.2 lots closed, now we have 0.8 lots
• 0.2 lots (as 20% of 1 lot) closed, now we have 0.6 lots
• 0.3 lots (as 50% of 0.6 lots) closed, now we have with 0.3 lots

Right click on a block -> Information

Indicator tester works like this: https://fxdreema.com/demo/mt4-indicator-tester
Inbdicator rise detects when the indicator rises - the difference between it's current value and old (candle) value is more than some number.
Indicator appear is when the indicator was not visible and it turns into visible, this is for arrows and oblects like this. Of course, it works on a buffer level.

Well, if you don't have money I think the minimum lot will be enough for you. And for those martingale strategies... you know that they always end up with margin call. And if for some reason you got backtest result that looks too good to be true, then better don't believe it, it's probably not true (ticks data quality).
Otherwise those "% of" options are doing it - they give you lot size that depends on the current money in some way. Again, in case of balance 10,000, the lot size will be 0.1. For 12,000 => 0.12. For 1,000 => 0.01. I don't know if there is a MM like this, because this method of calculating lot sizes was my idea at the beginning. Probably stupid idea, but sometimes I like it.

I have plans to remove those blocks from the betting system category and include them as a MM option in Buy now/Sell now. Who know when will I do that

1. No, and I can't tell you when or if it will be able to do that
2. https://fxdreema.com/documentation/gett ... indicators

This is for a new block like "Object Appear", but there are so many objects and parameters... sometimes it's easier to just write some simple code like this:

static string name0;
int total=ObjectsTotal();
for (int i=total-1; i>=0; i--)
{
   string name=ObjectName(i);
   if (name==name0) {break;}
   if (ObjectType(name)==OBJ_ARROW && ObjectGet(name, OBJPROP_ARROWCODE)==236)
   {
      if (ObjectGet(name, OBJPROP_COLOR)==Blue)
      {
         name0=name;
         ~next~
         break;
      }
      else if (ObjectGet(name, OBJPROP_COLOR)==Red)
      {
         name0=name;
         ~inext~
         break;
      }
   }
}

Try this in a custom block (https://fxdreema.com/studio/MQL4). I didn't tested it, but I guess it will work.. or it will need some simple fix. I hope you will get what is the idea, I think you have some MQL4 basics
Keyword ~next~ will be replaced with function calls for the next blocks for the orange output, and ~inext~ also, but for the yellow output.

Is it now ok? (get the same build 080)

Now it must be ok

"Round numbers detector" - it does not have magic number, only Market name (from which to get the price information) and the value that tells it how to detect round numbers. This block does not care of what trades you have, it works only with the current price.

I just replied to very similar question: viewtopic.php?f=2&t=2464

There is no need to work with objects if the indicator has working buffers, so check those buffers first. If buffers does not give you any meaningful information (because not all custom indicators do), then the objects can be used.

Otherwise in your project you are checking for Arrow Down and Arrow Up, but the arrows on the chart are not exactly this type. Here are all arrow codes listed: http://docs.mql4.com/constants/objectco ... /wingdings You can check that code with Condition, but better check if you have working buffers out there

And use "Once per bar" after (not before) the block who detects when the arrow is there to make the logic to detect only the first appearance of the arrow.

There is a block named "Indicator appear", but it depends on the indicator itself. This block waits for the buffer to turn from 0 or EMPTY_VALUE to something that is different than 0 or EMPTY_VALUE. So if your indicator is... let's say "not standard"... then you should use Condition block(s). In any case, I will recommend you to check your indicator's buffers using "Indicator tester" block. With this block you will see how buffers work, and if they work properly then "Indicator appear" can be used

I can see you are using Martingale blocks with fixed SL and TP.

I think the value of "% of Balance is not correct in this case, but this is my fault, because I need to update some information in these blocks.
So, 0.5% is damn too small for this option. What this option means is that if you have 10,000 dollars, 100% of them are 10,000 dollars, which in lot size is 0.1 lot. Well, at least in EURUSD and those similar currencies When you use 0.5% it just takes the minimum lot that is available.

But! I just realizes what is the real problem. You are using Martingale blocks to do Anti-Martingale strategy. If you want to increase lot size after PROFIT, this is NOT Martingale, this is Anti-Martingale. Martingale doubles the lot size after a loss, and this is by definition.

It depends. It passes when it is executed and the candle is new for the block. If the block is on top (so it runs on every tick) it passes at the very first tick of the new candle. If it's under some condition it can pass later. So if you want it to pass in the beginning, just place it on top (with no other blocks above).
Also note that each "Once per bar" works for it's own. In other words, if you have multiple blocks "Once per bar" and one of them passes, this will not stop others to pass. Each one has it's own memory (static variable) where the last known candle time is written.