Hi Support,

I need to replace the default template in effect after calling Context.openChart(FeedDescriptor fd) in light of the reluctance* to support some kind of Context.openChart(FeedDescriptor fd, {SomeType} template) call (*number of old messages/requests observed).

<node name="ChartTemplate">
      <map>
         <entry key="currentChartTemplateSettingsFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="currentChartTemplateFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="currentTemplateSettingsFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="currentTemplateFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="currentTemplate" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="defaultChartTemplateSettingsFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="defaultChartTemplateFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="defaultTemplateSettingsFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="defaultTemplateFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="defaultTemplate" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="templateFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="templateSettingFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="templateSettingsFilePath" value="/home/x5/JForex/Templates/hm.tmpl"/>
         <entry key="template" value="/home/x5/JForex/Templates/hm.tmpl"/>
      </map>
</node>

None of the above make a difference. Many thanks.

Templates are not part of the API. Hence, it is not advised to rely on specific template xml format, as it subject to change.

I absolutely agree. Nonetheless my objective within the testing harness I am running within the platform is to open additional charts that should look like the first chart opened by (and specifed via templating in) the historical tester. The default tick chart that opens on the platform when you click on an instrument, backtest without a specific template or indeed open additional charts while backtesting I speculate can be influenced by the XML node above. I'm not asking you guys to provide guarantees about the format or its period of stability prior to any unforeseen change. I am looking for ways to enhance my existing workflow with the support (albeit temporary) of a platform provided by the best broker in retail trading.

I assume all responsibility for my decisions and antics and will happily accept a reply in private if that alleviates concern.


Previous requests with respect to this provision have included a response mentioning XML. I feel API support for templates need not concern XML insofar as the XML is generated and named on the platform and any reference to it from the API would only have to name the template e.g. myMAsetup.tmpl for the platform's openChartTemplate provision to do the rest. It's highly unlikely that one attempting to support API templates would do it in a way requiring endusers to write and maintain their own templates; despite the existence of XML DTD validation.

Could you please elaborate what parameters to the newly opened chart you would like to set?

BASIC Interpreter version 2.8.0. All Rights Reserved
1 REM Elaboration of the perceived problem leading to the approach and question above
2 DIM $MyResearchEnvironment = "STANDALONE"
3 PRINT "Historical Tester under standalone doesn't support opening charts"
4 PRINT "Solution: Give up on the ITesterClient.openChart(fd) feature request and work in the platform"
5 $MyResearchEnvironment = "PLATFORM"
6 PRINT "Configure backtest templates (and hence parameters) for easy viewing of custom research indicators"
7 PRINT "No openChart(fd) templates - chart theme and presentation utilities only work under standalone"
8 PRINT "Solution: Give up on the platform and work under standalone"
9 GOTO 2
RUN
ERROR 666 <ParsingViolation> - No Active Vars precede line 9
HELPMSG 666
MSG 666: Infinite loops with no active constituent variables run counter to reason and hinder productive workflow
DELETE 1-9
Language buffers cleared