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)
yes there are two parts of code that refers to, one is the redraw mapping area and the other is the construction of the ladder itself, maybe you can do me one favour. I have a suspicion it is still the price constant ladder.
Can you switch if off in the parameters and see what is the effect.
Go to the indicator parameters and look for "Price Constant" and set the Show option to "FALSE" instead of true and then try to refresh or reload and see does it still give the same problem?
yes there are two parts of code that refers to, one is the redraw mapping area and the other is the construction of the ladder itself, maybe you can do me one favour. I have a suspicion it is still the price constant ladder.
Can you switch if off in the parameters and see what is the effect.
Go to the indicator parameters and look for "Price Constant" and set the Show option to "FALSE" instead of true and then try to refresh or reload and see does it still give the same problem?
1Lot
Without the price constant ladder it works, any way to narrow the error down some more? Where is that part of the code?
can you try this attached source. I have commented out the code that does some funny stuff with the price constant ladder. If it works I expect you to see a funny price constant but that is fine, so long as it works. Then I know where the problem is.
See attached source file. Just copy over previous source, recompile it and then reload that template. Price Constant ladder must be set back to True so it runs that area of code.
I have to run out, back in a few hours but I believe I have found the error, I just just need you to confirm on that new source file.
Will work on it later this evening when I get back and hopefully by tomorrow we have seen the last of this blue screen.
1Lot
Works fine now, nice work by the way! If NT8 should not come with a really nice DOM, this might be the startpoint for a full blown custom DOM on steroids....(I said before I'd develop one if the NT guys don't so I might jump on board then...) Next steps could be to stick it into a form, then we could easily set rows to display and so on and then hook it up with chart trader, catch the mouse y price and fire preset orders with one click and even manage them with the ATMs...
This is great.
2 great minds work on this together
1Lot's DOM's been working fine for me except for when the market's busy and fast.
It lags seriously.
I don't have the top of line computer and I assumed it is the reason
Anyone tried this during a busy hour?
If it's only me I have a perfect reason to buy a new computer.
This is great.
2 great minds work on this together
1Lot's DOM's been working fine for me except for when the market's busy and fast.
It lags seriously.
I don't have the top of line computer and I assumed it is the reason
Anyone tried this during a busy hour?
If it's only me I have a perfect reason to buy a new computer.
I only had a glance, but my guess would be that it could be optimized quite a bit. Just thinking out loud, so no offense please: It shouldn't be much heavier than my T&S....and it certainly shouldn't lag....
There is some string stuff in the code, that's always expensive...but if it should be optimized, I'd (not saying I will) put it into a separate form and rewrite large chunks. Some code could be stripped down if it wasn't running on a chart... many things could be stored very cheaply in simple int values with an added overflow method...
But all this would take probably weeks to code....
All this is not to discredit @1LotTraders great work but merely to show fields of optimization!
Great news on that find.. I will sort that over the next few days and finally we are rid of that crap bug. I will take my time to make an update as I want to just test it properly. So maybe tomorrow end of day I'll release something.
The issue with market slow down is based on the configuration. What actually slows the DOM down in this format more than anything is in fact the screen refresh rate and redraw of the chart. I have quite powerful machines so I had it turned up when I used it.
It can be the case though where in a fast market the refresh rate becomes to fast and bottlenecks your machine. It is just part of the configuration and one of the reasons I actually created it (ability to tune), if you are using one DOM in one market all day you can afford to raise certain settings. If you are using 3 or 4 on different markets the case is different. With Ninja you have a 1 size fits all and generally it is tuned down so that it will work on everyone's pc's. If I compared mine against the Ninja DOM when it was tuned for my setup it easily outperforms the Ninja stock DOM but as I said must be tuned for your setup.
The tuning options would not be hard to expose. It is mainly the refresh rate and also how many levels in the book will activate a refresh. Ninja themselves are only updating the top bids at a high rate and lower bids at a slower rate, of course they are also limiting to 5 or something where as this DOM exposes all levels of the book.
Ideally for optimal performance you would want a custom form as vvhg has mentioned and start from there. It is not hard and if anyone wanted to take on that project I could offer some help in how to do it.
This DOM was my very first attempt and prototype of a DOM which I was able to throw together fairly quickly with the Gom Volume Footprint as a base, the code is by no means clean or optimal but it is good enough for anyone looking to start out with a book. Ninja's book in my opinion is not very nice to look at. I used this one personally for around 4 months but then built my own book outside of Ninja that routes directly through CQG's API which in the end was a better solution for me personally.
At the end of the day this one can be made to work nicely, I used it for some time and learned to read an order book with it.
Ninja themselves are only updating the top bids at a high rate and lower bids at a slower rate, of course they are also limiting to 5 or something where as this DOM exposes all levels of the book.
All levels of the book? I assumed the futures exchanges only allowed for 5 levels of depth...So Ninja is to blame.
Quoting
I used this one personally for around 4 months but then built my own book outside of Ninja that routes directly through CQG's API which in the end was a better solution for me personally.
Did I understand you right. So you can build a Dom in its own separate window for Ninja? Can you show us a picture please?:-)