SteveHopwood wrote:I have had the "Outside trading hours " message all day, even when firmly within trading hours, but only on my trading machine. Here on my coding machine, all has been fine. I copied 1e onto my trading machine by downloading it from post 1.

I just remembered that when I shut down the editor last night, it whinged at me that BBBE needed saving, so I did.

I wonder if I posted 1e without actually saving some of the fix? It is possible - I have done so before. Try V1f from post 1 and see if it fixes the problem.

fmuir wrote:v1f also giving zero divide errors

fmuir wrote:@SteveHopwood,

I downloaded v1g. I installed it and used my Tokyo setfile. It opened a trade. I then changed by setfile to use times outside of the current session. I did stop, made the changes and then restarted the EA. That didn't cause any change in the output screen about being outside of the trading time. I then re-installed BBBE, using the setfile with the times outside of session. The output screen then said that the BBBE EA was outside of the trading hours for that session.

Could this be an issue of having to re-install BBBE on the chart whenever you change setfiles for different sessions?! I recall reading on one of the threads in your forum that when any changes were made to that particular EA, that it was suggested that you remove the EA from the chart and then re-install the EA on the chart.

Does this make sense to you?

Regards,
-Frank

SteveHopwood wrote:
Yes. When changing setfiles do so by dragging a fresh instance of the bot onto the chart. Using the F7 key has unpredictable consequences.

SteveHopwood wrote: Yes. When changing setfiles do so by dragging a fresh instance of the bot onto the chart. Using the F7 key has unpredictable consequences.

MurphyMan wrote:

SteveHopwood wrote: Yes. When changing setfiles do so by dragging a fresh instance of the bot onto the chart. Using the F7 key has unpredictable consequences.

Let's not forget about sacrificing the chicken to make it work.

3_kaparot_1692.gif

SteveHopwood wrote:

fmuir wrote:v1f also giving zero divide errors

This sent me to look at my demo and the same thing.

I had been trying to use one of the fields in Baluda's symbolValues array that holds the pip factor for each symbol. This did not work when cycling through the list of trades to carry out management, so factor = 0 which caused the zero divide errors. I had to reintroduce the PFactor() function.

You cannot ignore these folks - the stop the EA from working. V 1g is in post 1 with the fix.