Dear Support!
I'm very disappointed the bug is still not addressed in the new release 2.6.49.
The bug is so obvious and so easy to reproduce.
May I kindly ask you to have a look at this and provide a fix as soon as possible?
I literally can't work on the standalone api with our strategies with this major bug included.
I've done some further testing to help you locating the bug.
I've tested all basic periods with the function Period.isPeriodBasic(Period).
While in the API 2.6.38 all passed periods were handled as expected, in API 2.6.49 there are several periods that did return null, which means they are not recognized as basic periods.
here is the API-docu:
Quote:
isPeriodBasic(Period) - Static method in class com.dukascopy.api.Period
The method checks whether the passed period is basic {TICK, TEN_SECS, ONE_MIN, FIVE_MINS, TEN_MINS, FIFTEEN_MINS, THIRTY_MINS, ONE_HOUR, FOUR_HOURS, DAILY, WEEKLY, MONTHLY} If it is basic - appropriate basic period is returned If it is not basic - null is returned
The following list shows the results of isPeriodBasic calls with all periods that are listed as basic periods in the API doc:
Period.isPeriodBasic(Period.TICK) -> returns Period.TICK
Period.isPeriodBasic
(Period.TEN_SECS) -> returns nullPeriod.isPeriodBasic(Period.ONE_MIN) -> returns Period.ONE_MIN
Period.isPeriodBasic
(Period.FIVE_MINS) -> returns nullPeriod.isPeriodBasic
(Period.TEN_MINS) -> returns nullPeriod.isPeriodBasic
(Period.FIFTEEN_MINS) -> returns nullPeriod.isPeriodBasic
(Period.THIRTY_MINS) -> returns nullPeriod.isPeriodBasic(Period.ONE_HOUR) -> returns Period.ONE_HOUR
Period.isPeriodBasic
(Period.FOUR_HOURS) -> returns nullPeriod.isPeriodBasic(Period.DAILY) -> returns Period.DAILY
Period.isPeriodBasic
(Period.WEEKLY) -> returns nullPeriod.isPeriodBasic
(Period.MONTHLY) -> returns nullPlease let me also know should you come to different results and your calls all return ok.
Looking forward to your reply,
RR.