Posts made by james

Hi again - sorry!

I'm a little unclear about the "Bulls in a row" block. Clearly the name suggests that if I set it up to count X candles of Y minimum size, then that's what it will do.

What I'm unsure about is the "continuous" and the "Once per bar" signal type. I'm assuming this means "tick by tick" and "once per bar" respectively. Am I right?

Also, what happens if a zero minimum body size is specified?

Finally, in "Row Mode", I assume that "normal" means any pattern of bull candle, and "candle size increase" means X in a row all increasing, and vice-versa for "candle size decrease". Am I correct?

Many thanks again!

Regret to say this is still happening.

I'm having a problem with "AND".

I have a trades loop like this one: http://fxdreema.com/shared/JvY0VGFid.

However, when I try running it I always get this error:
__2013.05.24 23:42:02 2011.01.03 00:39 omg5 EURUSD,M1: stack overflow[/quote:1ci0zawb]

Any thoughts as to what could be wrong?

OK

Hi

Are you any nearer a fix for this? Its becoming rather a nuisance! I now have a variable which thinks its used in 15 different blocks, when in fact it isn't used in any, but I can't delete it.

Help!

Hi

Yes, I've tried to replicate this on the on-line version, but have failed. It only seems to occur in the local version, and even then not every EA created suffers from it. Some of my EAs are edited and re-edited many times, and left open on screen for days. Maybe there is a correlation, but I cannot pinpoint one. The only work-around is to create the ResultNNN variable in the Variables list.

Update to this:

I'm not aware of changing anything, but I did do a system reboot. Now the Actions History is recording my work... having not worked for a few days.

After some time and around 200 blocks, "Actions History" stops updating.

None of the input parameter check boxes were checked, or even checked and then unchecked. They were merely created.

I have 7 formula blocks which create "ResultNNN", and 6 other varying blocks which refer to these results. With 6 formula blocks, fxdreema happily compiles the code. With the 7th added, I get an undefined variable error for all formula blocks, and have to declare these variables in the "Variables" list.

I have a query about the "break even point" and "add to volume" blocks.

In the example here http://fxdreema.com/shared/mEEDd95Ad, will the following happen?

1. condition is met and a buy happens
2. when the break even point is reached of the first buy, the "add to volume" block is allowed to pass generating a further buy
3. all trades have their own trailing stop set at the level within the "trailing stop (each trade)" block
4. this happens "n" times according to the counter setting, each new trade occurring when the previous is at break even, and each one gets its own trailing stop

Therefore, when a buy trade reaches break even, up to "n" additional trades are made, each one after the one before reaches break even, and each one given its own trailing stop.

Then if the in loop condition is met, all trades are closed by the "close each trade" bock, and the counter reset by the reset block.

Many thanks, as always!

Yes. Big "Data/zdebug.txt". Now deleted! Will look forward to new version!

The error appears in 5 seconds or less. Maybe 3. I can't figure out the exact block, but if I copy and paste the blocks over to another session of fxdreema with a new project name I can usually get around the problem.

I'm experiencing a problem. I'm using Win XP, so no permissions problem.

Occasionally fxdreema local will present me with a message in a pink box at the top saying it can't write the file when I click export to .mq4. After this happens my EA seems to be corrupted, and when I try to run it a message in the journal says stack overflow, with no other information other than date, time and EA name.

I then have to re-build my EA from scratch. Has this been noticed before?

......
Clipboard03.jpg

Hello again!

In build 036, you updated the local version to connect to dreema.net and fxdreema.com, which is a good idea. But returning to my old theme, I still think you should somehow allow the local version to start up without an internet connection. I'm sure it wouldn't be hard to allow, say, 25 re-starts before the local version stopped and said it needed to connect to one of your servers. I also think that if you did do this, you should show a count-down on screen stating how many re-starts are available off-line.

The benefit of this is that if someone is unable to connect to the internet, they would not be prevented from working. This can easily happen when travelling and using a laptop, for example.

Anyway, just a helpful (I hope!) suggestion!

...and here's Clipboard02...

......
Clipboard02.jpg

Yes. I might do the TeamViewer thing, but I'll have to check if it breaches the security rules on our system. In the meantime a "phantom block" is a ghost! A block which was created and later removed, but the Variables area seems to think it still exists.

Sadly build 036 didn't fix the issue.

I've created "test_in_local_version" and uploaded the .ex4 and .mq4.

In it I created 5 variables and 4 simple blocks. Then I removed the last block, number 5, which referenced the last variable. Then I tried to delete the variable, and fxDreema said the variable is still used by the now removed block, number 5.

I attach Clipboard01 and Clipboard02 (02 in the next posting as 3 is maximum) showing the deletion of the block then the attempted deletion of the variable.

That is really all there is to see. TeamViewer wouldn't display more to you.

......
test_in_local_version.ex4
test_in_local_version.mq4
Clipboard01.jpg

Glad to see new VPS server up. Logins fast with me.

Still having this phantom block problem. I have a load of variables which I can't delete! Have saved, quit, and re-loaded fxDreema several times.

Hello again!

I'm sorry to come back to this one, but its actually beginning to cause a little difficulty. I now have several variables in an EA which just won't delete, and keep saying they're used in non-existent blocks. Therefore my variables list is getting a little too long..!

Is there a work-around for this you could suggest?

Thanks again.

Yes. You are probably right about the caching.