KTextEditor
Document Extension Interfaces
Collaboration diagram for Document Extension Interfaces:
![]() |
Detailed Description
A KTextEditor implementation may implement a Document extension interface, but it does not need to.So as a KTextEditor user you have to cast the Document to the desired interface and then check, whether the cast returns NULL or the valid interface.
Use qobject_cast to cast a Document doc into the DesiredExtensionInterface, example:
// doc is of type KTextEditor::Document* KTextEditor::DesiredExtensionInterface *iface = qobject_cast<KTextEditor::DesiredExtensionInterface*>( doc ); if( iface ) { // the implementation supports the interface // do stuff } else { // the implementation does not support the interface }
- See also:
- KTextEditor::Document
Modules | |
Smart Cursors and Ranges | |
Classes | |
class | KTextEditor::AnnotationInterface |
A Document extension interface for handling Annotations. More... | |
class | KTextEditor::MarkInterface |
Mark extension interface for the Document. More... | |
class | KTextEditor::ModificationInterface |
External modification extension interface for the Document. More... | |
class | KTextEditor::SearchInterface |
Search interface extension for the Document. More... | |
class | KTextEditor::SessionConfigInterface |
Session config interface extension for the Document, View and Plugin. More... | |
class | KTextEditor::SmartInterface |
A Document extension interface for handling SmartCursors and SmartRanges. More... | |
class | KTextEditor::VariableInterface |
Variable/Modeline extension interface for the Document. More... |