Re: Working on some tools for Blender and Pipmak

[rivenwanderer <riv...@ya...>]

> - Is there a reason for having the panorama rendering and camera 
> location saving in two separate steps? I'd have expected it to save the 
> camExport file already in the rendering step.

There isn't a good reason, it just made more sense during development :p 
Next version will combine them.

> - It would be nice to have a file browser for the "path" field instead 
> of having to type it.

Hm, I'll see if Blender's API has an easy way to do that.

> - For nodes that lie at different heights, the elevation of the handles 
> is inverted: the handle that goes up on my tower is down on the floor 
> instead of covering the top of the tower.

Oops! ^_^;; I'll fix that in the next version.  Must be a sign error or
something.

> - Node names that are not numbers must be put in quotes in the 
> "target=xyz" line. Otherwise Lua sees them as variables, which have 
> value nil when undefined, and nothing happens when you click on the 
> handle (not even an error message). (For Pipmak >= r209, even numbers 
> could be put in quotes, but that wouldn't work for 0.2.7.)

The script has a "use_pipmak_2_7" variable which I'm already using to
determine whether to use az/el or caz/cel--I can use the same variable to
switch off of quoting all node names or not, and allow the variable to be
set via commandline args (defaulting to assuming it's the standard 0.2.7
version if it's not specified).  I think that 0.2.7 and "the latest version
from SVN" are the only two versions of Pipmak I'm going to care about, so I
won't worry about versions between 0.2.7 and r209.

Thanks for testing!
-- 
View this message in context: http://www.nabble.com/Working-on-some-tools-for-Blender-and-Pipmak-tp20317074p20409183.html
Sent from the pipmak-users mailing list archive at Nabble.com.