The only way to make an effective change to the display rule is to go into the component options, click to edit the display rules, and modify it there.
Is this a big deal? No. But it's annoying, especially when there are no cues to tell us that it isn't working other than simple trial and observation of error.
As long as the user isn't expected to make a change in this interface, visual cues such as greyed out text fields and no "OK" button should be presented to the user.
Edit: I have to take part of this back. Apparently other parameters of the display rule can be changed and saved, but the value that it's looking for remains unchanged.
Hi Derek,
Am I understanding your workflow correctly? You double-click on a Display Rule from the tree within the Active Template
You change the value. In my example below I change it from 5 to 3. Click OK.
Then you're saying that this change is not applied? I accessed the Display Rule also through the Component Properties just to make sure. See below that the value is set to 3.
Please provide me with more detail of what you're describing, so that I can better understand the problem.
Thanks,
Holly
For more information about the Road and Site design tools, visit the Road and Site design WIKI at: http://communities.bentley.com/products/road___site_design/w/road_and_site_design__wiki
I figured out why you're seeing what you're seeing and why I'm seeing what I'm seeing.
When I change the value and I press Enter while the cursor is within that same field, the test value isn't accepted.
When I change the value and I press Enter when the text insertion cursor is in any other field, the test value is accepted.
When I change the value and without moving the cursor from that field, and I click the OK button, the test value is accepted.
Apparently this applies only to the value on the condition. For any other field I've tested, when I press Enter after changing anything else, the new selection is accepted.
Can this be considered a bug to be fixed in the future? Surely I'm not the only one in the world that would ever experience this behavior. If my hand is already on the keyboard because I'm entering in a value, it simply makes sense that I might want to use the keyboard to also hit Enter. And while I could hit Tab before hitting Enter, maybe my hand is on the right side of the keyboard, nowhere near Tab. Also, there's the whole user expectation thing.
Answer Verified By: Derek Schmidt
Good catch. I created defect 768144 for development to review. In the meantime, the workaround is to click the OK button to accept changes instead of hitting Enter.
Still a bug, and its 2021...and it was transferred into OpenRoads.