KTextEditor
Collaboration diagram for Document Extension Interfaces:
Modules | |
Smart Cursors and Ranges | |
MovingCursors and MovingRanges | |
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
The following classes are a list of all available Document extension interfaces.
This file is part of the KDE documentation.
Documentation copyright © 1996-2014 The KDE developers.
Generated on Tue Oct 14 2014 22:31:41 by doxygen 1.8.7 written by Dimitri van Heesch, © 1997-2006
Documentation copyright © 1996-2014 The KDE developers.
Generated on Tue Oct 14 2014 22:31:41 by doxygen 1.8.7 written by Dimitri van Heesch, © 1997-2006
KDE's Doxygen guidelines are available online.