Robynsveil
Admirable
One of the loneliest endeavours one can embark on is that of self-taught add-on development. As a real Python developer can quickly determine from a cursory glance at my so-called "code", "self-taught" screams from every function.
But, it works.
So, my purposes have been satisfied, which were based on an insufferable laziness: I found painting shaders on figures imported from Poser to Blender a process needlessly tedious and repetitive. Even when copying and pasting entire shaders from mat zone to mat zone became a matter of Ctrl-C | Ctrl-V, doing that a few times became annoying, so a script seemed a good solution.
The original script worked, but it was very short on features.
Long-story-short, I've been adding features. "Oh, what a complex web we weave, when first we practice... to write apps." I know, not how it goes, but it's applicable.
Currently, the app looks like:
You select the figure to 'shader', select the figure type (original figure name) and click [Apply Shaders]. Works okay, *IF* all the .csv files were edited correctly and all conditions were met and so forth and so on. Errors sort-of happened in the background (console) which most users would never look at, and so the programme probably never seemed to "work right"... dunno, because I never got either complaints or comments or anything, really.
So, I started to trap errors, and most recently was able to get them to display in an error dialogue of sorts, in the foreground with an OK button:
Well, the OK doesn't close the dialogue, something I sort-of need to nut out why, and other stuff, but at least the error isn't hidden out of sight. I currently trap for 7 or 8 possible errors... but do warn folks to have a look in console if the software seems to be hanging somewhere.
In the meantime, here's where I'm hoping to be going soon...
But, it works.
So, my purposes have been satisfied, which were based on an insufferable laziness: I found painting shaders on figures imported from Poser to Blender a process needlessly tedious and repetitive. Even when copying and pasting entire shaders from mat zone to mat zone became a matter of Ctrl-C | Ctrl-V, doing that a few times became annoying, so a script seemed a good solution.
The original script worked, but it was very short on features.
Long-story-short, I've been adding features. "Oh, what a complex web we weave, when first we practice... to write apps." I know, not how it goes, but it's applicable.
Currently, the app looks like:
![](/proxy.php?image=http%3A%2F%2Fwww.tightbytes.com%2FBlender%2FFigShTute00.png&hash=f6f9657f7a1841c399d7a225b82f36fa)
You select the figure to 'shader', select the figure type (original figure name) and click [Apply Shaders]. Works okay, *IF* all the .csv files were edited correctly and all conditions were met and so forth and so on. Errors sort-of happened in the background (console) which most users would never look at, and so the programme probably never seemed to "work right"... dunno, because I never got either complaints or comments or anything, really.
So, I started to trap errors, and most recently was able to get them to display in an error dialogue of sorts, in the foreground with an OK button:
![](/proxy.php?image=http%3A%2F%2Fwww.tightbytes.com%2FBlender%2FFigShTute03a.png&hash=b3f6a7d40ba7798106a588da23ccaeb3)
Well, the OK doesn't close the dialogue, something I sort-of need to nut out why, and other stuff, but at least the error isn't hidden out of sight. I currently trap for 7 or 8 possible errors... but do warn folks to have a look in console if the software seems to be hanging somewhere.
In the meantime, here's where I'm hoping to be going soon...