In conditional statements, order is illogical
birdmanx35 - February 3, 2008 - 01:29
| Project: | Flexifilter |
| Version: | 6.x-1.1-rc1 |
| Component: | User interface - Admin pages |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Currently, under any conditional statement (I haven't tested that, but I would assume so), the order for their parts is this:
-If
-Condition (such as Text length)
-Change Condition
-Components
-Add components
I think the Change Condition one should be moved to the bottom. The order looks bad currently (the change condition piece is smaller than the others), and I would assume that people are certain about what kind of condition they want, so the components in the condition should go before the option to change it. I would also assume that they would add a component before changing the condition.
#1
The previous title seemed as if it was a bug, it's not. It's just a usability problem.
#2
I'd assume dmitrig01's patch will change this; I'll wait and see...
#3
Can you check that, cwgordon7?
#4
Correct me if I am wrong, but the components are executed when the condition is true; it would be like to have a "then () if ()".