I agree that QTreeView would be better choice. Especially hoisting feature 
is asking for a QTreeView/Model pair. After all hoisting is just another 
view into the same model.

In current version computed icons are handled by QTreeWidgetItem, so there 
should be no difference between how it is handled now. 

The only thing that I don't understand is why are we deleting all the items 
on every redraw and then creating new ones. instead. That seems to me wrong 
and most probably is the cause for the delay in tree actions.

If any node is changed in any way, it is straight forward to change 
corresponding treeWidgetItem and not deleting all the items and recreating 
all of them again just to create different one for the node that has been 
changed. QTreeWidgetItem instances have methods setText, setIcon that can 
be used to alter them as needed.


You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To post to this group, send email to leo-editor@googlegroups.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.

Reply via email to