The strength of widget views in general is that they are very easy to get started with compared to item views, but fall short in more complex use-cases.
It does sound like you would be better off with an item view, however whether or not it's viable to switch is mostly a matter of how much further you intend on extending and maintaining your current implementation. It's quite likely that you are at a point where the amount of work involved in adding new functionality requires an exponentially increasing amount of work to get done due to having to fight the convenience provided by the widget view, and jidging by your example I'd say that this seems to be the case. On the other hand, if you're close to finishing and don't think it will need much maintenance once done then it's questionable whether the effort is worth it. Item views are undeniably more complex than their widget counterparts but their complexity is really only a reflection of how complex the data you're working with really is, and hierarchical data especially is amongst the most complex data there is. To put an analogy on your problem, you've been working with Microsoft Movie Maker and are looking to do things that Nuke has no problem doing. Do you learn Nuke, or find ways around the problem in Movie Maker? > On 15 Apr 2015, at 17:17, Ben Hearn <[email protected]> wrote: > > I am representing XML data in a tree view and enabling the editing of this > XML data, when the user changes some data in the editable fields the view is > then updated to represent this new data. > > I have not used QTreeView or any model information yet. Are there any huge > differences with adding items and editing them? Also is there that much of a > benefit in switching from QtTreeWidget especially since I am quite a leap > into the project at current. > > >> On 15 April 2015 at 17:37, Marcus Ottosson <[email protected]> wrote: >> Without fully understanding what you're up to, you may be better off with a >> QTreeView and QAbstractItemModel. The model would keep track of hierarchy, >> and your view simply represent it. Thus if you refresh the view, the data >> remains the same and if you change the data, the view updates accordingly. >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Python Programming for Autodesk Maya" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/python_inside_maya/SR3v1N1zYuc/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOD_M7Myk_4LXkgGn-QWtum53FjsAYQQVMg_ii5y1_eJvQ%40mail.gmail.com. >> >> For more options, visit https://groups.google.com/d/optout. > > > > -- > > > Tel - +46 76245 92 90 (Sweden) > LinkedIn: http://www.linkedin.com/pub/ben-hearn/50/a64/33b > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAM2ybkUwuA5Z00taxccfLUnZaUeKBgjRbdqKpu-%2BGaNE7TDWLA%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/4EF72B65-6EE8-4D48-9BAE-B7CF2644F877%40gmail.com. For more options, visit https://groups.google.com/d/optout.
