Thanks Campbell for pointing me, I'll check those functions to see what's there because I'm highly interested in this problem. While it really sounds great that blender can sum 1' with 30.48 cm, I think that that creates more problems (as this one with coma) that it's used buy ordinary users. For instance, I don't use either metric or imperial units, I use only blender units. Well, IMHO a whole unit system is a bit confusing and can lead to a lot of problems. For instance, I have attended to one Blender workshop where people had to collaborate and create models witch will be externally linked in one final Blend file. We should use metric system in cm, but a lot of people have used different scale so in the end we had all sorts of problems with model scaling in final scene. That wouldn't be the case if only BU was used.
On 17 April 2011 08:00, Campbell Barton <[email protected]> wrote: > recommend to look at interface.c and bpy_interface.c - > BPY_button_exec(), in principle what you suggest could work however > all parsing is done by python its not so simple to make decisions > based on input unless we write our own. > > In brief it works like this: > * user inputs some number/py-code/units > * for unit buttons blender does python compatible replacements (yes, > units systems cheats by relying on python :-) ). > * python evaluates this string - if its a tuple ist sum'd, otherwise a > number is expected. > > The conflict with units is input from multiple units system is > possible, so you can type in 10cm even if Imperial units are selected. > Or 10' when Metric is used. > > On Sat, Apr 16, 2011 at 10:24 PM, Damir Prebeg <[email protected]> > wrote: >> Well, I know that Python interprets 1, 2 as (1, 2) but as I can see >> numeric field actually calculates sum of numbers separated by coma >> witch Python doesn't do by it self. Since parser does that, wouldn't >> be possible to create parser that will distinguish simple 1, 2 from >> sum(1, 2) or from [1, 2]? >> And to be honest, I don't understand what's the problem with units. If >> someone uses imperial, metric or blender unit system, then he will use >> only one system at the time. Parser should be aware active unit system >> and should not mix 1'000,00 and 1,0. >> >> On 16 April 2011 16:12, Campbell Barton <[email protected]> wrote: >>> Also units, where: 2' 4" >>> ... is valid input for: 2 ft 4 inches >>> >>> Supporting 1'000,00 & units & python evaluation would be tricky and >>> error prone enough to make it not workable IMHO. >>> >>> On Sat, Apr 16, 2011 at 11:28 AM, Martin Poirier <[email protected]> wrote: >>>> The issue is that it doesn't accept just numbers, it accepts anything that >>>> evaluates to an expression, so you can type stuff lie: 1/3, 16/9*480, >>>> sum(15, 12.5, 48.6), ... >>>> >>>> Strictly parsing with a locale is not possible. >>>> >>>> Martin >>>> >>>> --- On Sat, 4/16/11, Remo Pini <[email protected]> wrote: >>>> >>>>> From: Remo Pini <[email protected]> >>>>> Subject: Re: [Bf-committers] Numeric fields should accept coma and >>>>> convert it todot >>>>> To: "bf-blender developers" <[email protected]> >>>>> Received: Saturday, April 16, 2011, 3:54 AM >>>>> I actually think that Blender should >>>>> try to adhere to whatever locale >>>>> settings the user has chosen if at all possible. This goes >>>>> for date, >>>>> time and number formats. >>>>> >>>>> I've seen numbers setup like 1000.00 / 1'000.00 / 1,000.00 >>>>> / 1'000,00 -> >>>>> simply accepting "." and "," will not solve this issues, >>>>> the "parser" >>>>> needs to be locale aware instead of just replacing >>>>> things... >>>>> >>>>> Cheers >>>>> >>>>> Remo >>>>> >>>>> > -----Original Message----- >>>>> > From: [email protected] >>>>> [mailto:bf-committers- >>>>> > [email protected]] >>>>> On Behalf Of Damir Prebeg >>>>> > Sent: Freitag, 15. April 2011 11:08 >>>>> > To: bf-blender developers >>>>> > Subject: [Bf-committers] Numeric fields should accept >>>>> coma and convert >>>>> it >>>>> > todot >>>>> > >>>>> > I use numeric keys a lot, but on my locale settings >>>>> num key DEL is >>>>> > coma not dot. Because of that I often make mistakes >>>>> with numeric >>>>> > inputs. I think that all numeric fields should accept >>>>> and convert coma >>>>> > to dot. >>>>> > _______________________________________________ >>>>> > Bf-committers mailing list >>>>> > [email protected] >>>>> > http://lists.blender.org/mailman/listinfo/bf-committers >>>>> _______________________________________________ >>>>> Bf-committers mailing list >>>>> [email protected] >>>>> http://lists.blender.org/mailman/listinfo/bf-committers >>>>> >>>> _______________________________________________ >>>> Bf-committers mailing list >>>> [email protected] >>>> http://lists.blender.org/mailman/listinfo/bf-committers >>>> >>> >>> >>> >>> -- >>> - Campbell >>> _______________________________________________ >>> Bf-committers mailing list >>> [email protected] >>> http://lists.blender.org/mailman/listinfo/bf-committers >>> >> _______________________________________________ >> Bf-committers mailing list >> [email protected] >> http://lists.blender.org/mailman/listinfo/bf-committers >> > > > > -- > - Campbell > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
