#2966 closed defect (fixed)
setComponentModifierValue can't set a two level modifier
Reported by: | Adeel Asghar | Owned by: | Adrian Pop |
---|---|---|---|
Priority: | high | Milestone: | 1.9.4 |
Component: | Interactive Environment | Version: | trunk |
Keywords: | Cc: |
Description (last modified by )
Creating a two level modifier produces a wrong code,
setComponentModifierValue(B,a.r.start, $Code(=5))
However, if the component already have the two level modifier then the API works fine.
Check the attached script file.
Attachments (1)
Change History (5)
by , 10 years ago
Attachment: | Bug2966.mos added |
---|
comment:1 by , 10 years ago
Description: | modified (diff) |
---|
comment:2 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:3 by , 9 years ago
Milestone: | Future → pre1.9.4 |
---|
It doesn't make sense to keep closed ticket in the "Future" milestone that were simply forgotten to assign to the correct milestone in the past.
comment:4 by , 7 years ago
Milestone: | pre1.9.4 → 1.9.4 |
---|
Removing the pre1.9.4 milestone in favor of 1.9.4.
Note:
See TracTickets
for help on using tickets.
Fixed in r23475.