The previous Import feature.

[GTElite]

Hi,

I was using the previous V2.1 for a long time and I loved it. Now I've updated to V6.1 and I don't see that feature anymore. Has it been discontinued and if yes, are you going to bring that function back? Being a trader[time is money] and it's a pain writing all that info down at every station that I go to. Regardless, I still like this tool for all my trades. Thanks again.

[Forecaster]

Import feature? For importing what? If you're talking about something in the original Cmdr's Log know that I'm not the original author of that. Cmdr's Log Continued is a complete re-write with no relation to ArchV1 except the similar concept.
If there is a feature you want in CLC you need to explain it, preferably with a use-case if applicable. I can then decide if it's something I want to work on or not.

[GTElite]

Sorry about that. Thought you were the original author. The feature of V2.1 that I was mentioning is a connection to the EDMarketConnector Tool. The EDMC imports the system/station's market info into a CSV file and the CMDR's Log exports into CMDR's Log[not including rares]. Let me know is you need more details. I'll be glad to help as best as I can.

[Forecaster]

@GTElite So, I've been away for a while, but I should really try to get back to working on this, and I've decided that allowing importing data from market apps is not unreasonable I suppose. While I don't play that way and consider it cheating I want to provide an application that is useful, and frankly manually entering market data from even one station is pretty tedious, and relying on the Journal API means it only updates commodities that are bought or sold.

But to implement this I'm going to need examples of the data from the application you want support for. If you could provide a couple of exported files that I could use that would be great.