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
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
2012-03-06style cleanup, brackets in else/if, some indentation.Campbell Barton
2012-03-04style cleanup / comment formatting for bli/bke/bmeshCampbell Barton
2012-02-23style cleanup for blenkernel, no functional changes.Campbell Barton
2011-12-22split some >120 lines, no functional changesCampbell Barton
2011-12-07Fix #28663: All "unit" properties show a value of 0 (on WinXP&MinGW&scons)Sergey Sharybin
Use %g instead of %lg due to %g is supposed to be used for doubles and %lg confuses mingw at all
2011-11-05use (const char*) rather than (char*) where possible.Campbell Barton
also removed some unused function definitons.
2011-10-23remove $Id: tags after discussion on the mailign list: ↵Campbell Barton
http://markmail.org/message/fp7ozcywxum3ar7n
2011-09-16Fix #28663: All "unit" properties show a value of 0 (on WinXP&MinGW&scons)Sergey Sharybin
Initially problem was caused by updated version of mingw-runtime which changed behavior of snprintf and vsnprintf so %lf isn't anymore valid for doubles. According to manpages, %f is a correct format for snprintf for doubles.
2011-08-30Fixes for snprintf usage:Brecht Van Lommel
* replace by BLI_snprintf in various places, note _snprintf on windows does not properly null terminate the string. * fix overflow in sequencer proxy code due to buffer being smaller than specified size. * fix some usage of snprintf as strcpy, this is will go wrong if the string contains % characters. * remove BLI_dynstr_printf function in gpu module, use BLI_dynstr_appendf
2011-08-11fix [#28213] Imperial unit for 0.001 inches inconsistently displayed as mils ↵Campbell Barton
and thous
2011-04-19patch [#26978] Minor Spelling Mistakes in Editor OperatorsCampbell Barton
+ some errors I noticed.
2011-03-29use less verbose string formatting for units and interface.Campbell Barton
2011-02-27doxygen: blender/blenkernel tagged.Nathan Letwory
2011-02-23Clean up headers a bit more.Guillermo S. Romero
2011-02-23doxygen: prevent GPL license block from being parsed as doxygen comment.Nathan Letwory
2011-02-13fix for warnings from Sparse static source code checker, mostly BKE/BLI and ↵Campbell Barton
python functions. - use NULL rather then 0 where possible (makes code & function calls more readable IMHO). - set static variables and functions (exposed some unused vars/funcs). - use func(void) rather then func() for definitions.
2010-12-10bugfix [#25154] .MXF files should be included as a known video file type in ↵Campbell Barton
the sequencer [#25159] Vertex locations dont read correctly and are not labeled correctly in the properties bar. - non rna buttons can now have units set. - calls with invalid units system now raises an assert(). - include .mxf in filter.
2010-11-23use unit system for the grid floor (was only ortho before).Campbell Barton
2010-11-23Changes to the ortho grid drawing based on discussion with Ton.Campbell Barton
- ortho grid now draws scaled by the view3d 'Scale' setting, venomgfx noticed this was missing. - so as not to confuse add scale next to unit display text, so rather then "Metres" it shows "Metres x 1.5" otherwise its confusing that grid lines are not in exact units. - changed grid spacing to grid scale (needed for more logical behavior with units) - when units are enabled grey out subdivisions.