Hello 
On a chart in MT4, its possible to drag the moving average indicator onto an already open volumes window (or any other), and display a moving average of the volumes, thus:
However, I don't see a way to express this in fxDreema. I'd like to be able to do something like; "when volume exceeds moving average, do such-and-such".
Is there a way to achieve this?
Thanks, as always.
......
Clipboard01.jpg
Yes. Thanks, I realised I could do this in a global variable, but I suppose I'd also like to have it in a safer non-volatile format!
For now I'll keep to the global variable, and look forward to a new block sometime!
Hello!
The brilliant fxDreema software is still just as brilliant! Thank you.
I have a query - well, a request really. You have a "File Write (Excel table)" block, but no "File Read" block. As it turns out, this would now be of use to me. I understand from http://book.mql4.com/functions/files that it is possible to read data from a .csv file into an EA.
Specifically I'm looking to record a number after each trade, and then use that number to adjust the position size on the next trade. The reason I need it to be laid down in a .csv, is so that if there is a power failure or something, then when the system comes back up, the number will be there. I could do this in a global variable, but I suppose I'd also like to have it in a safer non-volatile format.
Would you consider adding this block? I, for one, would be most grateful!
Thanks, as always,
James.
OK. Thank you for the reply.
So, unless I'm mistaken, in the block I'll put the following:
__US500.Z,US500.H,US500.M,US500.U[/quote:6i4dakji]
...and this will mean that the EA will run on any of these markets each time I start it on one of them.
Please correct me if I'm wrong!
I understand this block will pass when the open chart matches the list of markets within the block. The examples given within the block itself are, EURUSD,GBPUSD,AUDUSD.
Some markets change their symbol at different times of year. On my broker, the S&P500 index is known as US500.Z, US500.H, US500.M, and US500.U depending on the time of year.
How should I enter this in the block? Is simply "US500" sufficient to catch all variations? Or should it be "US500?" as in the Project Options?
Thanks.
My apologies. I used the daily candle to try to keep things easy, but all I did was to confuse! Sorry.
I'm trying to achieve this:
__
*
The next bit is eluding me. I just can't work it out!
It seems to me that I need to come up with a magic way of extracting from the unix time, a value in "hh:mm" format, place it in a new variable, and drop this into the "from" and "to" fields of the once per day block. Sadly, my magic isn't strong enough (indeed, its pretty weak!) to come up with the method. I appreciate I may need to use a Custom MQL4 Code block along the way to achieve this.
Any suggestions would be most welcome!
Thanks again,
James.
Great! Thank you.
Now, however, a further query - sorry!
In the updated example here, https://fxdreema.com/shared/3GOCLH61b, I've captured the time of the last daily bar's close, but want to execute a Once a Day block in a 15 minute window, beginning 23hrs 45mins later.
But dropping the variables "LastCandleCloseTimePlus23hrs45min" and "LastCandleCloseTimePlus24hrs" into the Start and End Hour boxes doesn't seem to work for the block.
Suggestions will be most gratefully received!
Thanks, as always,
James.
Is this recording the close of the previous candle?
...sorry - forgot.
I also need to have the time recorded in human readable format!
Hello
I'd be very grateful for a little help.
I'm attempting to capture the time a bar closes, thus:
__on the close of the current bar, send the time to PrevBarClose (a variable)[/quote:33ol25al]
Or possibly:
__on the open of a new bar, send the time of the closure of the previous bar to PrevBarClose[/quote:33ol25al]
I've been messing around with all sorts of methods, none of which worked. So I don't even have anything to share which is meaningful!
Thanks again,
James.
Hi
Yes. That seems to have cured it!
James
Hello
I don't think its me - although it could be! - but I don't seem to be able to save point format rules in 084, despite the comment in the change log!
Many thanks,
James.
You live in the poorest for internet - except for rural Scotland! There are many zones around where I live where I can't get any sort of signal! 
When I'm "off grid" I'm even using my email off-line - Gmail has the ability to do so. So using fxDreema and MetaTrader in off-line mode (MetaTrader works fine for testing purposes off-line) would useful to me, and probably others. You do have a global audience for your product.
On top of that, in aeroplane mode, my laptop is permanently off line - the air steward insists!
Perhaps, as I mentioned before, the local version might be made to allow a limited (not too limited!) number of logins off-line before demanding an on-line one. Just a friendly wee suggestion!
But, hey ho! Its whatever you decide! FxDreema is still a terrific product, and I'm not changing to anything inferior! 
Best regards,
James.
Hello!
I was very interested to see the following in the version history for the local version, which update I only downloaded today:
__Build 082, 22.05.2014
Thanks again.
James.
Hi power7
I agree that there is a learning curve - but that is in common with all other software. Our friend, Mr fxDreema, does have some help material on the web site, but I've yet to find a comprehensive manual. This is understandable, since the software has been undergoing rapid development. The answer is click, investigate, and test all the features of fxDreema. There are many, but the journey is worthwhile.
My experiences with fxDreema have been wholly positive. Any glitches I've come across in the software - and there haven't been many - have been fixed within hours. I can't fault the support.
The results from the software when I've run the EAs have indeed worked out as I'd intended. Any time it initially didn't it was always down to my own lack of knowledge, poor logic (this bit is critical), or just a basic silly mistake on my part.
I've been running this software since November 2012. I've also looked at other similar products, but have not found any better.
Anyway, I see fxDreema himself has answered your last query (9). As far as the basic operations go (like "does this mean that it will execute whatever is 'underneath' this block for every trade? (3) Or just the ones connected to this block?") these are covered in the help sections. Do read through them all. I think you'll find that all your operational queries will become clear as you use the software after reading them.
__I would like every trade I enter to have two stop loss at two separate predetermined levels. Can I do this by using the 'for each trade block' or is that not what it is meant for? (6)[/quote:3kovovv4]
Anything is possible in fxDreema. As he himself said to me, the software is an enabling tool. As long as you can think through the logic, there is probably a way of making the software do it. Sometimes lateral thinking and sleeping on it is required! This I have learned by trial, error, and evolution.
I can only encourage you to sign up. FxDreema is very sensibly, reasonably and flexibly priced. If it hadn't been I wouldn't have considered it!
I hope this helps you on your journey, for that's what it is!
Remember: if you can work out the logic, there's probably a way to make it happen in fxDreema.
James.
The calculation is a "formula" block. I renamed it in my example, and confused things. Sorry
To group trades, take a look inside the relevant blocks. Click the "Origin of trades" bar, and place a number in there. Use this same number in the rest of the relevant parts of the EA (you can have multiple groups within an EA), and it will act solely on the trades associated with this number, leaving others to do their own thing.
Neat!
...and to make it work on specific trades, you'll need to combine it with the "Group" facility in fxDreema. This is equally easy.
No. The "add to volume" block is standard to fxDreema. It should be in your list. I think you should be able to do what you are looking for with my method, or a variation of it.
Yes. I see that. This works for me because of other things I'm doing. I guess in that case I'd store every previous trade's lot size (MODE_LOTSIZE) in a variable, and call that in to the calculation which should then work. However, the principle of the method would remain the same. I hope!
Hi power7,
Here's how I do it:
https://fxdreema.com/shared/ejBkBwe7c
Maybe you will be able to improve it for us both!
James.