i would really like an auto saving of workspace files like word would do things.. if you crash out or NT crashes it would notify you that you have a saved workspace that you were working with before you crash and if you would like to bring that one back to life.. lets bring this puppy up-to-date..
dont believe anything you hear and only half of what you see
NJ7 uses two different ways to populate its color choices in drop down menus when the user is color coding his
tools or indicators. One of these ways is much much easier and faster, imho, than the other. And I would suggest NT8 lose the one and recreate it using the method of the other. The easier one can be viewed when choosing to change the color of an existing indicator, for example, a Mov Avg line. For such a change as that, the color can be accessed through the Properties dialogue box under Plots, which shows the color currently chosen in a little box. When that drop down menu is expanded, the colors are listed and grouped by their similarities to each other, from top to bottom, darker to lighter for each main category of color. The names of the colors are listed and can be used in programming code, but for regular use, who remembers these obscure names anyway? So the vertical listing by color group is ideal. But the other method employed, when changing a color of a drawn line, for instance, does not group colors into common classed, but instead, lists the colors by their alphabetical names, ascending order. This makes the viewing of the color universe jump back and forth from red to green to yellow to black and all the nuanced shades inbetween mixed up like a ransacked box of crayons. ...all to serve the alphabetical hierarchy within the drop down menu. it's a pain. Group them all by color commonality and the slider allows quick scrolling to the desired area. Leave them in alpha name order and add annoying and wasted time trying to rediscover and replicate a color chosen previously for some specific class of user preference trend line.
I trade about six instruments, but some of them Live and others SIM.
I would like someway to mark on the chart if that instrument is set to SIM or the Live account. At present you have to maximise Chart Trader to see this.
Even if it was done by colouring the Chart Trader Maximise arrow/button to be the same colour as the the Chart Trader window - my Chart Tradeer background colour is set to yellow for SIM and the default colour for Live account.
I understand we cannot access 'Get.Account' to create our own indi to do this now.
I would also like the option of NT requiring a password when it first boots up. At the moment if my computer was stolen from home, some one could easily start up NT and trade my Live account.
The following user says Thank You to steve2222 for this post:
Ninja does too - you set it in the configuration which is part of your user profile, and on the computer. This is QUITE accepted practice, especially in larger companies ("single sign on"). Every password they would set on their end is bullshit anyway - it has to be stored somehow in your local system, so it can be bypassed (if not cracked then reset). Having a Ninja password would with 99% chance be false security.
Alternatively they COULD allow configuring a ocnnection WITHOUT password, then asking for the password on connect - that would be safe as the password to your broker would not be stored on your computer.
The following 3 users say Thank You to NetTecture for this post:
I have often wondered why this hasn't been brought up more often as a concern... not a programmer, but don't think this would be that difficult to add...or not that it would be that big of a concern...but what about the ability to password protect your chart...ie not being able to open up a chart and change the settings or add an indicator from a chart unless password protected... could also password protect the ability to open a dom...just some thoughts...and no i am not being paranoid...I am sure some of this could be concerns for those that might not trade from their homes...
The following user says Thank You to fesx for this post: