Cut off the end of a sentence that doesn't make sense:
"You can also start profiling at any time before or during gameplay, depending on if you want."
It seems like removing the "depending on if you want." improves clarity of the documentation.
This allows users to leave comments on pages that don't have
`:allow_comments: False` somewhere in the page's source.
Both manual and class reference pages can receive comments.
Index pages cannot have comments, as discussion should occur on "leaf" pages.
GitHub Discussions is used as a backend on the same repository. This means
that Discussions *must* be enabled on godotengine/godot-docs before this
commit is merged to `master`. Users can choose to use the "Custom" watch
mode if they don't want to get notifications for discussion updates,
but still get notifications for issue and pull request updates.
User comments are intended to be used for the following purposes:
- Add a clarification or correct something in the documentation,
without having to open a pull request. Contributors are encouraged to
take a look at discussions from time to time, and see if there's information
worth incorporating in the pages themselves. Don't forget to reply to
the comment when doing so :)
- Mention a workaround for a common issue.
- Link to useful third-party resources that are relevant to the current page,
such as tutorials or add-ons.
User comments should *not* be used for technical support. Other community
platforms should be used for that.
Page-to-discussion matching is done using the `pagename` Sphinx variable,
which is independent of the Godot version and documentation language.
Being independent of the Godot version allows keeping old comments
when the Godot version changes, while also allowing users from `/stable`
and `/4.1` to "see" each other in discussions.
See https://giscus.app for more information.
Until now, there was little documentation on how to create breakpoints
(including persistent ones with the `breakpoint` keyword). This may
not be obvious to those who haven't used other IDEs before.
This also documents' breakpoints persistent behavior since the editor
state is saved.
* Document the Visual Profiler debugger tab, update some screenshots to 4.0
* Update tutorials/scripting/debug/debugger_panel.rst
Co-authored-by: Clay John <claynjohn@gmail.com>
---------
Co-authored-by: Max Hilbrunner <mhilbrunner@users.noreply.github.com>
Co-authored-by: Clay John <claynjohn@gmail.com>
