Question on Target order limit...

[Alfred]

In screen shot 1 below...have the Stop Limit Offset set to Off... and Use Stop Market set to True in both the DOM & Chart Trader...yet clicking on the order target in the DOM there is a limit of 2 offset showing...is this correct...should'nt this be auto set as "0" in this case...??

Also...if you then close out the trade before closing the check mark box on the target...the check mark box remains showing in the DOM...screen shot 2 below...then if you close the check mark box there is still a red X showing in the DOM....screen shot 3 below...

Thanks....

[NinjaTrader_Jason]

Hello Alfred,

The numeric box in the screenshot does not indicate the offset but quantity. Clicking the size marker of an active ATM order will cause a numeric box to appear. However you can change the quantity of the order using this numeric box - it does not relate to the offset.

I am able to reproduce the issue you report in the second paragraph. I will forward your findings to Development. Thank you for reporting.

[Alfred]

1 more question...had the quantity set to 1 in the DOM...(screen shot 1 below) ....so is the 2 showing in the check box necessary rather than 1 ??

If you set the Stop Limit Offset to a value in the DOM & Chart trader properties , (and have Use stiop market set to false) does that value then apply to both entrys and targets ?

Thanks...

[NinjaTrader_Jason]

Hello Alfred,

When clicking the size marker of an ATM order, it will automatically reflect a value that is 1 more than the original value.

The 'Stop limit offset' setting in the Properties menu only relates to stop limit orders that are submitted manually. It does not relate to stop limit orders submitted as stop loss. These stop losses use a default offset of 20 ticks which cannot be changed. This is to ensure the market does not trade through the order.

[NinjaTrader_Jason]

Hello Alfred,

I have been informed we will leave the issue you reported initially. This is a very rare non-impacting situation and fixing this issue will touch sensitive code in the SuperDOM. The risk imposed to resolve the issue does not outweigh the nature of this bug.

Thank you again for reporting.