Hi…
Been thinking about the export/import problem, even if we went with #peterST good petition idea and PRC said they were going to do it, I wouldn’t expect to see for a couple of years.
So other than that its going to be either a compromise solution or data collection/entry.
Currently the is no way, as mentioned to directly import/export the data in question.
However the new PRINT() function could be used to generate a List of the data, then that could be cut/pasted to generate a hard copy in another format .
The image could be input to OCR to convert to editable text. Don’t know how reliable the conversion would be!
Then that to spreadsheet etc.
A thought!…, if the list generated from the PRINT() had an export feature, that would be a start! Maybe that would be an easy/quicker option to implement than a fully export feature.
Next manually/ simple C/C++, or similar simple program could take modified data, store in a text file, use as input to generate a new text file listing the data as variables in PRT array format.
Cut/paste into its own indicator file, and then call it from another with main program code.
When historical data is in file, just add new entries as they come along.
I don’t think you can pass array’s via the ‘call’ instruction however if you link the barindex to the index of the array you can build the history[lookback] of a variable or load a new array over the chart bars from bar zero.
This call/load would only need to be done once, as the chart was build, and then just use similar as close[n] or array etc.
Another idea that comes to mine, is to run as a backtest and the write code to enter at the valid resistance levels and exit at the support level.s. If these execute at the right levels, you could export the data from the detailed report statistics page…..
Might have to build in some alignment offset to align data to known reference point. But entry and exit price could be at same value as required res/ sup levels, if so, exportable.
These are just a few ideas of top of head and untried apart from the ‘call’ bit.
In worst case scenario, boring data entry session.
regards druby
Ps #juld63 been working on a version of your res/sup code idea, will post when ironed a few bugs out for you to pass judgement.