My app is slightly different and uses a patch panel style of interface rather than linear blocks. Every time the system is changed, the layout is parsed into code and any invalid paths are coloured red to show
a) where the problem originates
b) which blocks are affected by the problem
Additionally there is a crude type system that prevents the wrong type of signal being passed to a block - e.g. a buy/sell datatype cannot be passed into a block which expects numerical time series data. I would say that you should prevent users from entering rules which make no sense as far as is possible..
I guess it depends how technical your users are. I'm attempting to stay away from terms such as nil or boolean, so I would go for something like your first example, but with more information, perhaps like:
"I don't know how to follow the rule "if moving_avg > buy" because xyz" which sounds friendly and non-technical but hopefully xyz will help them understand why it doesn't work and learn from their mistake.
a) where the problem originates b) which blocks are affected by the problem
Additionally there is a crude type system that prevents the wrong type of signal being passed to a block - e.g. a buy/sell datatype cannot be passed into a block which expects numerical time series data. I would say that you should prevent users from entering rules which make no sense as far as is possible..
I guess it depends how technical your users are. I'm attempting to stay away from terms such as nil or boolean, so I would go for something like your first example, but with more information, perhaps like:
"I don't know how to follow the rule "if moving_avg > buy" because xyz" which sounds friendly and non-technical but hopefully xyz will help them understand why it doesn't work and learn from their mistake.