#515 re-think model.global's membership and use in <line>

AMBER
open
Lou Burnard
None
5(default)
2015-05-28
2014-07-02
Syd Bauman
No

Council Chair requested this ticket in response to our discussion of 485.

Related

Feature Requests: #485

Discussion

  • James Cummings
    James Cummings
    2014-11-18

    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -Council Chair requested this ticket in response to our discussion of 485.
    +Council Chair requested this ticket in response to our discussion of [#485].
    
     
  • James Cummings
    James Cummings
    2014-11-18

    • status: open --> closed-wont-fix
     
  • James Cummings
    James Cummings
    2014-11-18

    Council decides that it is too complicated to fix this.

     
  • James Cummings
    James Cummings
    2014-11-18

    • status: closed-wont-fix --> open
     
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -Council Chair requested this ticket in response to our discussion of [#485].
    +Council Chair requested this ticket in response to our discussion of 485.
    
    • assigned_to: Lou Burnard
     
  • Lou Burnard
    Lou Burnard
    2015-05-28

    It's true that model.global elements can appear in <line>, but only because they are (ahem) global. That's no argument for adding further inappropriate components however. My recommendation would be to review the current members of the model.global class. Or do nothing.