[This message was posted by Greg Malatestinic of Jordan & Jordan <[email protected]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/a467892b - PLEASE DO NOT REPLY BY MAIL.]
>From an implementer... 1. TextField_t – establishing a width for this control – you’re correct – you could derive a field width from Parameter/@maxLength. Perhaps you should point this out as being the appropriate way to size text fields? (NB It would be clearer if the definition for maxLength and minLength read “The maximum/minimum allowable length of the parameter in characters.”) 2. Can StrategyPanels contain both controls and other panels? Actually the answer is in the entry for ‘StrategyPanel’ in the table on page 21: “Container for either groups of parameters or strategyPanels, but not both.” – perhaps the “not both” should be in bold, and also should it rather read “…groups of Controls or StrategyPanels…? 3. Bordering on panels – as per the entry for ‘StrategyPanel/@border’ in the table on page 36, the current list is: • None • Line • RaisedEtched • LoweredEtched • RaisedBevel • LoweredBevel As mentioned, I would argue that this level of detail puts an unnecessary burden on the implementer, and is stepping a little on the toes of the OMS/EMS in terms of presentation/look-and-feel. I think it would be better to stop at None and Line. I hope this is helpful. [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.
