Next: Sample Code
Up: MIC3
Previous: Data Types
  Contents
This section documents known bugs for which there are no plans to fix
for the 3.0 release. They should be fixed for the final release,
3.01.
- It is glaringly difficult to use many features of the error
reporting parts of MIC without a good understanding of the internals
of the error packaging objects, esp. with regards to dynamic
fields. This needs further evaluation and design.
- Although nested groups are usable, there is state loss in
that if there is a parent group is pageable and children groups are
pageable, then when the parent is paged, the children will believe
their index is that of the the index of the children on the previous
instantiation of the parent. That is, if on page one of the parent
group, we page to page two of the child group, then when we page to
page two of the parent, we will be on page two of the child, even if we
have never specifically paged that instantiation.
- It is believed that the maxnum attribute of the MICgroup tag has
no effect.
- The error marking routines break abstractions and need to be
implemented in their own tag, or MICinput needs better design.
Next: Sample Code
Up: MIC3
Previous: Data Types
  Contents