| Age | Commit message (Collapse) | Author |
|---|
|
Select clipping now works when x-ray is disabled.
|
|
Following removal from C source code.
See: 8c68ed6df16d8893
|
|
Needed for clan-format not to wrap onto one line.
|
|
Was confusing eg: G_AUTOPACK belonged to G.fileflags, G_PICKSEL to G.f.
|
|
BF-admins agree to remove header information that isn't useful,
to reduce noise.
- BEGIN/END license blocks
Developers should add non license comments as separate comment blocks.
No need for separator text.
- Contributors
This is often invalid, outdated or misleading
especially when splitting files.
It's more useful to git-blame to find out who has developed the code.
See P901 for script to perform these edits.
|
|
Done using:
source/tools/utils_maintenance/c_sort_blocks.py
|
|
|
|
|
|
|
|
Object mode locking wasn't accounting for the 3D view context
which doesn't have an active object once its hidden.
|
|
|
|
|
|
|
|
Only for workbench solid/wire modes.
|
|
Disabled for now because of draw-order issues.
Also move clipping test out of view3d_draw_legacy.c
|
|
|
|
Prevents clang-format merging into a single line.
|
|
|
|
Deprecated GL_SELECT no longer works in OpenGL core profile, so there is no
reason to have this.
|
|
Without this clang-format may wrap them onto a single line.
|
|
Prevents clang-format wrapping text before comments.
|
|
For clang-format not to wrap definitions.
|
|
The original issue is that we were changing the camera shiftx
temporarily for the stereoscopic calculation. However we are using the
evaluated object when calculating the projection matrix.
Note: Camera framing drawing for stereo still seems to be broken.
But the viewport itself is now correct.
|
|
In a better way...
6dbfd7f6d6bc would make the final vertex weights always calculated in
edit mode. Now it's only if the option is enabled.
|
|
Debugging the edit mode selection I realized the vertices are often
occluded by edges with the same depth. Sometime it can be the center
pixel of a vertex point and that can lead to some selection issue.
So I increased the offset a bit for the vertices and it seems to fix it.
|
|
This makes it more future proof and remove baked id offset inside the vbos.
Instead we add the offset as a uniform. This makes it possible to reuse
the vbos instead of discarding them all the time.
Also using batch request may reduce batches creation time.
|
|
TH_BACK was being used when drawing the 3D view even though
there was no way to set the color in the preferences.
The color was zero'd when moving to the new 2.8x theme.
Having both gradient and background colors was confusing,
especially having to use 'TH_HIGH_GRAD' for the 3D view, 'TH_BACK' for
other views.
Move the background color back to 'TH_BACK', 'TH_BACK_GRAD' is used
when gradients are enabled.
RNA is unchanged so presets don't need updating.
|
|
Fixes T60251.
|
|
Working in 2.7x, was just disabled in 2.8x.
Fixes T60256
|
|
|
|
|
|
|
|
Needed for clang formatting to workaround bug/limit, see: T53211
|
|
Use for object dimensions.
|
|
|
|
|
|
- Use non-rna button for adjusting dimensions.
- Make Object.dimensions RNA read-only since it never worked well.
This is mainly a UI editing feature.
|
|
Vertex paint overlays the color w/ solid mode,
Having a partial overlay makes the sample tool not give useful results.
|
|
|
|
|
|
|
|
Caused by rBc7a96651dfa4 when trying to remove all uses of the deprecated `rv3d->gridview`.
|
|
* 2D Animation: lots of changes from the grease pencil team. Properties
editor layouts, brush and material settings, and more.
* 3D Viewport: wireframes set to 1.0.
* World: use nodes by default.
* Node Editor: use narrow toolbar.
|
|
|
|
In blender 2.8, when you zoom in, the adaptive subdivisions appear earlier than previous versions.
The grid still appears a little before the snap, but since it is very small I see no advantage in snap for this case.
|
|
Gizmo was scaling w/ object.
|
|
|
|
This was originally caused by fix for T53788. Not sure why extra
`where_is` is needed there, the object is supposed to be evaluated
already.
|
|
This commit makes it so curve path parent solving accepts an explicit
arguments for both time and curve speed flag, making it so we don't
have to mock around with scene's frame.
One unfortunate issue still is that if the instancing object is used
for something else, we might be running into a threading conflict.
Possible solution would be to create a temp copy of an object, but
then it will be an issue of preventing drivers from modifying other
datablocks.
At least the original issue is fixed now, and things behave same as
in older Blender version. Additionally, the global variable which
was defining curve speed flag behavior is gone now!
|
|
Err on the side of too much padding.
|
