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)
The last post by Vegas highlights another problem. Having lots of indicators does not seem to have a direct effect on performance. But as the dropdown list of indicators gets longer and longer, it becomes harder and harder to find the one you are looking for.
Especially since there is no rhyme or reason to the way in which they are named, which will dictate the (alphabetical) order in which they appear in the list. Which I have also addressed.
The order of the list of available indicators seems to be alphabetical, and the order of the list of applied indicators seems to be the order in which they were added. I name all my personal indicators 'A1...' so that they will appear at the top of the list of available indicators
The indicator drop down list IS alphabetical. That doesn't help if the names that appear in the list are inconsistent and randomly assigned.
If an indicator does not have a Name property, ( this.Name, assigned in Initialize() ) its class name will appear in the indicator list. (An indicator is a CLASS object that is a member of the Indicator NAMESPACE.)
Class names cannot include any spaces or punctuation marks. But the Name property is a string object that CAN include spaces and punctuation marks. It can even include ʂPĒcıÅŁ cĤãɌȀc˦ερΣ ®.
So the key to organizing your indicator list is a systematic naming convention taking advantage of the flexibility of the this.Name property. Most programmers don't bother to specify any value for this.Name.
To add to the confusion there is also the Windows FILE NAME for the cs file. The Windows file name, the class name, and the this.Name should have some consistency.
I just switched to Sierra charts... IMO, for a high level trader without deep programming knowledge... it is so much better than NT. Drawback for Sierra is you need a high performance CPU as it really loads up your CPU!
At least I can breath easier now.
Wish to see expert programmers put more thoughts on Sierra...
Sierra Chart is much easier on CPU load than Ninja, IMO. You must be doing something a lot different.
Sierra Chart is fast, lean, and very stable. It is extremely flexible, allowing the user many configuration options. It has built-in Excel-compatible spreadsheet studies that can do even more things, without C++ programming. And if you are a programmer, their C++ based ACSIL language will allow nearly unlimited flexibility and power. It has a hundred indicators, many chart types, many bar types. And all for less $ than Ninja. I'm never going back.
This statement is a bit simplified. Both NinjaTrader and SierraChart are excellent products that can be recommended. NinjaTrader is fast, lean and very stable, if you do not use fancy, CPU hungry custom indicators. Did you ever make a comparison of the features of both software packages?
You could start a new thread as this is certainly not the place to discuss Sierra Chart.
