Posts made by james

OK. That's great. Thank you so much for checking this out. I'll get on with 041 now.

I'm afraid I think I've hit another snag with local version 040.

The attached MT4 source file, BuySellFiboError.mq4, was created in 037 and compiles correctly in MetaEditor, but when loaded as a project from file into 040, then saved and re-compiled in MetaEditor produces the errors shown in the log file attached, BuySellFiboError.log.

Could this have anything to do with the dll fault I've reported earlier here? http://fxdreema.com/forum/viewtopic.php?f=3&t=2048

I'm going to return to version 037 again, as I don't feel confident about moving on. Sorry.

Hope we can resolve the issues soon as I'd really like to keep up to date with fxDreema's development. I still really like the product, by the way! I know these issues will be resolved.

......
BuySellFiboError.mq4
BuySellFiboError.log

Yeah. I'm a bit of a dinosaur using XP, but my reasons are:
*completely stable
no compelling business case to upgrade, so haven't wasted my time on it!
works with my Samba Linux CentOS5 (Red Hat Enterprise Linux 5 - Windows server immitation - check it out !) domain
[/list:u:1ljuezft]

I'd be very grateful if you could fault find on XP for me. It would settle my mind. In the meantime I'll do as you suggest and just skip the error message - and keep my fingers crossed!

Yes. This error comes up in 040.

Yes. I am in Windows XP with service pack 3.

This is what I see:

• Upon launch, I get the "fxDreema is loading, please wait" message with the moving green bars:
• Then immediately this error message:
• Click the OK, and the "fxDreema is loading, please wait" message box reappears for a second:
• Then I get the login screen, and I am able to log in.

The error therefore appears during the initial launch stage. Was something in this part changed after build 037? I don't have a copy of build 038, but both 039 and 040 produce the fault.

However, I have not started using the new local version, as I feel unsure that there might be unpredictable outcomes. I'd be very grateful for your guidance on this. For example, are you able to say that I can safely ignore this error message?

Just to be clear, the machine running fxDreema is used for no other purpose, and apart from MT4 and MT5 has no other non-Microsoft or any application software installed. I also have no difficulty running build 037, which is where I am currently stuck, since I feel unsure about using the recent upgrades .

Because the error does not show up in 037 I am assuming this is an fxDreema thing, but of course I could be wrong. Googling around for an answer really hasn't helped either. The closest I've come so far is here: http://support.microsoft.com/kb/142606. This seems to point towards fxDreema being the cause, even though it doesn't mention XP.

I came across a little hint of what might be a fix here: http://code.google.com/p/dolphin-emu/issues/detail?id=4344. It says:
__Dolphin x64 builds will no longer work on Windows XP x64 unless you compile Dolphin with the "USE_SRWLOCKS" and "USE_CONDITION_VARIABLES" defines disabled.[/quote:145xy88x]
Does this help you at all? Although I am not running XP x64, I wondered if the information about program compilation might provide you with any clues. Maybe this bit is just a red herring! However, the Microsoft support article is clear enough.

And here's another Microsoft support article: http://support.microsoft.com/kb/300179.

The bottom line is that it seems that fxDreema may be calling something that doesn't exist in XP - I think, but I could be wrong! I'm not a programmer of any sort!

...but I would like to use the fxDreema updates!

Ah ha! That explains it! I'm so sorry to have troubled you. Thank you.

I'm really sorry to have to report that I still have the same dll error I reported before in "dll error launching local version build 039".

Build 037 doesn't have this issue, so something has changed.

I am now stuck on version 037, but am keen to be able to move up. Can you please help?

http://fxdreema.com/forum/download/file.php?id=160

When backtesting with the attached EA and data, I discovered a Divide Error which causes the EA to stop. The workaround is to remove the US500.U market, leaving just the _US500. The problem seems to be a gap in the broker's US500.U data.

However, this led me to wonder if there was a more elegant way to handle zero divides. I looked around on the internet, and found some stuff which I didn't really understand. So I wondered if fxdreema had any good ideas?

The data file attached may be imported into MT4. It is an extract of minute data from a reliable source, not the broker.

......
_US500.txt
Zero_Divide_Error.mq4

This is the point format which my broker uses:

*Indices - 0.01
Forex - 0.00001
Futures - 0.01[/list:u:6rqa7lhw]

So it would be helpful if I didn't have to redefine each in Options -> Current project options -> Point format.

Fxdreema currently can set a market or timeframe using a block. I just wondered if something similar to this could be created for Point Format.

Of course you are right, but if you have no time, lake some experience and own some extra cash, you may prefer to buy an EA instead of building, and that's why you should be cautious if you took that decision!

I think that you should never purchase an EA where the author won't allow you to see the source code. It is SO important to use good money management that you should not ever leave this to anyone else to decide. Its really easy to loose money; so hard to make it!

Fxdreema - could you say what you think a small SL/TP might be?

Also, if using M5 or above timescale, would you say the backtester is 100% correct?

Many thanks.

Hi, and thanks for the reply.

I'd like to apologise in advance as I'm a little confused, and may be missing the completely obvious!

I'm conversant with the "Options -> Current project options -> Point format" method of changing the point format. But what I'd like to be able to do is use one EA over several market types with different point formats. At the moment I need three EAs to do this, and this makes things a little unwieldy.

You kindly told me that function that makes the calculation is at http://fxdreema.com/documentation/collection of functions for mql4/pipvalue.

What I'd like to do is have a block, or piece of code to put into a "Custom MQL4 code" block, which works in the similar way to the "Set Current Market for next blocks" block. That is to say, the block says this; "let me check the point format for the market this EA is currently working on - ok its 0.01 - so for this EA we'll work in this point format". In this way I'd only need one copy of the EA to run on the three market types with different point formats.

Can I do that now? How?

Thanks so much, again.

But why pay for an EA? Especially as you've so clearly outlined the pitfalls?

Surely much better to build your own using the truly excellent fxdreema! And you needn't be stuck for trading ideas! There are many publications and much on the web to get you started.

So, go on - don't buy: build!

P.S. Have you some link with the Forex Robots Review web site you seem to be promoting?

My broker uses different point formats for differing markets:

*Indices - 0.01
Forex - 0.00001
Futures - 0.01[/list:u:2nfuc84p]

Is there any way currently of making fxdreema pick this up automatically? If not, could this become a feature? Maybe a new block?

The reason I ask, is that I've missed this on more than one occasion and caused myself extra work!

I mentioned this earlier, but did you discover why build 039 displays this error upon launch? Build 037 didn't. I'm a little concerned about using 039 because of this.

......
fxdreema 039 launch error message.jpg

Hi

Yes. It seemed to come up, but I didn't feel confident about using it so reverted to the older version again.

I have just upgraded from build 037 to 039. I now have this error:

What could be wrong?

......
Clipboard01.jpg

I'm really sorry about this. I think I haven't explained myself well enough.

I actually did as you suggested; I inserted the statement into the Value (numeric) field, but that didn't work.

Superb!

Any idea on when a new local version download will be available with these?

Er... as I said, "I can show date and time in a "Comment on chart (low level)""...

So I know that works!

But I just wondered why I couldn't get this to work in a"Comment on chart" block?

I can show date and time in a "Comment on chart (low level)" block by using:

[code=mql4]TimeToStr(TimeCurrent(),TIME_DATE|TIME_MINUTES|TIME_SECONDS)[/code]

However, this won't work if I wish to use the "Comment on chart" block. I tried placing the above line in the "value numeric" field.

How can I show date and time using the "Comment on chart" block? It is simply a matter of convenience to save typing out stuff!