Re: [Pipmak-Users] Patch rotation proposal

[Andrea V. <and...@gm...>]

Hello Christian, 

I think the use of anchorx,anchory was a good ideas, 
I was thinking at a same thing.

I'm a little confused about set anchorx=anchory=0.5 to make a patch
to coincide with a cube face, can you explain better?

When you speak about putting anchorx,anchory at (x,y),
I understand that you refer to the relative coordinates of the image,
is it correct? 

If I use the notation (nx,ny,nz), I could set an anchor that doesn't 
lie on the same plane on which the patch image lie.
What's happen in this case?
Do You think to get (x,y) with a orthogonal projection on lying plane?

About patches that extend beyond their face, I was speaking about 
the actual behaviour, I known that the arbitrary patches placement
will resolve all this situation, it was just a curiosity, 
overall about the random clipping.

About the performance, the behaviour is strange, because I have notice 
that also with a traditional pipmak project (like MyHouse Tour), 
sometime on my notebook the rotation along the azimuth is jerk, sometime no.

Another strange things: if I put the pipmak window in the background, 
pipmak eat over 80% of cpu time and when I put in the foreground,
the cpu amount rise to 5%, if I leave pipmak in the background for a lot
of time without do nothing, I have to kill because take 100% of cpu time.
Do you think this behaviour depend by my graphic card? 
(Nvidia quadro4 500 GoGL a particular model don't cover by Nvidia normal
drivers - so my drivers are update to year 2002 and doesn't exist more
updated drivers)

Bye 

Andrea