I'am getting this error, very simple one:
Posts made by owneroxxor
-
RE: fxDreema Updating Nowposted in Questions & Answers
@fxDreema Everything in this Project was compiling OK. I just entered to change a variable and then compile again and got all those erros on block 34. Something has changed, but I didn't touch that block for long time
-
RE: fxDreema Updating Nowposted in Questions & Answers
@fxDreema Really need to keep constructing my robot, when can we have the system normalized?
-
RE: fxDreema Updating Nowposted in Questions & Answers
I'am having same problems ast eclwartsleer, ndt113
-
RE: SERVER IS LAGGGGY.posted in Questions & Answers
Hm... Yes I can. It happens EVERY time I logout and then try to login.
Wanna try out some test or anything? -
RE: SERVER IS LAGGGGY.posted in Questions & Answers
Oh ok. Somehow when I was trying to download the .EX5 from chrome of my pc, it never downloaded. So I entered in my cellphone chrome, and it downloaded like in 5 seconds, worked everytime. Don't know what happened. Now the chrome of pc is working fine. The wifi was the same for both
.BTW, talking about other thing: When I have to fill my password to enter fxDreema, it ALWAYS shows ERR_LOGIN. Then I ALWAYS have to get a new password from email to enter the website. Its damn pretty anoying thing.
Thanks.
-
RE: use of P1/P2/P3... always return compilation errorsposted in Bug Reports
Why when I try to use those variables, they return compilation erros, at ALL cases?

http://prntscr.com/aqh2wwBTW, the "P3" in the formula "P1-P3" in the yellow box is tricky. I set the formula to "P1-P2".Then I hit "Update". When I open that box again, the formula now is "P1-P3"
something is going wrong here.BTW: the compilation error occurs for ANY use "P" variables, P1,P2,P3,P4,P5,P6....
-
RE: SERVER IS LAGGGGY.posted in Questions & Answers
Just cant compile my .EX5 files for hours... What is happening...?

-
RE: "Position closed" box not identifying partialy closed onesposted in Questions & Answers
Just look the SS:
http://prntscr.com/apiy4qWhen the Partial close is made, the "position closed" block dont pass. Why?
-
RE: BUG (On Trade Event)posted in Bug Reports
Why the symbol? lol The symbol is ok. WDO$ mean, W-web DO-dollar $-all historical. Well I made it out using "Turn off/on" blocks. Anyway. I tryed to use the "Once per position/order" twice in 2 regions of my EA, none of them worked, returning that ugly error. Just for you 2 know.
Thanks.

-
RE: BUG (On Trade Event)posted in Bug Reports
Ok, the routine is causing the "BUG". When I disable it, it works. BUT, still not right, because I need this routine working.
So I tried to just wipe that "Position Closed" box and put a "For each closed order" loop right after the "PASS" block, but with a "Once per position" box inside it, to prevent it from withdrawaling the same last position all times "On trade Event" tab gets activated. Logically it should work all times it see's a fresh new closed position on the Foreach Loop that is not a CANCELED one (Check Profit Condition Box). but look:
http://prntscr.com/alry5uhow to overcome this?
The "Once per position/order" box is causing this, btw.
ty
-
RE: BUG (On Trade Event)posted in Bug Reports
I think I got it. After any position get closed by a stop-loss, in my "On tick Event" there is a routine that: once there is less than two orders into the graph, it CANCELS all the current pending orders and create two new. What happens is that just before the "On trade Event" which makes the withdrawal after the stopped position, the EA executes this routine that cancels the pending order that remained, and I think the "Position Closed" box on the "On trade Event" doesnt recognize CANCELED orders as a trigger. So the block doesnt pass. Am I right in saying this?
-
RE: BUG (On Trade Event)posted in Bug Reports
Dude, help me, I really think there is something going wrong here.
Looking at this SS, we see two stop-losses trades happening at the same day: http://prntscr.com/alqjim
The first stop-loss trade did not pass the "Position Closed" block. But the second did.

You can see the blue dot that shows that the "On Trade event" tab got activated correctly, but, somehow, the just the second trade got passed in the "Position Closed" block.
Btw, no other SL positions passed the "Position Closed" block after this succesfull one

How could it be explained?

Last edited by owneroxxor on Tue Mar 29, 2016 11:06 pm, edited 1 time in total. -
RE: BUG (On Trade Event)posted in Bug Reports
Dude, help me, I really think there is something going wrong here.
Looking at this SS, we se two stop-losses trade happening at the same day: http://prntscr.com/alqjim
The first stop-loss trade did not pass the "Position Closed" block. But the second did.

You can see the blue dot that shows that the "On Trade event" tab got activated correctly, but, somehow, the just the second trade got passed in the "Position Closed" block.
Btw, no other SL positions passed the "Position Closed" block after this succesfull one

How could it be explained?

-
RE: BUG (On Trade Event)posted in Bug Reports
Nice! the assembly bug is gone.
Now got a new one, look at this: http://prntscr.com/alkfibOk, when some position get closed by the "Close positions" blue box into somewhere into by "On Tick Event", it activates the Screenshots's purple block "Position Closed" on the "On Trade Event" tab and it gets traced by the pink line and the withdraws are made perfectly.
BUT, when the positions gets closed by a STOP LOSS, it does not activates the the "Position Closed" box, and it does not make the withdraws of the comissions. Look: http://prntscr.com/alk8ff
The "Position Closed" purple block is not recognizing Stop-loss closed positions.
Can be fixed or made in another way?
ty
-
RE: BUG (On Trade Event)posted in Bug Reports
Dreema, look at this: http://prntscr.com/al8toa
My EA is working perfectly. But, when I put anything on the "On Trade Event", it crashes, right in the close of the first trade it makes:
http://prntscr.com/al8v9lWhat I wanna do is a Money withdraw after every order closed. This "money withdraw" would simulate de comissions paid into the backtests.
Know something better to do this? Can we fix this bug?
ty
