[FIX] Numeric_t.constValue and stateRule to clear fields

Mon, 10 Aug 2009 12:26:41 -0700 

[This message was posted by Dev Ashish of Lab49 <[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/6c15bf9a - 
PLEASE DO NOT REPLY BY MAIL.]

2 questions:

1) Numeric_t is the only parameter type which seems to be missing const and 
constValue attributes. Any particular reasons for this?

2) What are the thoughts around how the UI is supposed to clear fields that may 
be used in stateRules and strategyEdit?  For example, the sample OPLX strategy 
defines the following:

&lt;flow:StateRule value=&quot;0&quot;&gt;
  &lt;val:Edit field=&quot;Posting&quot; operator=&quot;EQ&quot; 
value=&quot;e_NOPOST&quot;/&gt;
&lt;/flow:StateRule&gt;

&lt;val:StrategyEdit errorMessage=&quot;DisplaySize does not match Posting 
selection&quot;&gt;
  &lt;val:Edit logicOperator=&quot;OR&quot;&gt;
        &lt;val:Edit logicOperator=&quot;AND&quot;&gt;
          &lt;val:Edit field=&quot;Posting&quot; operator=&quot;EQ&quot; 
value=&quot;e_SMART&quot;/&gt;
          &lt;val:Edit field=&quot;DisplaySize&quot; 
operator=&quot;NX&quot;/&gt;
        &lt;/val:Edit&gt;
        &lt;val:Edit logicOperator=&quot;AND&quot;&gt;
          &lt;val:Edit field=&quot;Posting&quot; operator=&quot;EQ&quot; 
value=&quot;e_NOPOST&quot;/&gt;
          &lt;val:Edit field=&quot;DisplaySize&quot; operator=&quot;EQ&quot; 
value=&quot;0&quot;/&gt;
        &lt;/val:Edit&gt;
        &lt;val:Edit logicOperator=&quot;AND&quot;&gt;
          &lt;val:Edit field=&quot;Posting&quot; operator=&quot;EQ&quot; 
value=&quot;e_Custom&quot;/&gt;
          &lt;val:Edit field=&quot;DisplaySize&quot; 
operator=&quot;EX&quot;/&gt;
        &lt;/val:Edit&gt;
  &lt;/val:Edit&gt;
&lt;/val:StrategyEdit&gt;

if the user selected e_NOPOST and then changed the value, the control with the 
stateRule will fail the validation since it didn't get reset to NULL.  In order 
to correctly handle this without writing special code, I had to add another 
stateRule (which looks hacky to me).

&lt;flow:StateRule value=&quot;&quot;&gt;
  &lt;val:Edit field=&quot;Posting&quot; operator=&quot;NE&quot; 
value=&quot;e_NOPOST&quot;/&gt;
&lt;/flow:StateRule&gt;


[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
-~----------~----~----~----~------~----~------~--~---

Reply via email to