Wow, thank you for checking into this for me! This project is 6 months old and it just stopped working last week. So, there must have been a backend update that broke this... @fxDreema can you help out here?
The good news is that I can just download the source file and build locally - it's a bit of a pain but not the end of the world. Thank you, @roar for your help!
@roar Sorry to bug you, do you happen to have any thoughts on this? No idea how the constructor for a tripple moving average indicator could possibly get messed up such that it's looking for a constant that I've never declared?
Yes, it is an MT5 project. The issue is with the Tripple Moving average indicator - for some reason, the constructor is looking for a constant variable for the timeframe. I don't have any constants called PERIOD_CURRENT- and this error just popped up randomly on this project and all of the previous projects from the last 6 months that haven't been touched in months... I feel like something happened on the backend. @fxDreema
public: /* Constructor /
MDLIC_indicators_iTEMA()
{
MAperiod = (int)14;
MAshift = (int)0;
AppliedPrice = (ENUM_APPLIED_PRICE)PRICE_CLOSE;
Symbol = (string)CurrentSymbol();
Period = (ENUM_TIMEFRAMES)c::PERIOD_CURRENT; //////// This is where the error is being generated from. I don't have any constants called PERIOD_CURRENT
Shift = (int)0;
/ Static Parameters (initial value) */
digits = (int)SymbolInfoInteger(Symbol, SYMBOL_DIGITS);
}
I added the additional buffers as shown above, and then in an ugly comment printed them out and it all appears to be working!
@fxDreema Did something change in the triple moving average model? Seems like the variable that's giving me trouble is defined inside that indicator constructor. I've never made a constant called PERIOD_CURRENT.
Randomly, yesterday my project decided not to build, I'm getting a compilation error for Period_current. So I downloaded the project file and tried to build it locally. I get the same error here.
I change the line to Period = (ENUM_TIMEFRAMES)CurrentTimeframe(); And it builds just fine. I then try to load that file back into FXDreema, and build it and I get the same error. Unsure why this is happening?
Has anyone experienced this before?
Forgot to mention, this is also happening on older projects that I have not edited in weeks or months. Still not building...
And this will automatically connect to the buffers that the indicator has declared. If so, that's VERY helpful!
Thank you
I'm trying to use a custom indicator that has a few buffers but when I pull the MQ5 into FXDreema it only sees a single buffer. I look in the source code of the indicator and can see the different buffers that are used - my question is how do I alter the source code of the indicator to make the buffer visible? The source code is pretty simple - and I've been through a good amount of the MQL5 documentation and it's just not clear to me how to make this buffer available. Hoping someone has a bit of experience here.
Update - was able to make it work by utilizing the count and start positions fir iLowest and iHighest with the start index as today.
Thank you for the help!
@roar This is very helpful, thank you! Is there a way to constrain it to yesterday only, I shifted the timeframe by 1, and the daystart is correct but it still seems to be returning the high/low for today. I don't see a parameter to bound the end time?
@roar Any chance you've encoutered this before?
Illustrating the point even further is that I just added the current server and GMT time to the live chart. Currently it's October 25th, but it's telling me that the high and low for yesterday occurred on October 23rd?
I switched from using the time to using candle ID and I'm still experiencing the same problem. Here's a screen shot of the issue right now. My EA is looking back 1 day to find the high and low time and candle ID. On the M15 chart, it's telling me the high from yesterday is 127 candles away from current price. This is an M15 chart, so 127 M15 candles is 31 hours ago. Looking at EURUSD, we can see that the low was really only a few hours ago. I don't understand, it's almost like the EA is looking back too far to two days ago, instead of just 1...
Code that calculates both the time and candle ID for the low/high
There's logic, trust me. Lots of data to suggest a correlation between violations and market behavior after... Knowing the time is important because I want to know if the violation was to the upside or downside when I do a lookback. So, Yesterday, was it a high or low violation - the only way I've found to do that is by finding the high and low candle time and seeing which candle violated (time-wise) first or last...
I look for price violations based on yesterday's price action. So, I need to look back and see if there was a violation and have to determine if it was a violation high or low or both. In the case where its a double violation I need a way to determine the last violation, so I find the high and low time of yesterday and compare which one happened first, thereby giving me the violation that happened last. This tells my EA to either look for longs or shorts. In the case of Mondays... The EA is seemingly confused because it tells me that the high and low happened at the same time (M15 candles) which is not what's happening.
Check the Journal, it may be that the minimul lot size you have in MT4 settings won't allow you to trade .01 lots.
I am looking to get the time value for the highest and lowest M15 candles between 01:00 and 23:00, not price.
My first thought is that the variables have the same name, which is a bad habit. This is how I handle dynamic risk. If the account balance is over x%, I take the base percent and add whatever I want and store that in a local variable. If the account balance is less than X%, then I restore the local variable back to the base setting, as not to over risk.
A part of my project tries to find the extremes from the day prior (high and low candles and the time) - I appear to be having issues on Mondays though, after the weekend. I'm wondering if this is a broker related issue or EA. This is a snip from today, where my EA found that the high and low (M15 data) happened at the same time, which is incorrect. Here is the code that calculates the variables.
So from this we can see that the day prior is the 13th, which is correct. There are no weekend days being looked at here. However, we know that the high and low of the day did not happen at the same time (M15 chart). Any suggestions on how to implement this differently so that it works?
Bringing up an old post here but let's say I optimized on entry times while backtesting and my time filter blocks are set to GMT. Let's say the Optimization said that 8AM GMT to 12PM GMT were the best times... Does this mean that those times are not actually GMT times, they were the server time, because I was backtesting and I need to adjust for that because my server time is +3 GMT.