Age | Commit message (Collapse) | Author |
|
|
|
Fixes the remote-tree not displaying the node's type like the local-tree does.
|
|
This was removed by @RyanStein in #21884 in the case where an error
message is provided, but this is actually useful information to have
even when there is a custom error message.
This PR makes it so that the "C++ Error" is shown whenever there is
a custom error message provided.
Also adds method name to the error item title, and re-adds the most
relevant info in the tooltip for quick error checks without expanding.
Renames C Error/Source to C++ Error/Source, since that's what it is.
And fix untranslatable entry due to misuse of TTR().
And some more cleanup for readability.
Cf. https://github.com/godotengine/godot/issues/32276#issuecomment-534119914
|
|
Improve the debugger shortcut UX
|
|
Fix Remote Tree Navigate to Inspected
|
|
- Display the shortcut in the button tooltips by defining the shortcut
on the buttons as well.
- Swap "Step Over" and "Step Into" in the Debug menu to match the button
order in the Debugger bottom panel.
|
|
This fades out messages originating from the editor to make messages
printed by the project stand out more.
This also tweaks wording in some editor messages for consistency.
|
|
Add informational messages to various editors
|
|
Fixes the regression of remote-tree not navigating to what is being inspected in the inspector.
|
|
sparkart/revert-30833-fix_inspector_clear_remote_node
Revert "Fix Clearing Inspector for Remote Node"
|
|
Add network profiler
|
|
|
|
|
|
|
|
|
|
Fix Clearing Inspector for Remote Node
|
|
|
|
Resolves: #30731
When you stop debugging... if you were inspecting a remote node, partial information about the remote node remained in the inspector (e.g. name and warning).
To resolve this, called EditorNode::edit_current() instead of EditorInspector::edit(NULL), which will call all the methods required using "NULL" if the current selected object is NULL.
In EditorPath::update_path() if the selected object is NULL, it does not update the path to reflect this change, basically does nothing. To fix this, we nullify everything, before the history loop.
|
|
|
|
|
|
Implemented remote scene tree filtering
|
|
Keep GDScript functions in stack while yielding
|
|
Remove always true/false values
|
|
|
|
Editor debugger now always handle connections.
|
|
The editor debugger used to only take the first client connection,
leaving potential new connections hanging until TCP timeout.
This caused a lock after some time when running multiple game/editor
instances, as the client will fill the write buffer, and then lock until
timeout (as the editor server would never read from that socket).
The editor now drops new connections immediately if it is already
connected to a client.
|
|
Unlike the old custom method, the `String::humanize_size()`
method works well with file sizes above 2 GB.
This also tweaks the suffixes for spacing consistency and
uses the correct acronym for exabytes (EB).
This closes #29610.
|
|
- Use dark colors when using a light theme for better visibility
- Enable antialiasing (only effective when using the GLES3 renderer)
- Make graph lines thinner but opaque
- Scale graph line widths on hiDPI displays
|
|
Fix remote scene tree root folding
|
|
User can now filter the remote scene tree, like the local one is filtered, while
the game is running
|
|
|
|
Also show script and line when the instance is gone when resuming from
yield.
|
|
Added a marker in text_edit that tells which row is executing.
|
|
|
|
|
|
Add CSV export to profiling data
|
|
|
|
This reverts commit fb37284c027b494ed3ec21124001fcb729f42cc4.
This reverts commit 4db0f51b9aa76cfc7649787fe1970af606ce8dab.
|
|
|
|
|
|
-Made relationship lines appear based on theme settings, not previous hack
-Fix drawing of relationship lines (was broken)
-Fix double initialization of theme settings
|
|
FIxed bug with Errors tab in the Debugger using wrong index in the
tab container.
Also removed unused variable that was probably left behind.
|
|
Fixes #25316.
|
|
Fixes #25487
|
|
Fixes #25198
|
|
Happy new year to the wonderful Godot community!
|
|
|
|
|
|
|
|
|