Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Thanks for your answer. The chart scrolling isn't the problem, i've already done that. I thought that enhance the DLL from uni- to bidirectional communication were a good functionality for a common NT AddOn DLL framework. Still happy to follow your thread.
Sorry for also off-topic, let's take it elsewhere, but:
Two thoughts:
1) Would you be interested in sharing the chart scrolling/positioning code? a few of us would find that useful.
2) For your particular problem have you checked out the TriggerCustomEvent Ninja approach? That way you could use the timer event or send Windows events and service them.
It is probably good to make the code on the NT side the master in terms of push/pull
for threading and consistency reasons
The code you have running on NT can push things to a method in your DLL
and the code can Poll the external side by call another method, which is a 'poll'.
This allows to communicate both ways, only it's not real-time.
Alternatively you can use 'loose coupling'.
I have done another implementation, where the code could not be linked together, due to .NET 4.0
and i made a stand alone process that was listening on a TCP/IP socket with the .NET 4.0 software,
so i didn't have to load the code in the NT memory address space.
I have a feeling that this second approach is closer to what you want to do.
Great idea and I'd love someone else to do it, otherwise I will do it when I've got KeyTrader finished, an update for ChartMinder out, a month's trading and 2 week's vacation out of the way. Ok, this primadonna over and out.
You might be able to get an example of "TriggerCustomEvent" from the LOM software. I believe I had to integrate that for certain events to work properly.
Thanks for the detailed tutorial.
Quick question about the usage: If the dll is recompiled and overwritten does NT need to be restarted or is a simple reload strategy enough to load the updated dll?
There are certainly experts that can answer this question, but if you import the DLL I would say it is okay to use. Overwriting seems like you need to force the system to recompile at a minimum as I think it collects the .NET files into cache files. I don't know that you need to restart, but you should recompile. I would say a reload might not even refresh the contents of the strategy, so I would recompile always.