futures io is the largest futures trading community on the planet, with over 90,000 members. At futures io, our goal has always been and always will be to create a friendly, positive, forward-thinking community where members can openly share and discuss everything the world of trading has to offer. The community is one of the friendliest you will find on any subject, with members going out of their way to help others. Some of the primary differences between futures io and other trading sites revolve around the standards of our community. Those standards include a code of conduct for our members, as well as extremely high standards that govern which partners we do business with, and which products or services we recommend to our members.

At futures io, our focus is on quality education. No hype, gimmicks, or secret sauce. The truth is: trading is hard. To succeed, you need to surround yourself with the right support system, educational content, and trading mentors – all of which you can find on futures io, utilizing our social trading environment.

With futures io, you can find honest trading reviews on brokers, trading rooms, indicator packages, trading strategies, and much more. Our trading review process is highly moderated to ensure that only genuine users are allowed, so you don’t need to worry about fake reviews.

We are fundamentally different than most other trading sites:

We are here to help. Just let us know what you need.

We work extremely hard to keep things positive in our community.

We do not tolerate rude behavior, trolling, or vendors advertising in posts.

We firmly believe in and encourage sharing. The holy grail is within you, we can help you find it.

We expect our members to participate and become a part of the community. Help yourself by helping others.

You'll need to register in order to view the content of the threads and start contributing to our community. It's free and simple.

Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.

Need help?1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first.2) Start a journaland post to it daily with the trades you made to show your strengths and weaknesses.3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make.4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance.5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers.6) Help using the forum? Watch this video to learn general tips on using the site.

This sounds Great Mike!
Does this mean, the DLL's created for NT can be imported directly into Easy Language & we don't have to convert the indicator or strategy to Easy Language?

If not I wish there was an easy way to do this, please let me know if you have any ideas on easy portability between NT & Easy Language.

No, it's not that simple.

It just means if there is something you want to do that can't be done in EasyLanguage, you could pass variables to/from a DLL and have your C++ do it.

As for NT -> EL conversion, it is case by case. I suggest creating a new thread here in the EasyLanguage Programming section for each indicator you want converted, attach a screen shot or two and the NinjaTrader .cs source, and then someone can probably covert it.

Mike

Due to time constraints, please do not PM me if your question can be resolved or answered on the forum.

Need help?1) Stop changing things. No new indicators, charts, or methods. Be consistent with what is in front of you first.2) Start a journaland post to it daily with the trades you made to show your strengths and weaknesses.3) Set goals for yourself to reach daily. Make them about how you trade, not how much money you make.4) Accept responsibility for your actions. Stop looking elsewhere to explain away poor performance.5) Where to start as a trader? Watch this webinar and read this thread for hundreds of questions and answers.6) Help using the forum? Watch this video to learn general tips on using the site.

I'm in the middle of trying to convert the (futures.io (formerly BMT) Elite) "Myst" strategy from NinjaTrader to MultiCharts 7.4 which lead me down a path trying to implement some of the toolbar functionality that NT handles natively in C# as a C/C++ DLL. I may go the C# or even PowerBasic DLL route at some point, but wanted to start with the most direct method first. Given I've yet to try to extend MC via DLLs, this seemed like a worthwhile exercise to see what was involved. I read the TradeStation/EasyLanguage PDF references and several postings on the web that specifically state that function prototypes need to be defined as "__stdcall" rather than "__cdecl" but MC was unable to locate the functions I defined via DefineDLLFunc due to the mangling that occurred by declaring the functions as "__stdcall" (e.g. bad_function( int ) is exposed as _bad_function@4).

I shot MC support an Email and they referred me to GlobalVariable.dll which exposes the functions without "mangling" the function names which makes me wonder if they used the recommended "__stdcall" method as well - requests for access to the GlobalVarialble.dll source haven't been answered .

I wrote a quickee C/C++ test harness using "__cdecl" (on Visual Studio 2010) that others may find helpful. I'd still be interested in hearing if anyone has been able to create and call DLLs by defining functions using "__stdcall" - attempts at going that route lead MC to report "Can't find function "blah" in dll.". These functions do nothing beyond returning the value passed, but it's a start (K.I.S.S.).

-Guy

p.s. BTW, wouldn't your example above return a string pointer from a stack frame that may cause "bad bahavior" - just curious - it's been a while since I've dabbled in C/C++...

Thank you Fu510n for posting this code, but I have a trouble to realize it. I copy your text into VC2010(express edition), compile, put the dll to TSSupport\Multicharts folder and after I open PL indicator on chart, i have this message:

Thank you Fu510n for posting this code, but I have a trouble to realize it. I copy your text into VC2010(express edition), compile, put the dll to TSSupport\Multicharts folder and after I open PL indicator on chart, i have this message:

32-bit vs. 64-bit Multicharts? (i.e. the DLL has to match whatever version of Multicharts you are running).

Just a thought,
Guy

p.s. I've since upgraded to using VS2013 Community Edition to generate 64-bit DLLs to use with MC64. The same code above "still works", in addition to a PureBasic variant which generates the exact same output. I can post new/updated sources for both versions if anyone is interested...

...function prototypes need to be defined as "__stdcall" rather than "__cdecl" but MC was unable to locate the functions ... due to the mangling
that occurred by declaring the functions as "__stdcall" (e.g. bad_function( int ) is exposed as _bad_function@4).
...
I wrote a quickee C/C++ test harness using "__cdecl" (on Visual Studio 2010) that others may find helpful. I'd still be interested in hearing
if anyone has been able to create and call DLLs by defining functions using "__stdcall"...

There are two ways to solve the mangling problem.

1) With DEF file: export the function names via a DEF file, there you can name them whatever you want. Specify the functions by ordinal numbers.

2) Without DEF file: Use linker comments. A lot of people will not like it but it's the simpliest way. The pragma statements belong anywhere in the function body.

Both ways work with VS2008 Pro, I can't test with later versions here but it should do.

32-bit vs. 64-bit Multicharts? (i.e. the DLL has to match whatever version of Multicharts you are running).

Just a thought,
Guy

p.s. I've since upgraded to using VS2013 Community Edition to generate 64-bit DLLs to use with MC64. The same code above "still works", in addition to a PureBasic variant which generates the exact same output. I can post new/updated sources for both versions if anyone is interested...

I received a request for the 64-bit PureBasic (5.31) source from another futures.io (formerly BMT) member, so I'll embed below...