| Age | Commit message (Collapse) | Author |
|---|
|
size.
|
|
|
|
|
|
Camera now supports all zoom styles too.
|
|
This is a temporary fix until I get to investigate it more carefully.
It will help if the report could include the steps to reproduce it
besides the buggy file.
Note: RenderResult should *always* have at least a valid RenderView,
which is not what happens here.
|
|
We used the node data as a store for node execution,
bad idea, since the data itself is a template from which
execution data should be derived, never to be modified during execution.
|
|
For the records, this one is caused by 31f984bc3ffcc838343, it wasn't
implemented at all ;)
|
|
Caused by own mistake in 31f984bc3ffcc83834, reported by @sebastian_k in
IRC
|
|
When zoomed out vert bias over edges meant it wasn't possible to select edges.
Now pick the edge if the cursor is closer to its center.
|
|
|
|
Note 1: If you go to a render slot previously rendered and change
something in the compositing the buffer will still vanish.
This is an old bug, T44181, and not addressed here
(I'm basically just fixing the regression introduced with multiview)
Note 2: I have a work in progress patch to get rid of
RenderResult->rectf/rect32/rectz entirely. It still not working, and we
should have a working code base before doing refactoring anyways.
|
|
Was using enum **value** as **icon id**... tripple sigh!
Guess it was working for its only current use (matcaps), but still.
|
|
|
|
|
|
Previousely this was "hidden" in the Properties Region, this makes it
more visible/usable.
Requested by @sebastian_k
|
|
|
|
This could cause memory corruption when moving files from system with one
bitness to another.
|
|
|
|
Python.
Many thanks to the problem report by flokkievids (Folkert de Vries)
through a comment in Patch D963.
|
|
panel)
Also hides index option in redo panel to be consistent with similar
operators
|
|
Change paths operator can also have the same placeholder logic now
|
|
Autodetect range of strips.
|
|
Placeholder images, means that the image sequence reserves a range for
images, displaying black while we wait for them to finish rendering.
This is meant as a feature to not break the layout of gooseberry
sequence edits while we wait for those frames to arrive.
|
|
View
|
|
Tooltips for buttons in the Outliner could overlap the Outliner's RMB
menu in some cases (and there's no way to get rid of the tooltip again).
This disables the button's tooltip before creating the menu (as we do it
for the normal RMB menu)
|
|
display more.
|
|
Was not using acquired render result correctly, most likely a copy paste
error.
|
|
Make sure stamp data is avaliable before writing stamp to image - this
still does not fix stamp, looks like issue is availability of the images
themselves for the view, investigating next.
|
|
|
|
|
|
|
|
Tweak hack of `file_draw_string()` (there may be better solution, but not worth
spending time on this, the whole filebrowser drawing code is to be rewritten anyway).
|
|
Glitch in rB57d9badc.
|
|
D1163 by @panzergame, with minor edits by me (@Severin)
|
|
|
|
|
|
removing point track
|
|
locked
Really doesn't look like a bug on a first glance but the line of code
that was there previously seemed to be there to prevent the manipulator
from drawing in this case.
|
|
use when the length of the destination string is needed.
|
|
|
|
No need to calculate height of each line, just use height of font.
|
|
|
|
Write those on render result during rendering, so we can cleanly write a
render result image after rendering.
|
|
* Theme support for metadata display
* Increase text DPI with scaling.
|
|
Basically, blender adds a few metadata fields to images when
we render an image. Those metadata can now be viewed in the
image editor.
Also, made sure metadata are available when we write imbufs
to disc with "Save As". There may be more cases here that need
fixing, but this means that loading an image with metadata
will now properly preserve them in blender.
|
|
Previously the GPencil strokes were just not drawn (even though they
were generated) until a strip was loaded.
|
|
only choose verts over edges (not faces)
|
|
|
|
Likely caused by rBd5f1b9c22233
|
|
Generalize logic for vert/edge/face selection:
- index cycling.
- selection bias with mixed modes.
Details:
- Edges now support index cycling (as verts/faces did already)
- Cycling over near elements is now only enabled when the mouse position remains the same.
- No longer do 2 selection passes to perform index cycling.
Fixes:
- Edges behind the view could be selected (surprising nobody reported!)
- Selection bias now only changes the element that gets picked without interning the return distance
(was buggy with mixed modes).
|
