Files
create/src/Mod/TechDraw/Gui/ViewProviderAnnotation.cpp
Markus Reitböck 0019739095 TechDraw: use CMake to generate precompiled headers on all platforms
"Professional CMake" book suggest the following:

"Targets should build successfully with or without compiler support for precompiled headers. It
 should be considered an optimization, not a requirement. In particular, do not explicitly include a
 precompile header (e.g. stdafx.h) in the source code, let CMake force-include an automatically
 generated precompile header on the compiler command line instead. This is more portable across
 the major compilers and is likely to be easier to maintain. It will also avoid warnings being
 generated from certain code checking tools like iwyu (include what you use)."

Therefore, removed the "#include <PreCompiled.h>" from sources, also
there is no need for the "#ifdef _PreComp_" anymore
2025-09-23 00:50:59 +02:00

142 lines
5.8 KiB
C++

/***************************************************************************
* Copyright (c) 2004 Jürgen Riegel <juergen.riegel@web.de> *
* Copyright (c) 2012 Luke Parry <l.parry@warwick.ac.uk> *
* *
* This file is part of the FreeCAD CAx development system. *
* *
* This library is free software; you can redistribute it and/or *
* modify it under the terms of the GNU Library General Public *
* License as published by the Free Software Foundation; either *
* version 2 of the License, or (at your option) any later version. *
* *
* This library is distributed in the hope that it will be useful, *
* but WITHOUT ANY WARRANTY; without even the implied warranty of *
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the *
* GNU Library General Public License for more details. *
* *
* You should have received a copy of the GNU Library General Public *
* License along with this library; see the file COPYING.LIB. If not, *
* write to the Free Software Foundation, Inc., 59 Temple Place, *
* Suite 330, Boston, MA 02111-1307, USA *
* *
***************************************************************************/
#include <QPushButton>
#include <App/DocumentObject.h>
#include <Gui/ComboView.h>
#include <Gui/DockWindowManager.h>
#include <Gui/propertyeditor/PropertyEditor.h>
#include <Gui/propertyeditor/PropertyModel.h>
#include <Mod/TechDraw/App/DrawLeaderLine.h>
#include <Mod/TechDraw/App/DrawViewBalloon.h>
#include "QGIView.h"
#include "ViewProviderAnnotation.h"
using namespace TechDrawGui;
PROPERTY_SOURCE(TechDrawGui::ViewProviderAnnotation, TechDrawGui::ViewProviderDrawingView)
//**************************************************************************
// Construction/Destruction
ViewProviderAnnotation::ViewProviderAnnotation() { sPixmap = "actions/TechDraw_Annotation"; }
ViewProviderAnnotation::~ViewProviderAnnotation() {}
void ViewProviderAnnotation::updateData(const App::Property* prop)
{
if (prop == &(getViewObject()->Text) || prop == &(getViewObject()->Font)
|| prop == &(getViewObject()->TextColor) || prop == &(getViewObject()->TextSize)
|| prop == &(getViewObject()->LineSpace) || prop == &(getViewObject()->TextStyle)
|| prop == &(getViewObject()->MaxWidth)) {
// redraw QGIVP
QGIView* qgiv = getQView();
if (qgiv) {
qgiv->updateView(true);
}
}
ViewProviderDrawingView::updateData(prop);
}
std::vector<App::DocumentObject*> ViewProviderAnnotation::claimChildren() const
{
// Collect any child Document Objects and put them in the right place in the Feature tree
// valid children of an Annotation are:
// - Balloons
// - Leaders
std::vector<App::DocumentObject*> temp;
const std::vector<App::DocumentObject*>& views = getViewObject()->getInList();
try {
for (std::vector<App::DocumentObject*>::const_iterator it = views.begin();
it != views.end(); ++it) {
if ((*it)->isDerivedFrom<TechDraw::DrawViewBalloon>()) {
temp.push_back((*it));
}
else if ((*it)->isDerivedFrom<TechDraw::DrawLeaderLine>()) {
temp.push_back((*it));
}
}
return temp;
}
catch (...) {
return std::vector<App::DocumentObject*>();
}
}
TechDraw::DrawViewAnnotation* ViewProviderAnnotation::getViewObject() const
{
return dynamic_cast<TechDraw::DrawViewAnnotation*>(pcObject);
}
bool ViewProviderAnnotation::doubleClicked()
{
setEdit(ViewProvider::Default);
return true;
}
bool ViewProviderAnnotation::setEdit(int ModNum)
{
if (ModNum != ViewProvider::Default) {
return ViewProviderDrawingView::setEdit(ModNum);
}
// retrieves the PropertyEditor of the Data tab in the comboview of the
// mainwindow and opens the editor of the "text" property of the selected
// item and mimics a click of the button inside that editor, which opens
// the plain text edit dialog
// I feel quite dirty writing this but that was the cleanest way to prevent
// code duplication, because everything just works as long as the structure
// does not change. In case this modus operandi gets used more
// often, this should be delegated to a utility function that takes a property
// path and opens the "deepest" editor of that property
auto comboView = qobject_cast<Gui::DockWnd::ComboView*>(
Gui::DockWindowManager::instance()->getDockWindow("Model"));
if (!comboView) {
return false;
}
auto dataPropView = comboView->findChild<Gui::PropertyEditor::PropertyEditor*>(
QStringLiteral("propertyEditorData"));
if (!dataPropView) {
return false;
}
auto dataPropModel = qobject_cast<Gui::PropertyEditor::PropertyModel*>(dataPropView->model());
if (!dataPropModel) {
return false;
}
// the property data is a tree model, to we need the first item in the first group
auto index = dataPropModel->propertyIndexFromPath(
{QStringLiteral("Annotation"), QStringLiteral("Text")});
// setting the current item also opens the editor
dataPropView->setCurrentIndex(index);
dataPropView->activated(index);
// there is a button in the editor widget that opens a plain text dialog
auto button = dataPropView->findChild<QPushButton*>();
if (button) {
button->click();
}
return true;
}