[Bf-committers] Proposal to unify UI float ranges

Roger Wickes rogerwickes at yahoo.com
Sun Aug 22 17:05:01 CEST 2010

I would just like to say that it would be great from a user standpoint if the 
muscle-memory was consistent with what the user does in 3D space
when grabbing or rotating an object. 

just clicking on the thumb and dragging is free-form in reasonable (whole?) 

holding shift and clicking or dragging moves the slider in very small 
increments. For floats
this would be something like .001 but should be specified in the code

holding ctrl and click/drag controls the step size and it moves in steps. For 
like a resolution field, this would be like 16. 

Arrows apply the step size to the value (same as a ctrl-click in the area 
between the thumb and margin)

right-clicking on a control could bring up a list of commonly used values or 
saved pre-sets. 

For Y resolution, e.g, 240,360,480,720,800,1080

entering values and formulas is a most excellent feature. please preserve. I 
regularly enter
1./2.2 for gamma and 40./12. for like 40 inches when I use 1 BU=1 foot. 

There was an innovative proposal that someone floated about setting bounds. Like 
color slider, or hardness, there is the default, coder-recommended min and max, 
in some cases the user may wish to specify a value much larger. So each control
should have both a recommended min/max, but then also a theoretical min/max 
on the data type. So, if someone wants say a red value of 2.5, they can set 


Check out my website at www.rogerwickes.com for a good deal on my book and 
training course, as well as information about my latest activities. Use coupon
Papasmurf for $15 off!

----- Original Message ----
From: "migius at gmx.net" <migius at gmx.net>
To: bf-blender developers <bf-committers at blender.org>
Sent: Sun, August 22, 2010 6:41:15 AM
Subject: Re: [Bf-committers] Proposal to unify UI float ranges

> Von: Ton Roosendaal <ton at blender.org>
> I think we should show float numbers as float always, and certainly  
> not round of numbers, which is very confusing. A button can display  
> missing digits with some kind of indicator, like 2.5* or so.
> The increment/decrement should of course match the amount of displayed  
> digits.

1. the amount of displayed digits should be controlled by the user:
- globally: in user preferences;
- locally: with mouse-wheel over slider

2. i like the idea with indicator, use "~" for it:
2.3456345 = 2.34~ or 2.3456~ 


Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief!  
Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail
Bf-committers mailing list
Bf-committers at blender.org


More information about the Bf-committers mailing list