Changes between Initial Version and Version 1 of Ticket #10478, comment 4


Ignore:
Timestamp:
2014-09-04T19:03:38+02:00 (10 years ago)
Author:
malcolmh

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #10478, comment 4

    initial v1  
    1 The reason that I need chunks with only "list_entry" items is that I have many different keys that share a common set of values, so I want to define these once and reference them in combos and multiselects with different keys. The "chunk" facility appears on the face of it to be a generalised macro definition entity, so it should only be the expanded source that is checked for validity in the preset context, i.e. don't check the chunks themselves, but check that all the invocations of the chunks result in valid preset entities.
     1The reason that I need chunks with only "list_entry" items is that I have many different keys that share a common set of values, so I want to define these once and reference them in combos and multiselects with different keys. The "chunk" facility appears on the face of it to be a generalised macro definition entity, so it should only be the expanded source that is checked for validity in the preset context, i.e. don't check the chunks themselves, but check that all the invocations of the chunks result in valid preset structures.