[Bf-committers] Proposal to unify UI float ranges

Ton Roosendaal ton at blender.org
Sun Aug 22 17:55:48 CEST 2010


Hi,

I mean to use an indicator like * for when widgets have no space, to  
indicate truncation as well.

-Ton-

------------------------------------------------------------------------
Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The Netherlands

On 22 Aug, 2010, at 17:46, Christopher Fredericks wrote:

>  I like the indicator idea and would like to add my 2 cents.
> To show that the content of the control is overflowed, fade the last
> digit(s) to transparent. (Seen on Android OS for program labels that
> overflow, off the top of my head)
> To view the entire value, mouse over the area and the entire string of
> digits is painted "on top" the way a tooltip is.
>
> Quick mockup:
>
> http://imgur.com/GvNt6.png
>
> First shows the initial state.
> Next, the entry of too precise a float to be seen in 3 decimal places.
> Next, proposed transparent overflow state.
> Finally, what happens on mouse hover of the element. The entire float
> can be seen.
>
> It's easy to see at a glance that a value is not complete, and doesn't
> clutter the UI with some other indicator like *
>
> Christopher
>
> On 8/22/2010 6:45 AM, Thomas Dinges wrote:
>>   Hi,
>> ok that is good!
>>
>> Ok where we agree is that the increment/decrement issue needs fixing!
>> But how should we fix that? We have lots of such buttons.
>> Like Environment Lighting Energy: Show the third decimal there or  
>> let it
>> change the second decimal?
>>
>> Forget about the rounding, that can indeed cause some confusion.
>> For the hiding of zeros topic:
>> It would "flicker" quite a bit when the value change it's decimal
>> amount. :) So lets forget that as well.
>> A Indicator like Ton propsed it would be good!
>>
>> Thomas
>>
>> Am 22.08.2010 12:26, schrieb Ton Roosendaal:
>>> Hi,
>>>
>>> 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.
>>>
>>> -Ton-
>>>
>>> ------------------------------------------------------------------------
>>> Ton Roosendaal  Blender Foundation   ton at blender.org    www.blender.org
>>> Blender Institute   Entrepotdok 57A  1018AD Amsterdam   The  
>>> Netherlands
>>>
>>> On 22 Aug, 2010, at 12:20, Thomas Dinges wrote:
>>>
>>>>   Rounding would be only for values with more than 3 decimals.
>>>> Less/Equal 3 will show correct.
>>>>
>>>> And this is only 1 option, we could skip the rounding fot the "more
>>>> than
>>>> 3 decimal" scenario.
>>>>
>>>> Thomas
>>>>
>>>> Am 22.08.2010 12:17, schrieb Daniel Salazar - 3Developer.com:
>>>>> All good points but I was never too sure about rounding  
>>>>> decimals! its
>>>>> quite misleading actually, you get into situations where you  
>>>>> typed a
>>>>> number like 1.55 and if it rounds to 1.6 you are not sure if you
>>>>> typed
>>>>> it right..
>>>>>
>>>>> Daniel Salazar
>>>>> www.3developer.com
>>>>>
>>>>>
>>>>>
>>>>> On Sun, Aug 22, 2010 at 4:14 AM, Thomas Dinges<dingto at gmx.de>     
>>>>> wrote:
>>>>>>       Hi everybody,
>>>>>> we have quite some inconsistency in the UI regarding Button  
>>>>>> ranges
>>>>>> at
>>>>>> the moment.
>>>>>> We have Floats where 1 decimal is shown, 2 or 3.
>>>>>>
>>>>>> And we have a lot of buttons where you click on one of the small
>>>>>> triangle icons (right or left) and you can't see a difference,
>>>>>> because
>>>>>> the third decimal is changed but UI only shows 2.
>>>>>> That is bad and the user could think it's not working, cause his
>>>>>> click
>>>>>> doesn’t show any effect.
>>>>>>
>>>>>> My proposal is:
>>>>>> Let's unify the view of the ranges like this:
>>>>>> Value is 1, UI shows 1
>>>>>> Value is 1.5, UI shows 1.5
>>>>>> Value is 1.55, UI shows 1.55
>>>>>> Value is 1.555, UI shows 1.555
>>>>>>
>>>>>> More than 3 decimals
>>>>>> Value is 1.5556, UI shows 1.556
>>>>>> or
>>>>>> Value is 1.5556, UI shows 1.555
>>>>>>
>>>>>> This way, we would save some space, as we don’t have to see 3
>>>>>> decimal
>>>>>> digits when the value only needs 1 decimal to show correct. etc.
>>>>>>
>>>>>> Second thing:
>>>>>> By clicking the Triangle Icons some properties increase/decrease
>>>>>> by an
>>>>>> amount of 1, 0.1, 0.2 etc. This is very inconsistent too.
>>>>>> For floats I would suggest to unify that as well, and increase  
>>>>>> the
>>>>>> first
>>>>>> decimal only. So 1.0 gets 1.1, 1.56 gets 1.66 and so on...
>>>>>> Any other values can be done via manual input.
>>>>>>
>>>>>> What do you think?
>>>>>>
>>>>>> Best regards,
>>>>>> Thomas
>>>>>> _______________________________________________
>>>>>> Bf-committers mailing list
>>>>>> Bf-committers at blender.org
>>>>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>>>>>
>>>>> _______________________________________________
>>>>> Bf-committers mailing list
>>>>> Bf-committers at blender.org
>>>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>>> _______________________________________________
>>>> Bf-committers mailing list
>>>> Bf-committers at blender.org
>>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>>>
>>> _______________________________________________
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
>>> http://lists.blender.org/mailman/listinfo/bf-committers
>>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>



More information about the Bf-committers mailing list