[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gzz] Lava, coordsyscache
From: |
Tuomas Lukka |
Subject: |
Re: [Gzz] Lava, coordsyscache |
Date: |
Tue, 29 Jul 2003 10:11:31 +0300 |
User-agent: |
Mutt/1.5.4i |
On Tue, Jul 29, 2003 at 10:05:04AM +0300, Matti Katila wrote:
> On Mon, 28 Jul 2003, Tuomas Lukka wrote:
> > I just noticed an alarming thing:
>
> ...
>
> > I still don't even understand the need for CoordsysCache, could you please
> > explain it once again, mudyc?
>
> Viewports a and b show the same canvas.
> Let's say in a we have node a1 focused and in b we have node b1 focused.
> If you like to move node a1, you need to know it's coordsys number.
All right so far
> Who has it? No one.
No, the VobMatcher does! You can find out from it by asking with the
parent and key.
> So what we have when we would like to do fast
> animation, other than the old vobscene?
Yes, this is given: fast animation is through reusing the old vobscene.
> If the viewport a is main node we
> know a lot of it so we can use this information. As Tuomas recommended,
> I used parent's matching key as a key to save coordsystems in the class
> which is under eyes now.
Umm, *why*? It sounds as if this is duplicating functionality that's
already in VobMatcher. If not, it *should* be there, right?
> By that key the coordsys number can be found from
> others which was the thing to reach for.
?
Tuomas