HotKey for +1 Breakeven

[Mr.Hamster]

Is there a way to make a HotKey for +1 Breakeven ? So instead of just breakeven , +1 tick positive above breakeven ? Thanks !

[Lancer]

This functionality has been a requested improvement for years, with several tracking ID numbers. Forum members frequently inquire about this, but who knows when this improvement might be addressed.

This hotkey improvement request from a Feb 2020 post here, is being tracked with ID# SFT-2386. Add your vote for this request.
A similar request from a June 2019 post here, is being tracked with ID# SFT-4072. Add your vote for that request as well.
A similar request from a January 2017 post here, is being tracked with ID# SFT-1109. Add your vote for that request as well.

Maybe whoever is managing improvement request tracking should combine all under a single ID#. Better yet, after at least 5 years of requests, actually adding this basic functionality in NinjaTrader would be much appreciated.

[Mr.Hamster]

It would be extremely simple to add . Probably take a programmer like 5 minutes to do . They already have breakeven , just add a option for how many ticks above breakeven .

[NinjaTrader_Kate]

Hello Mr. Hamster,

Thank you for your post.

The correct feature request number for this is SFT-2386. I have added a vote for you to this request.

SFT-4072 is closed and was rolled into 2386. 1109 is for order entry window buttons, not hot keys.

Deciding on features for future releases is not a simple black and white decision. There are many factors involved including but not limited to:

• Demand which is measured by objective user requests and subjective discretion on the part of our Product Management team.
• Feasibility
• Developer bandwidth
• Current projects in the queue
• Economics

You'll find a note regarding your feature request in the release notes when/if a feature is implemented.

Please let us know if we may be of further assistance to you.

[Lancer]

"1109 is for order entry window buttons, not hot keys."

I don't think that's correct. The post where 1109 appears to have originated is here. The thread and feature request that ChelseaB responded to with that tracking number is titled "Breakeven ATM Strategy plus one - Hotkey". Nowhere in that thread dialog leading to the assignment of the 1109 tracking number are order entry window buttons discussed. It is all about a Hotkey. So, if the internal 1109 description focuses on buttons and not hotkeys, then that error needs to be corrected, with 1109 closed and rolled into 2386. Or, if 1109 existed prior to ChelseaB's response, and it concerned buttons not hotkeys, then ChelseaB responded with an existing tracking number not applicable to the subject Hotkey issue.

[Mr.Hamster]

Hello Mr. Hamster,

Thank you for your post.

The correct feature request number for this is SFT-2386. I have added a vote for you to this request.

SFT-4072 is closed and was rolled into 2386. 1109 is for order entry window buttons, not hot keys.

Deciding on features for future releases is not a simple black and white decision. There are many factors involved including but not limited to:

• Demand which is measured by objective user requests and subjective discretion on the part of our Product Management team.
• Feasibility
• Developer bandwidth
• Current projects in the queue
• Economics

You'll find a note regarding your feature request in the release notes when/if a feature is implemented.

Please let us know if we may be of further assistance to you.

Thanks Kate ,

[Mr.Hamster]

I don't think that's correct. The post where 1109 appears to have originated is here. The thread and feature request that ChelseaB responded to with that tracking number is titled "Breakeven ATM Strategy plus one - Hotkey". Nowhere in that thread dialog leading to the assignment of the 1109 tracking number are order entry window buttons discussed. It is all about a Hotkey. So, if the internal 1109 description focuses on buttons and not hotkeys, then that error needs to be corrected, with 1109 closed and rolled into 2386. Or, if 1109 existed prior to ChelseaB's response, and it concerned buttons not hotkeys, then ChelseaB responded with an existing tracking number not applicable to the subject Hotkey issue.

Wow , now that sounds complicated . Glad you can figure it all out Lancer ,