| Age | Commit message (Collapse) | Author |
|---|
|
This makes it possible to see whether a scrollbar grabber is at the top
or at the bottom of a scrollbar. Also, if a scrollable area is very
large, this makes it easier to notice that the area can be scrolled
(since the grabber is proportionally very small).
The scrollbar grabbers were also made thicker and slightly more opaque
for better visibility, especially in peripheral vision.
|
|
|
|
|
|
|
|
|
|
The blue accent color is now used, which matches the default editor
accent color.
It doesn't change to match the currently configured accent color
automatically, but doing so would require modifying the CheckButton
class a lot for little benefit.
|
|
Add a minimap to the GraphEdit
|
|
gongpha/fix-texture3d-texturearray-icon-rasterizing
Improve Texture3D and TextureArray icons
|
|
Advantages:
- When searching for "progressbar", you'll see both nodes in the
search results.
- More consistent with Button/TextureButton.
|
|
|
|
|
|
|
|
|
|
use Text Server interface.
Implement interface mirroring.
Add TextLine and TextParagraph classes.
Handle UTF-16 input on macOS and Windows.
|
|
Co-authored-by: Ugis Brekis <ugis.brekis@productmadness.com>
|
|
Make Path3D handles visible and consistent with 2D.
|
|
Resolves godotengine/godot-proposals#1246.
It is difficult to tell the difference between the handles for adjusting
curves and the points themselves when looking at a Path gizmo.
This re-uses the icons used for Path2D.
Unlike Path2D, this does not use a different icon for smooth vs sharp
points, as using a potentially different material for each point would
prevent batching the points in add_handles (and adding them out-of-order
messes up other logic based on handle indices).
This includes a public API change to allow specifying a texture for a
handle material. This allows spatial gizmo plugins to customize the way
a handle is rendered, if desired, but does not break existing behavior
(as providing no texture uses the default).
The path handle icons were resized as well. 16x16 is the standard icon
size. These icons were 10x10 rather than 16x16, and appeared rather
small in the editor.
To resize, I:
- Opened the original in Inkscape
- Resized the document to 16x16
- Opened the transform dialog
- Scaled by 160% proportionally
- Used Align/Distribute to center on the page
- Saved the document
- Cleaned with `svgcleaner --multipass`
|
|
Add icons for the 'CanvasGroup' and 'CodeEdit' nodes
|
|
|
|
|
|
This decreases the editor binary size by about 8 KB.
|
|
Minor improvements to the Polygon 2D UV editor
|
|
ref: #42972
|
|
|
|
The default color was blue which is the active color, changed it to be gray by default.
|
|
See discussion in
https://github.com/godotengine/godot-proposals/issues/169.
|
|
See https://github.com/godotengine/godot/issues/16863#issuecomment-685236980.
|
|
|
|
A new `env.Run` method is added which allows to control the verbosity
of builders output automatically depending on whether the "verbose"
option is set. It also allows to optionally run any SCons commands in a
subprocess using the existing `run_in_subprocess` method, unifying
the interface. `Action` objects wrap all builder functions to include a
short build message associated with any action.
Notably, this removes quite verbose output generated by `make_doc_header`
and `make_editor_icons_action` builders.
|
|
|
|
There were a lot of SVG files changed by file_format.sh
|
|
their width/height equal
|
|
|
|
Left-over from 31b7f02a29cdf4f1c30cfc37962f43f67380b9ad.
|
|
This closes https://github.com/godotengine/godot-proposals/issues/818.
|
|
- Remove the crosshair as it no longer serves a purpose (the cursor will
now appear where the user "expects" it to).
This closes https://github.com/godotengine/godot-proposals/issues/1076.
|
|
This patch adds ability to include external, user-defined C++ modules
to be compiled as part of Godot via `custom_modules` build option
which can be passed to `scons`.
```
scons platform=x11 tools=yes custom_modules="../project/modules"
```
Features:
- detects all available modules under `custom_modules` directory the
same way as it does for built-in modules (not recursive);
- works with both relative and absolute paths on the filesystem;
- multiple search paths can be specified as a comma-separated list.
Module custom documentation and editor icons collection and generation
process is adapted to work with absolute paths needed by such modules.
Also fixed doctool bug mixing absolute and relative paths respectively.
Implementation details:
- `env.module_list` is a dictionary now, which holds both module name as
key and either a relative or absolute path to a module as a value.
- `methods.detect_modules` is run twice: once for built-in modules, and
second for external modules, all combined later.
- `methods.detect_modules` was not doing what it says on the tin. It is
split into `detect_modules` which collects a list of available modules
and `write_modules` which generates `register_types` sources for each.
- whether a module is built-in or external is distinguished by relative
or absolute paths respectively. `custom_modules` scons converter
ensures that the path is absolute even if relative path is supplied,
including expanding user paths and symbolic links.
- treats the parent directory as if it was Godot's base directory, so
that there's no need to change include paths in cases where custom
modules are included as dependencies in other modules.
|
|
|
|
|
|
This closes #38684.
|
|
This makes it possible to see if both errors and warnings were
pushed without having to open the tab.
|
|
|
|
|
|
Updade dialog node's icons
|
|
Fix: #37716
|
|
|
|
|
|
doc: Update classref with node renames
|
|
A few extra renames for classes which were missed in last week's PRs.
|
|
Configured for a max line length of 120 characters.
psf/black is very opinionated and purposely doesn't leave much room for
configuration. The output is mostly OK so that should be fine for us,
but some things worth noting:
- Manually wrapped strings will be reflowed, so by using a line length
of 120 for the sake of preserving readability for our long command
calls, it also means that some manually wrapped strings are back on
the same line and should be manually merged again.
- Code generators using string concatenation extensively look awful,
since black puts each operand on a single line. We need to refactor
these generators to use more pythonic string formatting, for which
many options are available (`%`, `format` or f-strings).
- CI checks and a pre-commit hook will be added to ensure that future
buildsystem changes are well-formatted.
|