QTextMarkdownImporter::import() took a QTD* as if it would be ok to reuse one instance of QTextMarkdownImporter for repeated importing into different documents; but in practice, we never do that: in fact it's usually a short-lived, stack-allocated object, as in QTextMarkdownImporter(&doc, QTMI::DialectGitHub).import(input); So it's less clumsy internally to require the document be provided to the constructor: that way a QTextCursor can be constructed immediately too, as part of the importer object rather than separately on the heap. This is private API, unused outside qtbase. Change-Id: I8041ceb33cb7e7608df55dc5a963292c585afb90 Reviewed-by: Oliver Eftevaag <oliver.eftevaag@qt.io> Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com> |
||
|---|---|---|
| .. | ||
| image | ||
| itemmodels | ||
| kernel | ||
| math3d | ||
| painting | ||
| platform | ||
| qopengl | ||
| qopenglconfig | ||
| qvulkan | ||
| rhi | ||
| text | ||
| util | ||
| CMakeLists.txt | ||