QtitanDataGridModel-view DataGrid component with rich functionality for Qt.C++ and PySideQtitanRibbonReplicates Microsoft RibbonUI interface for Qt.C++ and PySideQtitanNavigationDesignUIReplicates Microsoft Navigation Design interface for Qt.C++ and PySideQtitanChartCharts and Diagrams component for Qt.C++ and PySideQtitanDockingDockable Panels and Tool Bars for Qt.C++ and PySideQtitanFastInfosetXML Compressed format FastInfoset implementation for Qt.C++ and PySideRoadmap Development 2023
FireDataGridPowerful, modern, fast, DB-Aware Grid for Delphi-FiremonkeyFireDockingDelphi IDE/Visual Studio implementation of dock panels for Delphi-Firemonkey
I have some dialogs that are using qtableviews, and I'm planning to replace them with qtitangrid.
At the present the dialogs I made are using the currentRowChanged signal of the selectionModel linked to the tableviews to update some items contents in relation to the view row selected: which is the correct way to replace the tableviews with qtitangrid keeping this behaviour?
Here is a screenshot of one of the dialogs i'm using:
In QtitanDataGrid 2.0 you can use one of the following signals to implement the behavior what you describe before:
void GridTableView::rowClicked(QObject* sender, RowClickEventArgs* args);
void GridTableView::rowDblClicked(QObject* sender, RowClickEventArgs* args);
void GridTableView::cellClicked(QObject* sender, CellClickEventArgs* args);
void GridTableView::cellDblClicked(QObject* sender, CellClickEventArgs* args);
void GridTableView::focusRowChanged(QObject* sender, int oldRowIndex, int rowIndex);
void GridTableView::focusColumnChanged(QObject* sender, int oldColumnIndex, int columnIndex);
focusRowChanged, focusColumnChanged - signals will be thrown regardless of the change focus reason (mouse, keyboard or other). I think in your case it is the most optimal variant.