| Age | Commit message (Collapse) | Author |
|---|
|
|
|
The buttons are shown in the file browser context menu.
|
|
|
|
|
|
|
|
|
|
This always shows up right now. Hiding it correctly still has to be
done.
|
|
|
|
T68035 by @luzpaz
|
|
|
|
Clicking on the column header will sort the file list based on the
clicked column. Note that sorting by time only is not supported, sorting
by date already sorts by time and date.
|
|
Similar to what you know from other file browsers, at the table top
there's a row indicating column names and showing a little triangle to
mark which column is used for sorting. Later, this will become
interactive (to allow selecting sort method by clicking on a column
name).
I decided to hardcode drawing of this (like the rest of the file
browser) and just offset the file layout a bit. However that requires
some hacks for View2D and that the offset is respected in multiple
places. So now I think using a separate region instead makes more sense.
Leaving this as is now, code quality for file browser is pretty low
anyway.
|
|
|
|
Add common select options (toggle/invert etc).
|
|
Initial trigger to this work was T65782, requesting faster autoscroll
when current folder contains thousands of items. That was a fairly
simple change, just needed to make scrolling steps variable based on
'distance' between current position and desired one.
But several other issues showed up while working on this, among the most
annoying ones, the scrolltimer could keep running forever in some cases,
failing to detect properly an 'end condition', we could even get some
'bouncing' in extreme corner cases, edited item was not always properly
visible in the end, etc.
So as usual with UI, this ended up in a frustrating equilibrium game of
finding the optimal solution among several tradeof, taking unexpected
large amount of time... At least new code seems to work OK in
all possible (reasonable) cases, that will do for now.
|
|
We need to make those paths validation async, since some infamous OS is
unable to provide a quick way to check whether a path is valid or not...
Not much to say here, this is basic wmJob stuff really... We don’t even
need complex threaded coordination locks or atomics, given how simple
the changes are here.
Fake-tested with some `sleep()` calls to add atificial delay, seems to
work as expected.
|
|
|
|
|
|
|
|
Apply clang format as proposed in T53211.
For details on usage and instructions for migrating branches
without conflicts, see:
https://wiki.blender.org/wiki/Tools/ClangFormat
|
|
|
|
|
|
We really do not need two 256 chars variables to hanlde renaming, a mere
pair of flags can handle the situation just as well.
Also, scroll to newly renamed item, will help when one want to find
again the directory they just added and rename.
At some point we'll probably want to refactor scrolling further (to make
it fully out of rename code/context e.g.), but for now think this will do.
|
|
existing folders in display.
Smotthscroll to edited entry was broken since filelisting was
rewritten to become async...
|
|
While \file doesn't need an argument, it can't have another doxy
command after it.
|
|
Move \ingroup onto same line to be more compact and
make it clear the file is in the group.
|
|
Needed for clan-format not to wrap onto one line.
|
|
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.
|
|
|
|
Without this clang-format may wrap them onto a single line.
|
|
Prevents clang-format wrapping text before comments.
|
|
The highlight on mousemove operator should not swallow events.
|
|
|
|
Without this bugs slip through that don't null check the descriptions
since many were set to empty strings.
|
|
Makes it simpler to make some changes...
Also fix order of some includes (use alphabetical please).
|
|
That kind of implicit includes should really only be done when totally,
absolutely necessary, and ideally only with rather simple 'second-level'
headers.
Otherwise not being explicit with includes always end up biting in
unexpected ways...
|
|
See: T56648
|
|
|
|
Differential Revision: https://developer.blender.org/D3732
|
|
Also update menu items, adding select/de-select.
|
|
|
|
|
|
There's much more work to be done here, this is just fixing some obvious ones.
|
|
|
|
|
|
Strip unindented comment blocks - mainly headers to avoid conflicts.
|
|
Annoying for debug builds.
|
|
Fill-selection would only go upward in list of items to find an already
selected one and fill-select all items in-between. Now, in case upward
search fails, it will also intent to go downward, effectiviely allowing
to 'fill-select' from bottom to top.
Note that top-to-bottom keeps priority (i.e. if a top-to-bottom
fill-selection is possible, it will always happen, even if a
bottom-to-top one is also possible).
|
|
Practically all access to enum data is read-only.
|
|
Convention was only followed loosely,
apply to DNA where changes aren't likely to conflict.
(Skipped ModifierType for eg).
|
