Welcome to mirror list, hosted at ThFree Co, Russian Federation.

git.blender.org/blender.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2017-08-01Fix multi-units drawing re precision handling.Bastien Montagne
This is still far from prefect, but yet much better than what we had so far (more consistent with inheritent precision available in floats). Note that this fixes some (currently commented out) units unittests, and requires adjusting some others, will be done in next commit.
2017-07-31Fix two issues with recent changes to number display while editing them.Bastien Montagne
* Numbers with units (especially, angles) where not handled correctly regarding number of significant digits (spotted by @brecht in T52222 comment, thanks). * Zero value has no valid log, need to take that into account!
2016-05-03Cleanup: use const for units APICampbell Barton
Also make return args explicit.
2016-03-09Cleanup: style, spellingCampbell Barton
2016-03-02Correction to own previous rB9c0de0084bfe.Bastien Montagne
'1mm+1m' would fail with original fix, now consuming all alpha chars before checking unit again...
2016-03-02Fix T47661: cm (centimeter) unit breaks m (meter) unit in Metric.Bastien Montagne
`m` unit when used after `cm`/`mm`/etc. ones would get ignored, and the alt version of miles would be used instead. The root of the issue is that, in `unit_find_str`, once we get a 'hit' for a unit, we check it's actual unit (since 'm' would also hit on 'cm', 'mm', etc.). In case that hit is not a valid unit one, we would just return NULL, breaking the cycle of checks over that unit, and hence missing all later usages of it. So now, in case we have an 'invalid unit hit', we immediately retry to find it within remaining string.
2015-11-19Cleanup: redundant 'break', minor editsCampbell Barton
2015-10-05Fix T46379: Bad behavior of bUnit_ToUnitAltName() with default units.Bastien Montagne
It would simply remove default units (in most case), cannot see any good reason for such behavior? Might work in case default unit is the only one present, but breaks consistency (and it may not be always obvious for user which unit it is). Comes from original patch from five years ago, rB7d8f0fce. This will break keyboard-setting of values, e.g. '2m 33.4cm' would become '2 33.4cm', totally useless and invalid entry!
2015-07-16Fix T45459: Edge Length with Separate Units Displayed As 1m 100cm.Bastien Montagne
Our 'unit epsilon' was too small, given the fact we only display up to four digits usually...
2015-07-14Cleanup: use ascii as suffix (as with utf8)Campbell Barton
2015-04-21BLI_string: add BLI_snprintf_rlenCampbell Barton
use when the length of the destination string is needed.
2014-08-26Move bUnit_getScaleUnit -> BKE_scene_unit_scaleCampbell Barton
unit.c intentionally doesn't include DNA or BKE headers (except its own)
2014-08-26Fix T41590: When scene scale is not 1.0, and units are "None," Blender ↵Bastien Montagne
assumes translations are in meters. Turned out there were several issues in handling of scale parameter by numinput. Fixed that by factorizing more some code in common with 'usual' numbuttons eval code (new `bUnit_getScaleUnit()` helper will return valid scaled value, depending on given system and type). Now, numinput behaves as expected - using default unit amended by scale in case no unit is given (i.e. entering '20' with a scale of 0.01 will give you 20cm, and '20cm' as well!).
2014-08-20BKE_units: Some cleanup (mostly bools instead of ints).Bastien Montagne
2014-08-20Fix T38722: Adding units in Imperial setting results in inconsistent valuesBastien Montagne
Now always check for a default unit, and evaluate the whole expression in this "unit space". Not an ideal solution, but should handle most cases nicely (we can't address all possible corner cases anyway). Note default unit is searched in current string first (bigger unit of current system wins), then in previous string. Note this also replaces ',' by '+' in default separation between units, helps solving issues with parenthesis (e.g. (1'1")*2.5 would fail in existing code)! This would break if someone uses py ops with lower precedence than '+' (like bitwise operations, and comparison), but these are not expected usecase here anyway. Reviewers: campbellbarton Differential Revision: https://developer.blender.org/D340
2014-07-12Code Cleanup: use constCampbell Barton
2014-06-17Fix some loss of precision in BKE's unit code.Bastien Montagne
When converting text to value, units' "value" had only 6 digits of precision, leading to annoying loss of precision esp. when mixing big and small units (like e.g. miles and inches).
2014-04-26Code cleanup: use 'const' for arrays (blenkernel)Campbell Barton
2014-04-01Code cleanup: remove TRUE/FALSE & WITH_BOOL_COMPAT defineCampbell Barton
2014-02-05Code cleanup: use bool for static methodsCampbell Barton
2014-02-03Code cleanup: use bools where possibleCampbell Barton
2014-01-04UI: Use bool rather then int/short's where possibleCampbell Barton
2014-01-04Units: Add milligrams for massSergej Reich
Avoids having small values displayed as "0kg".
2014-01-04Revert "Units: Make grams base unit for mass"Sergej Reich
This reverts commit ead6d397fda12d8287dff7d6a6fff6ea1948cd69.
2013-12-31Units: Make grams base unit for massSergej Reich
2013-12-21Support units in modal numinputBastien Montagne
Summary: This completly changes the way modal numinput is handled. Now, edited expression is a string, which then gets unit- and py-evaluated to get a float value. We gain many power and flexibility, but lose a few "shortcuts" like '-' to negate, or '/' to inverse (if they are really needed, we still can add them with modifiers, like e.g. ctrl-/ or so). Features: - units (cm, ", deg, etc.). - basic operations from python/BKE_unit (+, *, **, etc.), and math constants and functions (pi, sin, etc.). - you can navigate in edited value (left/right key, ctrl to move by block) and insert/delete chars, e.g. to fix a typo without having to rewrite everything. - you can go to next/previous value with (ctrl-)TAB key. - As before, hitting backspace after having deleted all leading chars will first reset the edited value to init state, and on second press, the whole "modal numinput" editing will be cancelled, going back to usual transform with mouse. Notes: - Did not touch to how values are shown in header when modal numinput is not enabled (would do that in another commit), so this is still quite inconsistent. - Added back radian support in BKE_unit. - Added arcminute/arcsecond to BKE_unit. (those unit changes affect all angle UI controls, btw, so you can now enter radians or longitude/latitude values when in degrees units). Related to T37600. Reviewers: brecht, campbellbarton, carter2422 Reviewed By: brecht, campbellbarton, carter2422 Thanks everybody! Differential Revision: http://developer.blender.org/D61
2013-12-11User Interface: Align number buttons labels to the left, number rightCampbell Barton
2013-11-25Code Cleanup: rename vars for detecting change to be more consistentCampbell Barton
rename change/is_change/is_changed/modified -> changed also use bools over int/short/char and once accidental float.
2013-11-16More fix for this stupid uppercase-to-lowercase convertion code... Thanks to ↵Bastien Montagne
Lockal for noting this!
2013-11-10Fix [#37393] Input dimensions are case sensitive in the property panel, ↵Bastien Montagne
uppercase input is misinterpreted Typo in lowercasing code!
2013-11-08[#37327] Inconsistent numeric input conversion.Bastien Montagne
Issue was actually that micrometer was not drawing correctly (from r58165), reverted that fix and instead use utf8 drawing for editmode metrics when using a unit system (we already had a similar hack for surfaces and volumes, anyway).
2013-07-11fix [#36090] Blender displays strange symbol in edge lengthCampbell Barton
2013-05-31units: display 0.5mm rather then 500um, nicer when dealing with very small ↵Campbell Barton
sizes but not microscopic.
2013-04-08Fix #34875: 0 digits of precision was not supported for FloatProperty, nowBrecht Van Lommel
you can specify precision=0 for this, and use -1 for the default 2.
2013-03-14use BLI_strncpy_rlen() rather then BLI_snprintf() when no formatting is needed.Campbell Barton
also replace sprintf with strcpy when no formatting is done.
2013-03-13Fix #34481: camera focal length and sensor size did not use units yet, now ↵Brecht Van Lommel
they do. I've added a separate camera unit type. It's a bit strange to have an exception for this but it ensures units are shown in familiar millimeters and it also ensures backwards compatibility.
2013-02-11Suppress more uncommon units.Sergej Reich
2013-02-11supress Hectograms from being used when displaying weight units since they ↵Campbell Barton
are not so common.
2012-11-01style cleanupCampbell Barton
2012-09-27incorrect spelling in commentsCampbell Barton
2012-08-12style cleanupCampbell Barton
2012-07-04spelling cleanup: metre -> erCampbell Barton
2012-06-27style cleanupCampbell Barton
2012-05-24style cleanup: comma placementCampbell Barton
2012-04-29style cleanup: whitespace / commasCampbell Barton
2012-04-20aparently `yards` are not used a lot, suppress their use in button display ↵Campbell Barton
(input still knows about them) - was reported as a bug. also fix minor rip bug where active selection was lost.
2012-04-15code cleanup: dont include BLI_winstuff.h on non windows systems, also ↵Campbell Barton
cleanup some defines/includes for windows.
2012-04-10fix for unit system incorrectly replacint 'um' (unicode 'u'). with meters.Campbell Barton
result was editing number buttons with um would give a python error.
2012-03-10style cleanup: unit codeCampbell Barton
2012-03-09style cleanup: spelling.Campbell Barton
also remove large, duplicate comments from sunsky.h