[Plugin] TextureTools
-
So, as I suspected...
I'll reissue a trapped version that will take '.' or ',' as the decimal-separator in the inputbox for every tool, BUT it will if it's a string value it'll convert it to ',' to suit your locale and make a length from it if it has to... entering a number with a ',' it WILL work without failing [IF the locale supports] BUT it'll convert it back into a '.' when you OK the dialog...
Watch for an update... -
Ah yes, A period is as important to a programmer as it is to his girlfriend.
-
@tig said:
Massimo
I hadn't anticipated you weird Eurpoeans using a ',' as a decimal point rather than a sensible '.'
I can easily trap that in the code... I'll release an update later today - it should also have new tools added - TextureScale and TextureTweak......waiting for the fix.
-
Here's v1.5 http://forums.sketchucation.com/viewtopic.php?p=329765#p329765
Irrespective of their locale, users may now type a '.' OR a ',' as a decimal-separator, depending on their preference, for any of the tools' dialogs - issues with conversion of strings to lengths from potential locale-wrong input is addressed in the code, 'behind the scenes'.Feedback please...
-
@tig said:
Here's v1.5 http://forums.sketchucation.com/viewtopic.php?p=329765#p329765
Irrespective of their locale, users may now type a '.' OR a ',' as a decimal-separator, depending on their preference, for any of the tools' dialogs - issues with conversion of strings to lengths from potential locale-wrong input is addressed in the code behind the scenes.Feedback please...
Just tried it, win7 64 bit skp 8... works fine and I must say this is one of the best plugins ever made!!!
-
Hi TIG,
all functionality working very well on the Mac, except toolbar tooltips.
They work if I put the icons in the custom toolbar but not on the standard, floating toolbar.
not a big issue here, just thought I'd mention it.
john
-
-
@driven said:
Hi TIG,
all functionality working very well on the Mac, except toolbar tooltips.
john
The same, it works perfect on Mac.
-
-
TIG, i have tried this:
-painted a surface with a material;
-used one texture tool on the texture;
-picked the texture with the sample tool and painted other surfaces with different orientations.
Only with the "tweak" tool i get a strange behaviour following that workflow on connected faces. The texture looks a lot different on each plane... But if the planes are not connected it works just fine...
-
I think the built-in UV-mapping of connected-faces assumes a certain 'flow' of the material across their shared edges...
If you have separate faces then their textures are arranged logically on a per-surface basis.
Hence the different behavior of textures on separate and connected faces... -
Hmmm...That happens also with the "texture scale" tool if you input different values for U and V. But that doesn't happen if you use the native "edit" and input different values for length and width. (picture below)
-
Hmmm... this is v1... perhaps there's more to do...
-
No worries it's already a wonderful set of tools.
-
Thanks TIG! Most helpful plugin of the year!
-
Thank you so much for this, it is very helpful!
-
Looks like another must-have,
Hats off to TIG -
Hello sir,
Thank you very much .......
Its very useful .............
Good luck ........Thanks again .......
-
Dear ruby makers!
Please, If you put arrow keys (or any other ones) into the game make a temporary shortcut override!!!
There are some really usefull scripts with vulgar occupation of keys that make the life much harder.
Meanwhile only Thomthom implemented this feature. -
@rv1974 said:
Dear ruby makers!
Please, If you put arrow keys (or any other ones) into the game make a temporary shortcut override!!!
There are some really usefull scripts with vulgar occupation of keys that make the life much harder.
Meanwhile only Thomthom implemented this feature.
Sorry to say BUT I consider that you have it quite backwards!Scripts that use Arrow-keys for 'nudging' values are quite common - which suggests that you shouldn't assign them as your own shortcuts! It's not like we are reusing 'standard shortcut keys' here - we are just using logical key presses within an add-on tool.
Just as you wouldn't sanely assign a shortcut key to a number [0-9], as they is used in the VCB in most native tools, or even 'x' or '*' or '/' as that is used in Move+Ctrl copy array etc, or say swap M from Move to Delete ! ...
There are lots of keys, and modifier-key combinations for you to choose from when setting your custom shortcuts, without you having to use any of those that are needed by add-ons to be used logically...
It was only because Thomthom wanted to use the Move, Rotate etc shortcut keys in his Vertex Tool, that he mimics how they are set up in a default installation for the native tools - so you can use M to Move an entity in the native tools or Move a Vertex within his tool. However, the hoops he has had to jump through in code to get it to work are not acceptable to many scripters. Indeed, if you've ever had his tool crash, leaving these shortcut keys remapped, then you know how annoying even his fix is, because then many of your shortcuts are left permanently reset to the wrong tools, even when you are out of his tool, leaving a manual remap of shortcuts the only option to revert to a default setup... TT's tools are also now compiled as rbs files so the methods are not readily transparent to other scripters...
I wrote the original TextureRotate code from scratch in just two hours... as a 'proof of concept' - you'd have had to wait a lot longer for a 'massaged' version of the code to remap shortcuts etc... BUT if you want shortcut keys remapping temporarily then do it yourself - the code is open to your reuse! If you invent a simple, safe and foolproof temporary key remapping method then I suggest you publish it as then scripters might be more inclined to add the safety-net for those of you who persist in shortcutting to keys that are better left alone to tools that really need them
Advertisement