BobbyT » Sun Nov 20, 2016 4:01 pm wrote:
Well it seems I spoke too soon. And I've tracked down the issue. Shit just got real!!!!
So I have recently migrated all my terminals to /portable to stop them from sucking up my SSD with chart data.
It seems that even though the installs have been made portable and 'all the appropriate files have been moved', upon code compilation, MetaEditor still placed the ex4 in the original roaming directory.
Now I would have thought that with both the terminal and the editor pointing at the install directory and not the roaming directory that the editor would place compiled files in the install directory (you know, where it's actually running from.
I can't find anything in the editor options and can't find an editable config file to check there for some stray settings.
I guess the question now is, do you, or anyone else for that matter, know how to force MetaEditor to compile to the install directory? I would have though a /portable tag would work here too but not sure how to apply it to the terminal hotkey. I would like to avoid having to fully uninstall/reinstall. It took me 2 hours just to move everything this morning. And now the markets are open
Cheers,
BobbyT
Aaaaaaannnnnd, the embarrassment continues. Turns out MetaEditor will stay linked to the roaming folder so long as it exists. Delete it and ex4 go where they should.
Oh happy days!