> See 1e0df5 for more, especially why the demo will still not do the right > thing.
What do the hunks for src/views/view/utils.lisp do then, if they don't fix the problem (although it says "fix disappearing view fields")? Is this some precursor for the full fix, or maybe an only slightly related fix? > The reason the new test does as it does is that proper mixin data in > indirect mixins is deleted too early. I think this can be > straightforwardly solved with an enhancement to > map-expanding-mixin-fields, streaming its results directly to > factor-overridden-fields, and having the latter sort elements as they > arrive. It would even make GOVF a little faster and memory-lighter, > theoretically. I just thought of it 5min ago, so we'll see. Very good. This is one of the things that keeps us from releasing 0.8.3. Leslie --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "weblocks" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/weblocks?hl=en -~----------~----~----~----~------~----~------~--~---
