documentation comes from the underlying C++ language that Krita is written in. The magic happens because of a Python tool called SIP, which makes it possible for python speak in C++ and talk to Krita. The end result result is that when we import krita and call functions, we’re actually using the C++ methods listed in that documentation. Let’s see how this stuff works in more detail. Let’s take a look at the second activeWindow(), and action() which we used above. One of the more confusing things is seeing all the C++ classes that Krita uses, including the Qt classes that start with Q. But here is the beauty of SIP:

. . . 212 37.1.2 C 에서 러스트호출 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 37.2 C++와의상호운용성 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 37.2.1 테스트모듈 . . . . . . . . . . . . . . . . . . . . . . . . . 216 37.2.3 생성된 C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217 37.2.4 C++ 브리지선언 . . . . . . . . . . . . . . . . . . . . . . . . . . unsafe Rust 코드포함 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232 43.2 Chromium C++의 Rust 코드에의존 . . . . . . . . . . . . . . . . . . . . . . . . 233 43.3 Visual Studio Code . . . . .

. . . 211 37.1.2 C 에서 러스트호출 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 37.2 C++와의상호운용성 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 37.2.1 테스트모듈 . . . . . . . . . . . . . . . . . . . . . . . . . 215 37.2.3 생성된 C++ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 37.2.4 C++ 브리지선언 . . . . . . . . . . . . . . . . . . . . . . . . . . unsafe Rust 코드포함 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 43.2 Chromium C++의 Rust 코드에의존 . . . . . . . . . . . . . . . . . . . . . . . . 232 43.3 Visual Studio Code . . . . .