NakedMarkets Forum

Thanks again Khan for your help.
It's weird because we still are not able to reproduce the issue. We will allocate all the time needed on this matter since lately we had to prioritize other items (since this bug is not considered as critical).

Thanks for your suggestion. As you can understand, these user requests can have a significant impact on the user experience. So, we have to think about it at first how to implement it. The goal for us is to implement a user request feature in a way that is useful for the maximum number of users. So ...

Thanks but technically it's already the case, the users can resize it horizontally.
But maybe you're working under a low resolution ?
It's still possible to authorize a smaller horizontal size if needed

In this case, this item will see its priority increase on the roadmap.
Thanks for your suggestion

Hello, The new release is now available, it adds some news features and fixes few bugs. So, here is the changelog for this 1.0.8602 version : - [Roadmap] Fibonacci Extension Graph object added Additionally, the TradingView Fibonaccis object edition has been improved to be the same as Trading View. -...

No worries Khan, thanks for your report ! At the moment, we are not able to reproduce the issue on our side from a freshly created backtest. We used your backtest file and when we look at the current opened chart, there is indeed an issue. However, if we open a new chart under your backtest, everyth...

Okay, yes, indeed, at the moment, it's possible to change the style/color of the indicator only after being attached, from the related rule.
Yes, we could add the style parameters inside the rule to define the style/color before being attached. We will add it to the roadmap.

Hello,

Yes, sure, you can change the default color when attaching the indicator, by clicking on the "style" tab if your under the Tradingview theme or by changing color under the Metatrader theme.
You can change it by editing the indicator as well

Hi,

Thanks for your report, it has been fixed in the latest release.

Hi,

Thanks Khan for your report. For information, this bug was present only for previous backtest files with specific settings.
It is now fixed in the latest release.