QUndoStack across 2 cpps? QTreeView and QGraphicsScene
-
@StudentScripter your tree view has no reason to be doing that setup with the scene. They share a model, they don't need to know about each other.
As for the delegate, your goal is clear, and again, the editorEvent is what you want to use to implement the behavior you want.
wrote on 11 Jan 2024, 07:35 last edited by@SGaist Well but as i understand it with
model = new ViewLayerStandartItemModel(0,1,this);im creating a new instance of this class, a new object. So in order to have access to the same model i have to pass the object i create in the treeview trough to the scene.
Is this a mistake? How should i do it instead? -
@SGaist Well but as i understand it with
model = new ViewLayerStandartItemModel(0,1,this);im creating a new instance of this class, a new object. So in order to have access to the same model i have to pass the object i create in the treeview trough to the scene.
Is this a mistake? How should i do it instead?@StudentScripter you should create the model in the class that manages the ViewLayerList object and set it on both objects there. In the absolute, with the code you show, ViewLayerList is not even needed unless there are some additional function you are implementing. If not, then just use QTreeView directly and configure it in the class managing it.
-
@StudentScripter you should create the model in the class that manages the ViewLayerList object and set it on both objects there. In the absolute, with the code you show, ViewLayerList is not even needed unless there are some additional function you are implementing. If not, then just use QTreeView directly and configure it in the class managing it.
wrote on 12 Jan 2024, 08:12 last edited by@SGaist Yes im implementing additional functions in the qtreeview/ViewLayerList, thats why i subclassed it. Im creating the model object directly in ViewLayerLists constructor, cause i use that model mostly in this cpp.
So i guess my approach with giving the model from there to the scene is okish?
-
@SGaist Yes im implementing additional functions in the qtreeview/ViewLayerList, thats why i subclassed it. Im creating the model object directly in ViewLayerLists constructor, cause i use that model mostly in this cpp.
So i guess my approach with giving the model from there to the scene is okish?
@StudentScripter no, it makes that class know another one just for the purpose of sharing the model. That's tight coupling for the bad reasons.
-
@StudentScripter
It seems to me you have two possible general approaches:-
Use signals & slots to communicate between the tree view and the graphics scene. This can alleviate the need for each side to know too much about the other side. But be careful not to get into an "infinite loop", where each side "ping pongs" signals between themselves for some change.
-
As @SGaist says, create a common model and share the model between both sides. For example,
QStandardItemis part of aQStandardItemModel. You can already have multiple views (e.g.QTreeView) attached to the same model, make it so (some wrapper around) theQGraphicsSceneshares that model with your oneQTreeView. All your operations, like selecting or clicking a checkbox, should be implemented in the model, not the view or scene. Then that emits signals likedataChanged()orselectionChanged()in response to your actions and both views get notified about it and react in their own ways. The model code can be kept in its own/class/module/file, that is included into both the tree view & graphics scene classes, they should not need to see each other directly. This would be my inclination.
wrote on 12 Jan 2024, 22:03 last edited by@JonB said in QUndoStack across 2 cpps? QTreeView and QGraphicsScene:
The model code can be kept in its own/class/module/file, that is included into both the tree view & graphics scene classes, they should not need to see each other directly. This would be my inclination.
-
-
@JonB said in QUndoStack across 2 cpps? QTreeView and QGraphicsScene:
The model code can be kept in its own/class/module/file, that is included into both the tree view & graphics scene classes, they should not need to see each other directly. This would be my inclination.
wrote on 13 Jan 2024, 09:24 last edited by@JonB Ok and from their i add an setter in the qtreeview class and the viewlayerlist to retrieve the model.
-
@JonB Ok and from their i add an setter in the qtreeview class and the viewlayerlist to retrieve the model.
wrote on 13 Jan 2024, 13:33 last edited by@StudentScripter Yes, a suitable public getter & setter for the model called from each of the
QTreeViewandQGraphicsScenemodules. -
@JonB Ok and from their i add an setter in the qtreeview class and the viewlayerlist to retrieve the model.
@StudentScripter QTreeView already has a setter for the model. You just need to add one to your QGraphicsScene subclass.
-
@StudentScripter QTreeView already has a setter for the model. You just need to add one to your QGraphicsScene subclass.
wrote on 22 Jan 2024, 20:10 last edited by@SGaist Yep done everything and works fine. :D
-
@SGaist Yep done everything and works fine. :D
@StudentScripter great !
Then please mark the model as solved using the "Topic Tools" button or the dotted menu beside the answer you deem correct so that other forum users may know a solution has been found :-)
-
S StudentScripter has marked this topic as solved on 22 Jan 2024, 20:22