Topics created by Trader3487

That looks bad. I don't know exactly why it happened, so I can recommend to relod the generator (or the project), to move one step back (before that paste) and to try on clear 🙂

I recommend to use the same group of blocks instead of copy-paste them. I know it feels natural for beginner-programmer to copy-paste things, but this is not a good idea actually. Well, fxDreema is not exactly programming tool and it's not that flexible as the plain code, but the best is if any part of the program exists in one place and if needed it is used multiple times. Using Variables can help with this in general, not in every situation, but if it is possible use the same group of blocks with different parameters 🙂 Even better is to program custom code with all the specific stuff, but this is for someone who knows how to do it 🙂

My actions are "changing block title text"... 🙂
...I'm trying to reproduce problems in a small new project, but no luck... Maybe it's a problem in big projects.... 😏

I'll try to detect the problem in future projects....

Thanks

None of these require server calls (if there is something about MT that I am not aware of), they interact with MT only, and MT interacts with the server when needed - and this is when trade/order is created, modified, closed. Checking trades happens locally and it's actually fery fast, so I guess the EA reads temporary variables that MT updates when new event happens.

nice 🙂

When checked, a Variable is actually a Constant - it appears in Inputs list of the EA. But I don't recommend to check these. They exists only because one day I decided to merge Constants and Variables, but this was not a good idea.

ok, thanks 🙂

I think the "Once"-off blocks are good to keep or at least as the default number of passes because people will mostly use them. But occasionally you need the multiple option so, in my opinion, you could either:

A)
Create the "N times per" blocks and put them in the list under the "Once" options as they appear like this:
Once per bar
N times per bar
Once per day
N times per day
etc.

B) add the "N times per" functionality to the existing "Once" blocks and revise the titles like this:
Once (or N times) per bar
Once (or N times) per day
etc.

Once/N times per bar
Once/N times per day
etc.

I would probably go for option B) with the second naming convention "Once/N times" and set the number to 1 as default 🙂

wow - I was close 😉 that's really awesome 😉

I think I want to remove the "start" word from it, and the "start" meaning as well, because in fact all the next blocks are executed "inside" this one, so everything starts with it, happens in it, and also ends with it.

ok, not a problem. I'll check out the web version. Neat screenshot 🙂

You are counting how many arrows there are? Then answer the question - what does "Once per bar" do? 🙂

Yes. Magic number, SL and trade type (buy or sell) are properties of the trade and they are not lost. Trailing stop uses these properties, so it will work with them when EA is "smiling".
Even a problem can come from this - if you have two EAs with same MagicStart (Magic Number = MagicStart + Group), they can both control the same trades.

MetaEditor is much more flexible and you can find support from other programmers in mql4.com and mql5.com 😉

well, let's say you want to offset the trailing stop so it starts after the open price. A fixed value won't work for all symbols, wouldn't I need a dynamic value? How would I do this?

I'm sure, but at the moment the source code that any block generates does not depend on the order of input parameters, it's hard-coded 🙂

I found a workaround by using formulas instead of variables but here is an example before implementing workaround. Project id: mt4-1808

"Constants" and "Variables" in fxDreema are basically the same thing in MQL4 and MQL5 - global variables. The difference is that Constants are automatically set as input parameters (to be seen in Inputs list), in other words they have "extern" (MQL4) or "input"(MQL5) in front of them. What is specific in MQL5 is that input global variables cannot be modified inside the code, while in MQL4 they can... but I will recommend to use Constants as constants in MQL4, to not modify them in the project. Also, you can't define Constant and Variable with the same name... at least this will not work in MQL4/MQL5, you will see an error message.

But you can define a Constant (if it should be in Inputs, otherwise a Variable will also work) like "Hello" and a variable like "vHello" and set "vHello" as "Hello" in order to "reset" it.
If I'm gonna do the functionality to reset variables, it will be something like this, but... now I'm not so sure that this is a great idea, because now you can set a Variable to be Input (to be Constant) and if there is a functionality to reset that Variable... well, in MQL5 it will not be possible, and I also know that MetaQuotes are in process of changing MQL4 to be the same as MQL5.

just thinking, is there a way instead of creating a condition block for each market to create 3 condition blocks: 1) if market is 5 decimal places (that would cover EURUSD, AUDUSD, GBPUSD, etc and micro variations) 2) if market is 3 decimal places (that would cover JPYUSD & SILVER and micros) 3) if market is 2 decimal places (GOLD and GOLDmicro)?

"pips" uses the point format defined in options, so it depends.
search for "double toPips", I can tell where exactly it is located because what functions to be used inside the project depends on the project itself - only the ones needed are places in the code.