• Get access

Requests & Ideas - page 328

dannyla
241
dannyla  

thanks mladen

were should i look for the file?

in a folder?

Mladen Rakic
163389
Mladen Rakic  
dasssi:
thanks mladen

were should i look for the file?

in a folder?

In "C:\Users\bhageera\Desktop\MT4 Exchange"

Most of the problems with the new metatrader 4 comes from a fact that it switched to unicode (it used to work using ansi strings) and that now string handling and anything related to strings has to be completely rewritten and adapted

RWP
537
RWP  
mladen:
There are some problems in build 654 in some cases when parameters are passed using iCustom() and that is simply stopping the indicator from working. They have promised new update. I hope soon since this is not good

Hi Mladen,

Checking to see if anything has changed since then?

Mladen Rakic
163389
Mladen Rakic  
rayphua:
Hi Mladen, Checking to see if anything has changed since then?

rayphua

If by changes you mean if things git worse, yes, they got even worse with build 660

RWP
537
RWP  
mladen:
rayphua If by changes you mean if things git worse, yes, they got even worse with build 660

Does this mean that the way I need it to be coded cannot be coded with these builds?

Mladen Rakic
163389
Mladen Rakic  
rayphua:
Does this mean that the way I need it to be coded cannot be coded with these builds?

They are changing everything and they again messed up something with parameters passing when iCustom() is called (and that version must do it that way). Those errors were present when they started "upgrading" and some are back again. If they correct it, then it will be possible to make the code as it should be made

RWP
537
RWP  
mladen:
They are changing everything and they again messed up something with parameters passing when iCustom() is called (and that version must do it that way). Those errors were present when they started "upgrading" and some are back again. If they correct it, then it will be possible to make the code as it should be made

Ok thanks for explaining. And you don't have any idea when that correction will be made?

Mladen Rakic
163389
Mladen Rakic  
rayphua:
Ok thanks for explaining. And you don't have any idea when that correction will be made?

rayphua

If I could, I would take a baseball bat and go there and then I think those errors would be corrected fast. But since I can, all I can do is wait till they decide that it is enough of a trading platform full of bugs (even basic bugs like parameters passing in some cases) and that it is time to do it seriosly

From the experience so far, the correct something, then it resurfaces, then they correct it again, then it resurfaces again ... I don't know when are they going to correct those things ... no rule. They do not seem to be too interested in having a correctly working mql

RWP
537
RWP  
mladen:
rayphua

If I could, I would take a baseball bat and go there and then I think those errors would be corrected fast. But since I can, all I can do is wait till they decide that it is enough of a trading platform full of bugs (even basic bugs like parameters passing in some cases) and that it is time to do it seriosly

From the experience so far, the correct something, then it resurfaces, then they correct it again, then it resurfaces again ... I don't know when are they going to correct those things ... no rule. They do not seem to be too interested in having a correctly working mql

lol Mladen,

Not sure if you recall previously coding an indicator where I had similar requirements where I required multiple timeframes and parameters to be used together, wouldn't that method of coding work with this new request or would the previous indicator also not work now with the new mt build?

Mladen Rakic
163389
Mladen Rakic  
rayphua:
lol Mladen, Not sure if you recall previously coding an indicator where I had similar requirements where I required multiple timeframes and parameters to be used together, wouldn't that method of coding work with this new request or would the previous indicator also not work now with the new mt build?

rayphua

I am currently working with build 660 (I use the latest builds in order to be prepared to what is comming) and that build has those errors back and it is not possible to use that method that I have already applied in a less buggy builds normally in this newest build