abstrax wrote:What we are going to do in the next release is to make the displacement height and shift fields slider-less, i.e. you either have to enter the values or use the RMB slider. This should avoid that you accidentally set a very high displacement height/shift.
Finally...!
I've posted about weird and seemingly illogical slider values before (don't think I got a reply) and the exponential acceleration of some sliders is often very difficult to control. I wish you guys would review this throughout the app. Is a value of 0.000-1 really sensible? Why don't we standardize all values either 1-100 or 1-1000 and lose those silly decimal values?
I'm probably missing something but a response / explanation to the current logic would be appreciated.
A related issue: clicking in a bar to adjust the value, adjusts the slider location if it's near the value field in the slider... Just frustrating. Fuzzy addressed this successfully in the SketchUp plugin by changing the cursor cue to indicate that the text is editable when close to the value field without affecting the slider and consequently the render settings.
Simple yet effective. Would you care to consider this for Standalone?
Best,
Seeker
Win 8(64) | P9X79-E WS | i7-3930K | 32GB | GTX Titan & GTX 780Ti | SketchUP | Revit | Beta tester for Revit & Sketchup plugins for Octane