Hi (Jan, Vaclav),
If I understand correctly (looking at scripts), Cell::trsf is currently
used to define the initial geometry of the period (e.g. applying
rotations). Is that correct? I didn't expect this usage when I
introduced it, as it was supposed to record cumulated transformations.
The annoy
Hi Bruno,
Cell.trsf defines the current (not initial) transformation of the cell
with regards to the reference configuration, which is always
axis-aligned box with size Cell.refSize. (Footnote: although I did not
check bzr log, I am quite sure it was me who introduced Cell.trsf.)
Cell.trsf is
Hi Vaclav, thanks for reply.
I actually finished the implementation in the meantime.
> Cell.trsf defines the current (not initial) transformation of the cell
> with regards to the reference configuration, which is always
> axis-aligned box with size Cell.refSize. (Footnote: although I did not
> ch
Hi Bruno,
I think it makes sense what you write and it is good that you did the
implementaiton that works. The fact that flipCell can be encapsulated
inside the collider is nice, for instance. I would like to just ask for
2 things:
1. Make sure that the old interface (setting refSize etc) wo
Hi,
It's commited. Attributes doc should be ok but header doc and sphinx doc
are TODOs.
All scripts I could find seems to run unmodified.
I replaced definition of trsf and refSize by setters in the scripts
(couldn't find a better way since integrateAndUpdate can't really do the
job now). Setters a
Ah, last thing : generateCloud don't find any problem to fill
non-aligned boxes (in the cases I tested at least), but I still don't
know why... Maybe it's generating in axis aligned box then wrapping? I
didn't take time to verify. It can't affect older scripts anyway.
B.
On 19/01/11 19:28, Bruno
6 matches
Mail list logo
