Bugzilla – Full Text Bug Listing
| Summary: | ComposerField: Empty Condition-Field when editing "OR"-expression | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Christoph Thommen <christoph.thommen> | ||||||||
| Component: | Scout | Assignee: | Project Inbox <scout.core-inbox> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | ivan.motsch, zimmermann | ||||||||
| Version: | unspecified | Flags: | zimmermann:
indigo+
zimmermann: juno+ |
||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | Windows Vista | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 196869 [details]
Condition dialog
Created attachment 197589 [details]
patch to solve this issue
The problem was the EditMenu which checks whether the parent node of the selected AttributeNode is an EntityNode or not. If it's not - and it isn't if the AttributeNode is a child of an EitherOrNode - the EditMenu gets the available attributes from the ComposerField instead of the EntityNode, which leads to no or wrong attributes listed in the edit dialog.
The attached patch fixes this issue.
Patch applied, fixes the issue, thanks a lot! shipped with scout 3.7.1 removed iplog flag from ticket and added iplog flag to attachment |
Created attachment 196868 [details] ComposerField When editing an or expression on a composer field, the first "condition field" is empty (see printscreen).