Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Op 14/01/2016 om 01:08 schreef Stephen Kelly: Bo Thorsen wrote: To me QStandardItemModel is a quick hack I sometimes use when I just want to show a bit on the screen. But those temporary things have a tendency to stick around, and at some point I always end up rewriting the stuff with the real

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Thanks Bo, I made some progress with QStandardItemModel, an d will try to pull even with the QAbstractTable model approach, hopefully that will help getting a feeling for it all. >>If you have performance issues with a QAbstractTableModel over a QStandardItemModel, you're doing something >>w

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Thanks Andreas, that all makes sense. Will give the more manual approach some more attention. Cheers, frank On 14/01/16 12:00 pm, Andreas Pakulat wrote: Hi, On Wed, Jan 13, 2016 at 11:07 PM, Frank Rueter | OHUfx mailto:fr...@ohufx.com>> wrote: Thanks Bo, when you say "it's bad in s

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Bo Thorsen wrote: > To me QStandardItemModel is a quick hack I sometimes use when I just > want to show a bit on the screen. But those temporary things have a > tendency to stick around, and at some point I always end up rewriting > the stuff with the real thing. Me too. I only ever use QSIM in te

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Hi, On Wed, Jan 13, 2016 at 11:07 PM, Frank Rueter | OHUfx wrote: > Thanks Bo, > > when you say "it's bad in so many ways", are you referring to performance? > > I just realised that my last conversation with Jason had dropped the CC to > the list, so here it is again : > > so a few lines into t

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Den 13-01-2016 kl. 23:07 skrev Frank Rueter | OHUfx: when you say "it's bad in so many ways", are you referring to performance? Performance and ease of data manipulation are the two biggest points. But it's really simpler than this. To use an old design phrase - that class just smells bad.

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Den 13-01-2016 kl. 23:07 skrev Frank Rueter | OHUfx: Thanks Bo, when you say "it's bad in so many ways", are you referring to performance? I just realised that my last conversation with Jason had dropped the CC to the list, so here it is again : so a few lines into the new code and I bel

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Thanks Bo, when you say "it's bad in so many ways", are you referring to performance? I just realised that my last conversation with Jason had dropped the CC to the list, so here it is again : so a few lines into the new code and I believe I'm starting to realise that QAbstractTableMode

Re: [Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Hi Frank, Den 12-01-2016 kl. 22:40 skrev Frank Rueter | OHUfx: I just joined this list so hello everybody. I'm using QT via PySide mainly to create tools for vfx workflows and custom tools for the software Nuke. I'm not a programmer by trade, more of

[Interest] need advise on QStandardItemModel vs. QAbstractTableModel

Hi, I just joined this list so hello everybody. I'm using QT via PySide mainly to create tools for vfx workflows and custom tools for the software Nuke. I'm not a programmer by trade, more of a vfx artist and technician using Python/PySide to enhanc