diff --git a/reference_manual/tools/rectangular_select.rst b/reference_manual/tools/rectangular_select.rst --- a/reference_manual/tools/rectangular_select.rst +++ b/reference_manual/tools/rectangular_select.rst @@ -54,7 +54,9 @@ Gives the current height. Use the lock to force the next selection made to this height. Ratio Gives the current ratio. Use the lock to force the next selection made to this ratio. + .. versionadded:: 4.1.3 + Round X The horizontal radius of the rectangle corners. Round Y diff --git a/untranslatable_pages/cmake_settings_for_developers.rst b/untranslatable_pages/cmake_settings_for_developers.rst --- a/untranslatable_pages/cmake_settings_for_developers.rst +++ b/untranslatable_pages/cmake_settings_for_developers.rst @@ -6,14 +6,14 @@ :authors: - Boudewijn Rempt :license: GNU free documentation license 1.3 or later. - + .. _cmake_settings_for_developers: ============================= CMake Settings for Developers ============================= -The `CMake `_ build system generators used by Krita is one of the most used build system generatorss in the C++ world. A build system is a system that describes how a an application should be built from source code. CMake generates a build system from the information given in the CMakeLists.txt and *.cmake files. It is a complete but rather unusual language. +The `CMake `_ build system generators used by Krita is one of the most used build system generatorss in the C++ world. A build system is a system that describes how a an application should be built from source code. CMake generates a build system from the information given in the CMakeLists.txt and `*.cmake` files. It is a complete but rather unusual language. If you start working on Krita, you will need knowledge of two things: how to run the cmake generator, and which variables are important there, and how to edit the CMakeLists.txt files. This page tells you how to run the cmake generator. @@ -22,7 +22,7 @@ .. code:: cmake -DSOME_CMAKE_VARIABLE=SOME_VALUE ../path/to/source - + That is, every option is prefixed with -D, followed by a usually uppercase variable name, the equal sign and the value. The following variables are important for Krita. You cannot build Krita inside the source directory, so you need to give the path to the source directory, where the top-level CMakeLists.txt file is found. @@ -76,7 +76,7 @@ This option enables the experimental lock free hash table. This is ON by default at the moment. -FOUNDATION_BUILD +FOUNDATION_BUILD ---------------- This option is for packaging Krita on systems that do not have the default color themes shipped by KDE Plasma. @@ -96,7 +96,7 @@ Use Python 2 instead of Python 3. Only to be used when integrating Krita in a python2-based VFX pipeline. -BUILD_KRITA_QT_DESIGNER_PLUGINS +BUILD_KRITA_QT_DESIGNER_PLUGINS ------------------------------- OFF by default, enable this to build plugins for Qt Designer/Qt Creator so you can add Krita specific widgets to .ui files. diff --git a/untranslatable_pages/reporting_bugs.rst b/untranslatable_pages/reporting_bugs.rst --- a/untranslatable_pages/reporting_bugs.rst +++ b/untranslatable_pages/reporting_bugs.rst @@ -6,8 +6,8 @@ :authors: - Boudewijn Rempt :license: GNU free documentation license 1.3 or later. - -.. _triaging_bugs: + +.. _reporting_bugs: ============== Reporting Bugs @@ -55,13 +55,14 @@ Krita's chat channel is maintained on irc.freenode.net. Developers and users hang out to discuss Krita's development and help people who have questions. -.. important:: +.. important:: + Most Krita developers live in Europe, and the channel is very quiet when it's night in Europe. You also have to patient: it may take some time for people to notice your question even if they are awake. + - Most Krita developers live in Europe, and the channel is very quiet when it's night in Europe. -You also have to patient: it may take some time for people to notice your question even if they are awake. +.. admonition:: Also ... + Krita does not have a paid support staff. You will chat with volunteers, users and developers. It is not a help desk. -.. admonition:: Krita does not have a paid support staff. You will chat with volunteers, users and developers. It is not a help desk. But you can still ask your question, and the people in the channel are a friendly and helpful lot. @@ -95,10 +96,10 @@ - Tell us what kind of image you were working on: the size, the resolution, the color model and channel depth. - If you are reporting a crash, attach a crash log. Follow `this link `_ to learn how to get a crash log on Windows. On Linux, follow your distributions instructions to install debug symbols if you have installed Krita from a distribution package. It is not possible to create a useful crash log with Linux appimages. -The problem needs to be clearly stated: -- what happened, -- what had you expected to happen instead -- how the problem can be reproduced. +The problem needs to be clearly stated: +- what happened, +- what had you expected to happen instead +- how the problem can be reproduced. Give a concise and short description, then enumerate the steps needed to reproduce the problem. If you cannot reproduce the problem, and it isn't a crash, think twice before making the report: the developers likely cannot reproduce it either. @@ -115,7 +116,7 @@ When a developer decides to investigate your report, they will start adding comments to the bug. There might be additional questions: please answer them as soon as possible. -When the developer has come to a conclusion, they will **resolve** the bug. That is done by changing the resolution status in the bug tracker. These statuses are phrased in developer speak, that is to say, they might sound quite rude to you. There's nothing that we can do about that, so do not take it personally. The bug reporter should *never* change the status after a developer changed it. +When the developer has come to a conclusion, they will **resolve** the bug. That is done by changing the resolution status in the bug tracker. These statuses are phrased in developer speak, that is to say, they might sound quite rude to you. There's nothing that we can do about that, so do not take it personally. The bug reporter should *never* change the status after a developer changed it. These are the most used statuses: