New user feedback
Posted: Wed Dec 17, 2003 10:12 am
Hi,
I thought I would get these items in while I still have that newbie perspective - something you lose quickly and can never have again!
Here are some issues I've encountered that would have made my learning process faster and easier...
- Set the enabled attribute of tasks and devices ON by default when they are created. I must be a slow learner, but I can't tell you how many times I've waited for a task to do something only to discover that it did not happen because of a missing enabled setting somewhere.
- Clarify the meaning of task conditions. Currently, it is unclear that task conditions trigger on changes of state rather than on an ongoing basis because the language implies state, not change of state.
As an example, the condition "If 'System Time.Sunrise Indicator' is equal '0' " implies that the conditions would be met all night long, when in fact it is met only at sundown.
I suggest the addition of an action word like "becomes" to the condition...
"If 'System Time.Sunrise Indicator' becomes equal to '0'". This clarifies the condition greatly (to me, at least).
(I know putting these items in the bug report section is a bit of stretch, but the other sections were more of a stretch )
Claude.
I thought I would get these items in while I still have that newbie perspective - something you lose quickly and can never have again!
Here are some issues I've encountered that would have made my learning process faster and easier...
- Set the enabled attribute of tasks and devices ON by default when they are created. I must be a slow learner, but I can't tell you how many times I've waited for a task to do something only to discover that it did not happen because of a missing enabled setting somewhere.
- Clarify the meaning of task conditions. Currently, it is unclear that task conditions trigger on changes of state rather than on an ongoing basis because the language implies state, not change of state.
As an example, the condition "If 'System Time.Sunrise Indicator' is equal '0' " implies that the conditions would be met all night long, when in fact it is met only at sundown.
I suggest the addition of an action word like "becomes" to the condition...
"If 'System Time.Sunrise Indicator' becomes equal to '0'". This clarifies the condition greatly (to me, at least).
(I know putting these items in the bug report section is a bit of stretch, but the other sections were more of a stretch )
Claude.