why on earth would nobody comment that? make a cylinder maybe 300 mm diameter, now fillet one edge if it was not yet set to something similar try something low like 2. having it set to range 10 (that additionally is pretty lame the entire thing is lame) now drag the interactive register to the right, it ends at 4 which is ? what? i had the feeling that when i kept pushing neurotically it extended at some point but not even this anymore., so i switch to range 100 (again that is an idiotic nuisance) now the range reaches up to 8, its still nowhere near anything useful for me, so totally unnerved i switch back to 10 now the range increases again but only till 16 that must be a bug come on, to get where i want i have to switch between 10 and 100 multiple times.. this or i forget about all this crap and double click the register to start entering numbers multiple times till i am satisfied, which nullifies the entire endeavour trying to visibly get into the ballpark fast and dynamically.
please good people of McNeel, open the mac version of Rhino sometimes and go through the regular used commands at least. this has been in there for years.
when the dialog opens, you can double click the number in the slider and enter a number, this changes the range to bracket that value. You can now slide around in that range to dial in your expected result. Is this not the case for you?
exactly, and having to rethink the dimensions defies the of logic offering sliders to make it visibly adjustable in a fast manner.
also the accuracy switch does not work properly at least not on a mac. i have not tried windows yet. having to toggle the magnitudes several times so that the slider extends to a workable range can not be intended.
if you switch from bigger shapes to smaller and vice versa the slider gets stuck in the range and you have to enter a ballpark number again to be within a workable range.
for instance, make a cylinder that is like 8000mm find your fillet that visually is alright. now make a cylinder that is maybe 30. the slider gets so hard stuck i cant even move it, the slider becomes useless without having to guess and enter a dimension in the slider again. maybe its a mac thing?
what definitely would help here is to let the command read out the dimension of each face in question perpendicular to the facing edge and preset the slider to a reasonable value within that range, any thoughts? then you just have to use the slider. i would honestly just keep the double click option or have the value aside that you can just click on the value once additonally and not confuse with double clicking the slider and vanish the range settings entirely.
This seems more like a theoretical example than a real life situation. In all the projects I’ve done, I’ve never been in a situation where I use those kind of range differences. In principle, when you run FilletSrf, you start by first by giving it a starting value. This starting value can however also be entered after the dialog is shown, by directly typing it in the commandline.
Your initial complaint, that the slider range is not set correctly should work better in the WIP.
which it doesnt, at least not in Rhino WIP, 9.0.25252.12306 this or i did not understand my own complaint.
anyway the entire command is currently not very user friendly. maybe you dont switch dimensions often but architects working on details and bigger stuff simultaneously might do.
well i played a bit and it seems a bit better than in v8 now, or i finally got the overly complex concept idk. but it feels pretty sluggish in some instance, specifically when the object is bigger i think. its not as fun and straight forward as it could be. without having all the dimensions of the object(s) in my head that am dealing with it is a roulette.
the major issue is that as here in the file below i have 2 cylinders, not apart by extreme amounts, fillet the bigger one with 120 for instance. after that fillet the smaller one set it to mayebe 5 the slider being stuck in a different dimension literally now became utterly useless with a radius stuck between the values seen here
i have to guess what fillet is acceptable for this sice by double clicking the slider to enter a number if i guess right otherwise i have to keep entering. it is just not very intuitive. I hear you that in your work that might never occur having to fillet parts that are a bit further apart in one session but that just does not apply to every one for sure.
i understand you put some effort into it and there is some annoying idiot like me that keeps complaining but i am not doing it to be a pain just for the sake of it.
Not a pain at all, I just want to make sure that we are designing stuff for actual use cases and not some theoretical ones.
What I often do is set the range to a thousand first. Once you find a radius that works lower the range if you want to be more precise. Maybe making the range sticky would be better than constantly defaulting it back to 10
