Opened 12 years ago
Closed 12 years ago
#443 closed enhancement (fixed)
Check user plug-in interface, whether 'lock' is necessary
| Reported by: | kilian | Owned by: | kilian |
|---|---|---|---|
| Priority: | P1 | Milestone: | v2.0.7 |
| Component: | core | Version: | 2.0.5 |
| Severity: | minor | Keywords: | |
| Cc: |
Description
This is just a reminder that I would like to look into this, before the UI is fixed in the next release. No big deal.
Change History (4)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
| Milestone: | v2.0.6 → v2.0.7 |
|---|---|
| Priority: | P4 → P2 |
| Status: | new → assigned |
Agreed.
comment:4 Changed 12 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Summary:
- I decided to keep the 'lock' feature. The importance is minor, but it allows for a more transparent handling of helicity in beam/structure function chains.
- I modified the code such that locks are applied exclusively to the helicity quantum number.
- The documentation should make this clear now.
Note: See
TracTickets for help on using
tickets.
Ok, I do not know what that means but if it is not solved by tomorrow we postpone it hard-heartedly to 2.0.7.