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
2013-09-07rename cursor setting functions to make modal set/restore more clearly ↵Campbell Barton
related functions.
2013-08-07code cleanup: some structs were declaring data when only typedef's were ↵Campbell Barton
intended, make local vars and functions static.
2013-07-31add NULL checks in eyedropper_color_sample_fl since ↵Campbell Barton
BKE_area_find_region_type may not find a region.
2013-07-25add api function BLI_path_append to add to a path (and ensure a seperator), ↵Campbell Barton
replaces BLI_join_dirfile when the dir and the destimation were the same.
2013-06-07add support for storing text styles in themes.Campbell Barton
also reset text styles when resetting to the default theme.
2013-05-21remove return value from MEM_freeN, it wasn't used anywhere and was cast to ↵Campbell Barton
a different function signature. (which evidently works but error prone).
2013-05-08rename BLI_ghashIterator_notDone() -> BLI_ghashIterator_done()Campbell Barton
was renamed fairly recently but other similar iterators not negated like this, would prefer to keep it as it was
2013-04-22Bugfix [#34836] Crash when driver variable has path == 'data'Joshua Leung
Most of the places which relied on RNA_path_resolve() did so believing that if it returned true, that it had found a valid property, and that the returned pointer+property combination would be what the path referred to. However, it turns out that if the property at the end of the path turns out to be a "pointer" property (e.g. "data" for Object.data), this would automatically become the pointer part, while the prop part would be set to null. Hence, if a user accidentally (or otherwise) specifies a path for the single-property driver variable type like this, then Blender would crash. This commit introduces two convenience functions - RNA_path_resolve_property() and RNA_path_resolve_property_full() - which mirror/wrap the existing RNA_path_resolve() functions. The only difference though is that these include a check to ensure that what was found from resolving the path was in fact a property (they only return true iff this is the case), and make it explicitly clear in the name that this is what they will do so that there's no further confusion. It is possible to do without these wrapper functions by doing these checks inline, but the few cases that had been patched already were pretty hideous looking specimens. Using these just make it clearer and simpler for all. I've also beefed up the docs on these a bit, and changed these to using bools.
2013-04-04code cleanup: use bools in UI and WM code, quiet some shadow warnings, ↵Campbell Barton
remove unused function uiEmboss()
2013-03-13code cleanup: use const events for modal and invoke operators.Campbell Barton
2013-03-07Change !BLI_ghashIterator_isDone to BLI_ghashIterator_notDone. It isAntony Riakiotakis
always used in that context so we can at least avoid reverting it twice :p.
2013-03-03move toggle drag into a UI handler (was modal operator)Campbell Barton
2013-03-01fix for drag-toggle, bit-buttons weren't handled which made drag toggle fail ↵Campbell Barton
for buttons in the graph editor for eg.
2013-02-26simplify drag toggle operator, use BLI_rctf_isect_segment between mouse ↵Campbell Barton
events rather then many calls to ui_but_find_mouse_over().
2013-02-25fix for toggle buttons not taking effect on mousedown.Campbell Barton
2013-02-22remove 'register' from drag-toggle operator (so it doesn't show in the redo ↵Campbell Barton
panel). update credits script.
2013-02-22change to drag-toggle don't exit when the mouse is outside the region - its ↵Campbell Barton
annoying for setting layers in the 3d header.
2013-02-22Toggle-Drag UI FeatureCampbell Barton
Dragging on toggle buttons can now be used to press multiple buttons at once, especially useful for layer and outliner buttons. notes: - automatically enabled for all toggle buttons (may change this if it becomes a problem). - only buttons of the same type are pressed (helps avoid annoyances eg; dragging past layer buttons onto other 3d header buttons and pressing by accident). - automatic axis locking - dragging will lock to X/Y depending on the initial drag direction, makes swipe motions work better, especially with the outliner. implementation details: - may re-implement as a region handler (currently its a modal operator). - checking buttons in-between cursor motion events could be more efficient (but currently works ok). - button execution needs to be improved (currently executing a button thats not under the mouse needed a workaround for passing uiHandleButtonData), requires further changes to UI code, will do next.
2013-02-05Fix #34040: Moving Normal Node with enabled Cycles Material Preview crashesSergey Sharybin
Issue was caused by couple of circumstances: - Normal Map node requires tesselated faces to compute tangent space - All temporary meshes needed for Cycles export were adding to G.main - Undo pushes would temporary set meshes tessfaces to NULL - Moving node will cause undo push and tree re-evaluate fr preview All this leads to threading conflict between preview render and undo system. Solved it in way that all temporary meshes are adding to that exact Main which was passed to Cycles via BlendData. This required couple of mechanic changes like adding extra parameter to *_add() functions and adding some *_ex() functions to make it possible RNA adds objects to Main passed to new() RNA function. This was tricky to pass Main to RNA function and IMO that's not so nice to pass main to function, so ended up with such decision: - Object.to_mesh() will add temp mesh to G.main - Added Main.meshes.new_from_object() which does the same as to_mesh, but adds temporary mesh to specified Main. So now all temporary meshes needed for preview render would be added to preview_main which does not conflict with undo pushes. Viewport render shall not be an issue because object sync happens from main thread in this case. It could be some issues with final render, but that's not so much likely to happen, so shall be fine. Thanks to Brecht for review!
2012-12-02change uiButGetStrInfo() to use a trailing NULL arg rather then passing the ↵Campbell Barton
number of args as an arg.
2012-10-26Big i18n commit: add "reports" from bmesh/readfile/tracking/dynapaint (and a ↵Bastien Montagne
few others), and another bunch of UI messages tweaks/fixes, as well as some BKE_report()<->BKE_reportf()...
2012-10-14More UI messages and BKE_reportf->BKE_report fixes...Bastien Montagne
2012-10-13More UI messages fixes.Bastien Montagne
Also forgot to translate reports' titles, and change some usages of BKE_reportf to simple BKE_report, when the former is not needed!
2012-10-12quiet some -Wshadow warningsCampbell Barton
2012-10-08code cleanup: reduce change the size of some float vectors that were bigger ↵Campbell Barton
then they needed to be. update to clang_array_check.py - parse function definitions lazily for some speedup.
2012-09-27Fix/enhancement of "locale to po file name" code. Now should handle nicely ↵Bastien Montagne
locales like "gez_ER@abegede", and never read uilng string beyond its end!
2012-09-15Color Management, Stage 2: Switch color pipeline to use OpenColorIOSergey Sharybin
Replace old color pipeline which was supporting linear/sRGB color spaces only with OpenColorIO-based pipeline. This introduces two configurable color spaces: - Input color space for images and movie clips. This space is used to convert images/movies from color space in which file is saved to Blender's linear space (for float images, byte images are not internally converted, only input space is stored for such images and used later). This setting could be found in image/clip data block settings. - Display color space which defines space in which particular display is working. This settings could be found in scene's Color Management panel. When render result is being displayed on the screen, apart from converting image to display space, some additional conversions could happen. This conversions are: - View, which defines tone curve applying before display transformation. These are different ways to view the image on the same display device. For example it could be used to emulate film view on sRGB display. - Exposure affects on image exposure before tone map is applied. - Gamma is post-display gamma correction, could be used to match particular display gamma. - RGB curves are user-defined curves which are applying before display transformation, could be used for different purposes. All this settings by default are only applying on render result and does not affect on other images. If some particular image needs to be affected by this transformation, "View as Render" setting of image data block should be set to truth. Movie clips are always affected by all display transformations. This commit also introduces configurable color space in which sequencer is working. This setting could be found in scene's Color Management panel and it should be used if such stuff as grading needs to be done in color space different from sRGB (i.e. when Film view on sRGB display is use, using VD16 space as sequencer's internal space would make grading working in space which is close to the space using for display). Some technical notes: - Image buffer's float buffer is now always in linear space, even if it was created from 16bit byte images. - Space of byte buffer is stored in image buffer's rect_colorspace property. - Profile of image buffer was removed since it's not longer meaningful. - OpenGL and GLSL is supposed to always work in sRGB space. It is possible to support other spaces, but it's quite large project which isn't so much important. - Legacy Color Management option disabled is emulated by using None display. It could have some regressions, but there's no clear way to avoid them. - If OpenColorIO is disabled on build time, it should make blender behaving in the same way as previous release with color management enabled. More details could be found at this page (more details would be added soon): http://wiki.blender.org/index.php/Dev:Ref/Release_Notes/2.64/Color_Management -- Thanks to Xavier Thomas, Lukas Toene for initial work on OpenColorIO integration and to Brecht van Lommel for some further development and code/ usecase review!
2012-09-15quiet -Wmissing-prototypes warnings, and enable this warning by default for ↵Campbell Barton
C with gcc. helps for finding unused functions and making functions static, also did some minor code cleanup.
2012-09-05fix for various redundant checks and possibly fix some crashes in rare ↵Campbell Barton
situations.
2012-08-23code cleanup: rename BLI_in_rctf() --> BLI_rctf_isect_pt(), to conform with ↵Campbell Barton
our naming convention.
2012-08-20HDR color picker now works in the clip space.Campbell Barton
2012-08-19style cleanupCampbell Barton
2012-08-18code cleanup: use BLI rect functions for interface button and block code.Campbell Barton
2012-08-18use rctf struct for UI buttons and blocks, easier to read and means we can ↵Campbell Barton
use BLI_rctf functions.
2012-08-16support fro HDR color picking (values over 1.0) when color picking in the ↵Campbell Barton
image editor or node space.
2012-07-09UI translation from inside Blender UI: first part.Bastien Montagne
This commit reshapes a bit runtime button info getter, by adding a new uiButGetStrInfo() which accepts a variable number of uiStringInfo parameters, and tries to fill them with the requested strings, for the given button (label, tip, context, RNA identifier, keymap, etc.). Currently used mostly by existing ui_tooltip_create(), and new UI_OT_edittranslation_init operator. It also adds a few getters (to get RNA i18n context, and current language iso code). Finally, it adds to C operators needed for the py ui_translation addon: *UI_OT_edittranslation_init, which gathers requested data and launch the py operator. *UI_OT_reloadtranslation, which forces a full reload of the whole UI translation (including rechecking the directory containing mo files). For the first operator to work, it also adds a new user preferences path: i18n_branches_directory, to point to the /branch part of a bf-translation checkout.
2012-06-15fix for own mistake - sampling was adjusting alpha when it shouldn't, also ↵Campbell Barton
make spacebar reset the accumulated color while eyedropping.
2012-06-15click dragging with the eye dropper now averages out colors - useful when ↵Campbell Barton
you have grainy footage of a green screen.
2012-05-19code cleanup: use TRUE/FALSE rather then 1/0 for better readability, also ↵Campbell Barton
replace do prefix with do_ for bool vars.
2012-05-16Code cleanup: simplify standard GHash creation.Nicholas Bishop
Added four new functions as shortcuts to creating GHashes that use the standard ptr/str/int/pair hash and compare functions. GHash *BLI_ghash_ptr_new(const char *info); GHash *BLI_ghash_str_new(const char *info); GHash *BLI_ghash_int_new(const char *info); GHash *BLI_ghash_pair_new(const char *info); Replaced almost all occurrences of BLI_ghash_new() with one of the above functions.
2012-05-09Fix #31371: copy data path should be disabled in places where it doesn't work,Brecht Van Lommel
like the user preferences. Also renamed "View Docs" menu entry to "Python Documentation".
2012-05-05code cleanup: BKE_ naming, also make bpy.data.images.load() always load a ↵Campbell Barton
new image. (not use existing one)
2012-04-19Fix #30998: copy to selected in properties editor not working for bones.Brecht Van Lommel
2012-04-10Fix properties editor, right click menu "Copy to Selected" not working forBrecht Van Lommel
object modifier/constraint/physics properties. Now uses RNA path rather than only properties on the object itself.
2012-03-31move debug flag into its own global var (G.debug), split up debug options.Campbell Barton
--debug --debug-ffmpeg --debug-python --debug-events --debug-wm This makes debug output easier to read - event debug prints would flood output too much before. For convenience: --debug-all turns all debug flags on (works as --debug did before). also removed some redundant whitespace in debug prints and prefix some prints with __func__ to give some context.
2012-03-30style cleanup: interfaceCampbell Barton
2012-03-24style cleanup: follow style guide for formatting of if/for/while loops, and ↵Campbell Barton
else if's
2012-03-22style cleanup: spaces aroudn operators for operator definitions.Campbell Barton
2012-03-18spelling cleanupCampbell Barton
2012-03-04style cleanup - comment spelling + translate some dutch.Campbell Barton