Posts made by fxDreema

What if you grab the orange circle (on the bottom of the block) with the mouse, drag it around and release it over another block's white circle (which is on the top)?

You are trying to do very very very basic things. The idea is to check if the account number is equal or different than some number, but you compare the account number with itself. When asking if A==A, the answer is always Yes.

And you didn't connected this Condition with nothing else. In fxDreema when a block is not connected, it is the same as it is not there, this block is not included to the final EA.

You just need to play more with this. fxDreema makes programming easier and faster, but because it exists to build strategies with it, you must be able to build those strategies in the head first - to know what conditions to apply and what actions to take.

In your case, you only need to check if the account number is different than a number, written from you inside the project. Account number is a number, so it should be compared with a number. And then, if the account number is different than the number written from you - go to terminate the EA.

I will recommend to you again to open MetaEditor and start learning how to program. At least to understand the basics like "if", "for", "while", functions, variables and constants. I think this is actually fun, so just do it

Start with:

int init() {
    Alert("Starting the EA");
}
int start() {
    Alert("Tick");
}
int deinit() {
    Alert("Unloading the EA...");
}

init(), start() and deinit() are the 3 main MQL4 functions, and everything starts with them.

http://fxdreema.com/shared/3E03jnhhe

What you are trying to do is to inject MQL4 code into the .mq4 file, but knowing nothing about programming. Let's say that you want to learn how to do that, then I can recomment to open empty MQL4 project in MetaEditor and learn the basics mql4.com helps, there is a full documentation and other materials. There is also documentation on the right side of MetaEditor.

Otherwise in fxDreema you can set expiration date in project's settings, and check the account number and stop the EA with only 2 blocks.

Well, you can't put function inside other function in MQL4

Condition -> Account Information -> Account number.

After that condition you can place "Terminate EA" block.

I never tested that, but it should work.

It must be fixed, but check blocks 3 and 8, the same "x>" is used.

This indicator has no buffers, but at least it's lines have simple names - from mml0 to mml10. So I can suggest what is in "Condition" -> Chart object attributes, and write mml0 (or the name of the line you need) in "Object name" field.

For example (for mml2 level): http://fxdreema.com/shared/HhncDVGD

By the way I'm giving you 1 month for free. I think you need to build your experience more, and I can recommend you to open MetaEditor and start writing some MQL4 projects. Really. To fully understand MQL4 is not that easy, but in the same time it's not that hard to enter in it. And this will really help you to understand what you are doing, it will boost your creativity. Normally to understand something on basic level 1 month is needed, so you are free to start with MQL4

Well, this is something partial. And now again I will repeat that rule - when using "(in loop)..." block, ALWAYS, and again - ALWAYS use "Start %whatever% loop" block first. Especially for MQL4, this block %(#FF0000)[MUST BE ALWAYS USED]!

And again... to use "(in loop)..." block, especially for MQL4, you need "Start %whatever% loop" block, depending on what are you working with - trades, pending orders, history trades.

And again... even when using "(in loop)..." category in "Condition" block, "Start %whatever% loop" block MUST be placed somewhere above. Because it loads the trades/orders/history that is needed one by one.

But nevermind, this block (the pink one) does something over a single trade, the last one that is loaded by the EA.

In contrast, the blue block does not make a list of trades to be used in another block, it does what it does internally, and does not care of any other block. It only passes if what it sees is true. And then I can suggest "Close each profitable trade" to close the trades with certain profit.

And by the way... never use "(in loop)..." block or "(in loop)..." category in "Condition" without having "Start %whatever% loop" block placed above. Especially in MQL4. Never!

MQL4, MQL5? Web, Local? Some example link maybe?

This topic is for MQL5's block, but in it there is no pre-filter to select only positions with profit > X. So you work on MQL4 or MQL5?

By the way I tried to load one of your extra-giant projects, and it appears to be broken, is that normal?

I think it's my turn to quote the quote

http://fxdreema.com/shared/Vd8ol5Bnc

To add this to your projects, save it as .mq4 and then import it.

I could not find some pattern of this strategy, something that repeats over and over again, and that's why the project is so big (every block is used for a single purpose). Well, still some blocks can be reused by using variables (trading blocks), but nevermind...

5 groups of trades are used, which basically means that this EA will put trades and orders with 5 different magic numbers (because magic number = magic start + group number, where magic start is an input parameter which exists in all fxDreema EAs)

"Modify Variables" blocks are to hold the value intil the end of the event. Otherwise, if "(on trade) ... Open Price" is used directly into the trading blocks there is a problem because meanwhile there are other events that occur. For example, between block 6 and 9 there is another event caused by the deletion of orders in block 9, so block 9 updates "(on trade) ... Open Price" value before you reach to block 10.

I could not understand the thing about lot size, so everywhere the same lot size is used. But you can add another constant and use different lot size in every step.

For debugging purposes I choosed to start new cycle after 00:00, and this is marked with vertical line and a price label.

The format is YY:MM:DD, for example 13:07:08, which means 08 august 2013

Well, this function called "mainCheck()" is not executed at all. Just placing a function somewhere in the code does not mean that it will be executed. But something like this can help...

int init() {
    if (mainCheck()==false) {IsTerminated(true); return(0);}
   .....

or in start()

int start() {
    if (mainCheck()==false) {return(0);}
   .....

IsTerminated() is a custom function used inside the EA and this function plays the role of a variable. It is read with "IsTerminated();" (it is false by default) and set to true with "IsTerminated(true);". When set to true, the EA stops to react on ticks.

Maybe, someday, but many things must be changed before that

MT4: http://fxdreema.com/shared/eRSVRITqe
MT5: http://fxdreema.com/shared/ktRttwYod

But maybe it's better to wait for PSAR reversal (crossover with the market price) to close the position without stop-loss. Here is something like this: http://fxdreema.com/demo/mt4-3221

In Buy now and Sell now you use the current value to use is as SL and TP, everything ends after these blocks - what is done is done.

Trailing stop block... I think it's unable to do that, but I can think to modify it a bit.

Try the last attempt, with Dynamic level and "Dynamic level" and then "Dynamic level (price input)". Optionally you can check if the indicator value is on the right side of the trade, otherwise error 130 may appear many times.

Max 2 trades between 0:00 and 0:00, max 2 trades between XX:XX and YY:YY... it depends.

But some combination with "Check trades count", "Counter: Count n then pass", "Counter: Reset", "Once a day"... depending on what is needed.

Or if something like "Twice a day" can be used (there is no such a block), I can imagine two "Once a day" blocks connected in a way similar to these conditions: http://fxdreema.com/demo/applying-or-logic-method1 - in this case you will have 2 possible passes, which will automatically reset at 0:00 (because of the new daily bar).

Strange, everything is fine in my Firefox and Chrome. I think I will replace that editor (TinyMCE) with another one... but later, now I'm modifying some rules deep in the code.
I don't know what is this problem now, but at least you should be able to grab that window (to it's border) and move it around.