MetaTrader 4 Client Terminal build 610 - page 31

New comment
  
// I do not know if this was already fixed but in 6.10 the "//" comment delimiter is not recognized on same line with the "extern" like this:

extern string  m01Dat="2014.01.03 00:00";    //"2012.05.11 00:00"  (it does not display properly in the Inputs Property window)

//The comment must be written on the separate line like like this:

extern string  m01Dat="2014.01.03 00:00";
//"2012.05.11 00:00"

Is that a BUG?
 
sub:

Well, I am using Print to see what is inside the double. I believe that if I can't truncate to 4 or 5 digit the triggering and math will be unstable. This problem did not existed on the prior 5.9 version.

Notwithstanding the Print() function, in prior version if I had a problem with a triggering, usually when testing for "0", I would truncate by using NormalizeDouble() -- so how do you truncate?



The only difference from build 509 is the way doubles are Printed . . . you need to understand the issues of comparing double values, red this and understand the issue, it will help: Can price != price ?
 

I am giving up reporting bugs, they tend to close them without a fix.

So, perhaps we may share some "advanced features" of 617 in clips :)

>
 

Another advanced feature (certainly not a bug, it has been rejected).

Setting the indicator height to 20 and then to 0 and again.

>
 

Another cool feature:

Dragging the mouse pointer above (empty and naked) chart drains incredible power resources. Even with mouse events switched off.

 
Brilliant.
 
Ovo:

Another cool feature:

Dragging the mouse pointer above (empty and naked) chart drains incredible power resources. Even with mouse events switched off.


Trevhib:
Brilliant.

Why the hell are you using such poor software ? Are you masochistic ?

By the way, your sarcasms are not welcomed on this forum.

 
angevoyageur:

Why the hell are you using such poor software ? Are you masochistic ?

By the way, your sarcasms are not welcomed on this forum.

Is it really necessary to be so aggressive ?
 

Hello,

I'm facing some strange behavior in new build 610 (I'm not very sure if it was in 604 or in 600). When I'm doing optimization in strategy tester, I got some list of results. And when I choose one of them to run; the profit, number of trades, draw down are not the same as in the optimization results, even the graph goes to negative results. This should be something related with my code, but I'm %100 sure that it was not like that in build 509.

I'm using high quality data, same period is of course chosen and my code does not include any random behavior and just standard indicators.

I went through my code (which I cannot unfortunately share here) and I suspect two things:

1-) I'm using Time[0] to control stop order expire dates and when the current time Time[0] is bigger than the expire time of the order it deletes the ticket. This code was running perfect since last 6 monhts, may be the behavior of Time[] comment has changed. Any suggestions? (There are no run-time errors even in visual mode)

 if(TA2_ASE_Buy_N==true && Time[0]>=TA2_buystop_expire) {
      Alert("Deleting TA2 ticket");
      OrderDelete(TA2_ticket_buy);   
      }  

2-) When I first upgraded to Build 574, I was facing many conversion warnings, warnings like "possible use of uninitialized variable" . However they have disappeared after build 604. Do you think that I should deal with this type conversions and arrays and the problem lies here? If so how can I see these warnings again?

Thanks for your help in advance. This is a big headache for me and I should find the issue in my code.

Any other suggestions also very welcome.

 

By the way I see that when we choose

#property strict

Now I can see the old warning messages that I have stated in 2.

However with #property strict the optimization does not bring any values and completes in a second, in other words does not work.

I'm not very sure if I want to run the code compliant to old compiler. However the warnings I faced when I enable #property strict was not available in 509. Should I now need to correct them or not?

Some of the warnings are as below:

implicit conversion from 'number' to 'string' AB_118.mq4 1657 125

implicit conversion from 'number' to 'string' AB_118.mq4 1658 139

possible loss of data due to type conversion AB_118.mq4 1688 16

possible loss of data due to type conversion AB_118.mq4 1690 11

implicit conversion from 'number' to 'string' AB_118.mq4 1715 125

implicit conversion from 'number' to 'string' AB_118.mq4 1716 139

possible loss of data due to type conversion AB_118.mq4 1790 16

possible loss of data due to type conversion AB_118.mq4 1792 11

possible loss of data due to type conversion AB_118.mq4 1857 16

possible loss of data due to type conversion AB_118.mq4 1859 11

possible loss of data due to type conversion AB_118.mq4 1916 16

possible loss of data due to type conversion AB_118.mq4 1918 11

possible loss of data due to type conversion AB_118.mq4 1984 18

possible loss of data due to type conversion AB_118.mq4 1997 18

possible loss of data due to type conversion AB_118.mq4 2009 18

declaration of 'per' hides global declaration at line 75 AB_118.mq4 2086 20

possible use of uninitialized variable 'df' AB_118.mq4 2105 32

possible use of uninitialized variable 'df' AB_118.mq4 2107 8

possible use of uninitialized variable 'aust' AB_118.mq4 2131 56

possible use of uninitialized variable 'aust' AB_118.mq4 2132 29

possible use of uninitialized variable 'aalt' AB_118.mq4 2135 56

possible use of uninitialized variable 'aalt' AB_118.mq4 2136 29

possible use of uninitialized variable 'aust' AB_118.mq4 2157 56

possible use of uninitialized variable 'aust' AB_118.mq4 2158 29

possible use of uninitialized variable 'aalt' AB_118.mq4 2161 56

possible use of uninitialized variable 'aalt' AB_118.mq4 2162 29

possible use of uninitialized variable 'aust' AB_118.mq4 2183 56

possible use of uninitialized variable 'aust' AB_118.mq4 2184 29

possible use of uninitialized variable 'aalt' AB_118.mq4 2187 56

possible use of uninitialized variable 'aalt' AB_118.mq4 2188 29

possible use of uninitialized variable 'arr' AB_118.mq4 2220 6

possible use of uninitialized variable 'arr' AB_118.mq4 2245 6

possible use of uninitialized variable 'arr' AB_118.mq4 2271 6

possible use of uninitialized variable 'arr' AB_118.mq4 2297 6

possible use of uninitialized variable 'arr' AB_118.mq4 2325 6

possible use of uninitialized variable 'arr' AB_118.mq4 2351 6

possible use of uninitialized variable 'arr' AB_118.mq4 2378 6

possible use of uninitialized variable 'arr' AB_118.mq4 2402 6

declaration of 'k' hides local declaration at line 2414 AB_118.mq4 2415 12

possible use of uninitialized variable 'arr' AB_118.mq4 2425 24

possible use of uninitialized variable 'arr' AB_118.mq4 2426 6

declaration of 'k' hides local declaration at line 2440 AB_118.mq4 2441 12

possible use of uninitialized variable 'arr' AB_118.mq4 2451 24

possible use of uninitialized variable 'arr' AB_118.mq4 2452 6

possible loss of data due to type conversion AB_118.mq4 2473 27

possible loss of data due to type conversion AB_118.mq4 2474 28

possible loss of data due to type conversion AB_118.mq4 2475 28

possible loss of data due to type conversion AB_118.mq4 2476 28

possible loss of data due to type conversion AB_118.mq4 2485 27

possible loss of data due to type conversion AB_118.mq4 2486 28

possible loss of data due to type conversion AB_118.mq4 2487 28

possible loss of data due to type conversion AB_118.mq4 2488 28

implicit conversion from 'number' to 'string' AB_118.mq4 2575 23


1...24252627282930313233
New comment
Reason: