[This message was posted by Jason Wheeler of Sanford C. Bernstein <[email protected]> to the "Algorithmic Trading" discussion forum at http://fixprotocol.org/discuss/31. You can reply to it on-line at http://fixprotocol.org/discuss/read/a88db7f3 - PLEASE DO NOT REPLY BY MAIL.]
> One thing missing from the specification is a matrix to show which > ParameterTypes are valid for which Controls. > > Some are very obvious, for example LocalMktDate_t, UTCDateOnly_t, > UTCTimestamp_t and UTCTimeOnly_t only really make sense to be bound to a > Clock_t control. > > All numerical types such as Amt_t, Float_t, Int_t, Percentage_t etc. make > sense to be bound to SingleSpinner_t, DoubleSpinner_t and TextField_t. > > String types such as Char_t, String_t makes sense to be bound to TextField_t, > but string types do not make sense to be bound to numerical controls such as > SingleSpinner_t and DounbleSpinner_t. > > This is by no means an exhaustive list but just a few examples of what does > and doesn't make sense. A matrix representing what is and isn't valid would > certainly make it easier when building an atdl implementation. > > What rules have others applied in this area or have you left it open hoping > that when atdl files are created by brokers they are done in a sensible way ? > > > Thx. Neil. Seems like this would be a decent idea provided there aren't major differences among platform types and that it doesn't necessarily prohibit something that may be unusual but is still allowable (which can lead to inventive solutions). [You can unsubscribe from this discussion group by sending a message to mailto:[email protected]] -- You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/fix-protocol?hl=en.
