It still seems to act funny. For instance, the parameters appear in the upper portion of the Tool panel. I had expected them in the lower portion of the tool shelf where scripts generally run. But thats Ok, I clicked Generate Ivy and it did make some ivy, but then the lower portion of the tool shelf changed it’s heading to Ivy Generator and the parameters in the upper portion of the tool shelf disappeared. So I ran the script again and got nothing. I checked the console and did not see any errors reported. But On Windows XP64 it looks like you can only run it once.
Thanks for porting this script, I do like it, I hope this feedback helps.
Feedback is the best possible thing in the beta stage so please keep it coming!
The parameters most likely disappeared because the cube is automatically deselected by the script, I think this should change in future. If you reselect the cube (or any mesh), the parameters for a new ivy object should reappear in the upper portion of the toolshelf. However, at this stage hitting generate ivy again will create a new ivy object rather than modifying the old one. This because the generation is slow.
Cheers and hope that clears a few things up,
Maybe we shouldn’t use a poll of the … but give only an error-message, if no suitable mesh is selected.
Or in the Panel is shown, which (suitable) object is selected or NONE this by sure would be helpful, wouldn’t it?
I think it has something to do with this from the Developers Meeting Notes, July 24, 2011:
Python math utilities: there’s a bug in the code that treats “matrix * vector” and “vector * matrix” the same. They mean something else mathematically though. Campbell added a warning in console for wrong usage. Final fix then will happen 13th of September.
The SVN of about sunday changed the matrix vector implementation and TrumanBlending used that already.
Two ‘remedies’ possible: get a rather fresh Blender (say of yesterday or ) or revert the matrix * vector into vector * matrix in the code
at the lines (there are at least 3 places, where I did it too, after learning about the change , comipiled the trunk and no error )
I’ve been playing with this quite a bit since yesterday! very cool so far!
I think it’d be great if it auto saved the settings out to a text file (default addons path) when run and when the user hits the “update ivy” button. so the next time you open it it could autoload the last used settings…(with a set to defaults button too!)
I think that’s be useful when you want to re-use the same settings from multiple different start points… you could “tab” into edit mode to snap the cursor to a new position, tab out and then just add a new ivy!
As for moving the cursor…Well, sort of… of I want to snap the cursor to a vertex I can’t without losing the panel because i have to go into edit mode to snap it… I can move the cursor, sure!
I just think that some level of persistence between sessions would be a good thing and is actually fairly trivial to add with your own custom text file format…
the preset system is also well known by now with plenty of examples to reference… although that usually relies on outputting py scripts that set properties when run(on selection from the ui list)… it could also be a way to give persistence… have a “last used” preset auto saved on pressing the “update ivy” button and auto load it when running a session… then you can just load the default preset if you want to start over.
At my version I do not loose the panel! Or are you still referring to Trumans version, THAT is not a panel, but operator related GUI, which is closed, if you go into edit-mode (my reason to use a Panel!)
Would you be so kind and show us your ‘save’ code, please?