The difference between input validation and confirmations came up in this thread:
https://ninjatrader.com/support/foru...082#post538082
There is a huge difference. My request is to offer validation in several windows that have a form-like workflow even though this platform is a WPF app and not Windows Forms.
By form-like I mean several input controls and then the data is parameterized and collected all at once with a "submit" button for further processing. To keep the data clean primitive textboxes are avoided because they allow all sorts of invalid input.
This is already being done by use of specialized input controls with type, format, and value restrictions: a selector with known list of items, the QUD with quantity int value >0, etc.
Usually validation is implemented via binding of the control — a MessageBox or some warning red label TextBlock toggled visible right on the window itself, or a ToolTip etc, when the user is trying to input impermissible values. Or the control can just do the restriction silently and not even tell the user why a "?" character is being ignored for a phone number input. This is exactly the behavior of the QUD. If the user inputs "T", or "0", the control changes it to "1" with no explanation why.
However, the Order Ticket input controls are still static. They offer no or little interactive behavior between the controls like binding or selection changed event handlers. If instead of two buttons, BUY and SELL, there was an ActionSelector combobox with Buy/Sell/SellShort/BuyToCover items, then a lot more logic could be implemented at input time.
For example there should be validation method that uses four different parameters: OrderTypeSelector.SelectedItem, LimitPriceControl.Value, ActionSelector.SelectedItem and MarketData.Last to generate a warning against any of these improper orders:
https://ninjatrader.com/support/foru...186#post538186
Newbies to trading, or experienced traders new to the platform, especially if doing a trial prefer more hand holding.
So in the Order Ticket or the Basic Entry where there is plenty of real estate, it would be nice to have a validation label visible telling the user why the platform changed her QUD input of 0 to 1, or why StopLimit out-of-the-money is invalid and will be rejected. Since it is a worksheet-like logic it is much nicer to get the validation feedback right at the time of the bad or questionable input rather than waiting for an after-the-fact confirmation. Even worse is the fait accompli rejection after the order was already improperly submitted. The worst is to let the order reach the broker or the exchange.
I don't use these order entry windows but I noticed that throughout the platform there is very little use of validation messages and they can be much more intuitive and feedback timely.
The levels of these messages can be tailored as:
Thanks
https://ninjatrader.com/support/foru...082#post538082
There is a huge difference. My request is to offer validation in several windows that have a form-like workflow even though this platform is a WPF app and not Windows Forms.
By form-like I mean several input controls and then the data is parameterized and collected all at once with a "submit" button for further processing. To keep the data clean primitive textboxes are avoided because they allow all sorts of invalid input.
This is already being done by use of specialized input controls with type, format, and value restrictions: a selector with known list of items, the QUD with quantity int value >0, etc.
Usually validation is implemented via binding of the control — a MessageBox or some warning red label TextBlock toggled visible right on the window itself, or a ToolTip etc, when the user is trying to input impermissible values. Or the control can just do the restriction silently and not even tell the user why a "?" character is being ignored for a phone number input. This is exactly the behavior of the QUD. If the user inputs "T", or "0", the control changes it to "1" with no explanation why.
However, the Order Ticket input controls are still static. They offer no or little interactive behavior between the controls like binding or selection changed event handlers. If instead of two buttons, BUY and SELL, there was an ActionSelector combobox with Buy/Sell/SellShort/BuyToCover items, then a lot more logic could be implemented at input time.
For example there should be validation method that uses four different parameters: OrderTypeSelector.SelectedItem, LimitPriceControl.Value, ActionSelector.SelectedItem and MarketData.Last to generate a warning against any of these improper orders:
- StopLimit order out-of-the-moneyBuy StopLimit below the market
Sell StopLimit above the market - Limit order in-of-the-moneyBuy Limit above the market
Sell Limit below the market
https://ninjatrader.com/support/foru...186#post538186
Newbies to trading, or experienced traders new to the platform, especially if doing a trial prefer more hand holding.
So in the Order Ticket or the Basic Entry where there is plenty of real estate, it would be nice to have a validation label visible telling the user why the platform changed her QUD input of 0 to 1, or why StopLimit out-of-the-money is invalid and will be rejected. Since it is a worksheet-like logic it is much nicer to get the validation feedback right at the time of the bad or questionable input rather than waiting for an after-the-fact confirmation. Even worse is the fait accompli rejection after the order was already improperly submitted. The worst is to let the order reach the broker or the exchange.
I don't use these order entry windows but I noticed that throughout the platform there is very little use of validation messages and they can be much more intuitive and feedback timely.
The levels of these messages can be tailored as:
verbose for newbies;
concise for intermediate users;
none for expert users
Or, as is already the culture of NinjaTrader, just let the user mix and match!concise for intermediate users;
none for expert users
Thanks
Comment