[Plugin][$] FredoScale - v3.6a - 01 Apr 24
-
Hi!
I have a little problem with this plugin. If the stretching device provided by the component or group, then the attribute does not change the size.Sorry, this turned out to google.
-
I think I understand what you wrote, local, but it isn't entirely clear.
It is true that if you stretch a component or group, you only change the appearance of that entity but it doesn't change the definition not does it change any other instances of the component in the model. This happens with the native Scale tool as well. To change the definition (attributes) you need to open the component or group for editing and modify the geometry inside.
-
Could it be that he's referring to Dynamic Components?
-
This component consists of several group.
-
I am not sure of the question but the stretching tool alters the component itself,unlike the scale tool.
If more than one instance of the component is in drawing, stretching creates a new component definition--so the original component is unchanged.
-
Hello all,
This is my first post, but I have spent countless hours reading this forum and it has been the the most amazing SU resource. Im just learning, and I would have a fraction of my current knowledge/ability without this forum, not to mention the developers who make scripts for SU (thank you Fredo!!!) Im amazed how much effort and energy the individuals in this community are willing to give. Truly amazing!
I now have my first question, or at least a question I could not answer simply by reading. I tried to search for the answer, I did not find it, but im sure its simple.
Using Fredo scale box scaling, when I grab/drag a handle and scale it jumps from 1.0 to 1.05, and I can not get it to scale in this range (1.0-1.05) without typing the values. It would be very nice to stop this, and have it scale in this range without it jumping from 1.0 to 1.05.
Is there a way to change this?
thanks...
-
Hm. I tried both with the native Scale tool and FredoScale and I can easily move my mouse in a way that it smoothly "grows" the numbers by 0.01 increments.
-
@gaieus said:
Hm. I tried both with the native Scale tool and FredoScale and I can easily move my mouse in a way that it smoothly "grows" the numbers by 0.01 increments.
When I use the native scale tool it scales by .01 increments. But, when using Fredo Scale it jumps to 1.05, and then scales up from there at .01 increments. Very frustrating. There is a similar issue when using target mode with small (not minute, but small) distances.When using scaling handles I can type in the values between 1 and 1.05, but with target mode there is no way to get the scaling through the small distance.
If anyone has any ideas please tell me what you think. There didn't seem to be anything in the settings to correct this.
-
Can you share the model file (or at least the problematic part) you are working with?
-
I see it too on a simple box. When the scale handle first moves it is either to 1.05 or 0.95. That's really no a big deal, though. If you want a precise scale factor, just type the desired value including 1.01 or whatever you really want.
-
@gaieus said:
Can you share the model file (or at least the problematic part) you are working with?
I could upload a file, but Im not sure it would help. This is the behavior all the time. There is not particular file or problem area. It behaves like that all the time.
Should I upload a file? Will that help?
Again, its only with the Fredo Scale, not the native scale.
Let me know if you think it will help ill post one, but it appears to be the script, not a particular file/operation.
Thanks for the help guys
-
@dave r said:
I see it too on a simple box. When the scale handle first moves it is either to 1.05 or 0.95. That's really no a big deal, though. If you want a precise scale factor, just type the desired value including 1.01 or whatever you really want.
Exactly, yes that's what mine does. Very frustrating.
yes, I can type it in, but this is not as useful as there is no real-time feedback/deformation. If its possible to change it I would love to know how.
Also, possibly more urgent is that fact that in target mode this 'jump' prevents the operation from occurring at all. Neither draging the handle, or typing in parameters produces a result when scaling in this small range.
Perhaps its a script issue?
-
There is a parameter for fixing the minimum amount of scaling when dragging. Unfortunately, I did not make available for setting in the Default Parameters...dialog box.
I think I will in a next release.
In the meantime, you can modify the line 180 of file bootstrap_FredoScale.rb, which is:
LIMIT_InferenceScale = 0.05
Just change the value, for instance 0.01.Fredo
-
@unknownuser said:
There is a parameter for fixing the minimum amount of scaling when dragging. Unfortunately, I did not make available for setting in the Default Parameters...dialog box.
I think I will in a next release.
In the meantime, you can modify the line 180 of file bootstrap_FredoScale.rb, which is:
LIMIT_InferenceScale = 0.05
Just change the value, for instance 0.01.Fredo
Ahhhhh, thank you so much Fredo! And thanks for all the wonderful toys!
One question, I tried to edit the .rb in a text editor but I was "denied permission". Can anyone tell me how should I go about editing the bootstrap_FredoScale.rb???
Thanks for the help.
-
You should be able to edit it in your text editor. What program did you try to use to open?
-
@dave r said:
You should be able to edit it in your text editor. What program did you try to use to open?
Got it!
It was a security issue. I did not have full read/write access for the file. Just had to give myself permission, which i graciously did.
-
The attched skp files shows a very simple case using FredoScale 2.2a in the free rotate line inference mode. The plugin seems to declar an intersect point by changing the line color but when one double clicks on the line it shows no division until the base of the triangle is conneted with the line tool. Then intersect happens. All snapping has been deactivated for this case.Using Fredo6 4.5 lib.
free roate artifact or issue.skp
Is this normal ?? -
@mac1 said:
The attched skp files shows a very simple case using FredoScale 2.2a in the free rotate line inference mode. The plugin seems to declar an intersect point by changing the line color but when one double clicks on the line it shows no division until the base of the triangle is conneted with the line tool. Then intersect happens. All snapping has been deactivated for this case.Using Fredo6 4.5 lib.
[attachment=0:1s75sq9r]<!-- ia0 -->free roate artifact or issue.skp<!-- ia0 -->[/attachment:1s75sq9r]
Is this normal ??You are right. The extremity is well positioned, but the target segment is not divided.
Actually Fredoscale does nothing else than perform the rotation to the right angle and let Sketchup do the rest as with the native Rotate tool).
Should FredoScale force the Divide?Fredo
-
One of the first checks I do is double click the line and if does not divide I conclude some thing is wrong. However, this functionality is not high use ,at least for me, and knowing the artifact I cannot say it is a make play to make a program chage just for that. Maybe some high use users will comment. Otherwise I would suggest to make it a planned change( with other chages) if it isn't a big program impact.
The cases I run into, although few, are 3d and so I use the sphere line intersect spread sheet I have.
Your tool which is great and that cover all I need .
-
I've seen a different looking toolbar in Richs Tutorial, do someone know a source for these icons?
Advertisement