openmw.org

If you want multiple views on the same data, having a single view model was the only sane way i saw to update all views if you change the data in one view (that already worked, also multiple views was working). For the single record type editors, the plan was to fetch a "managed" record fr...

Can you tell me the design flaws that made it necessary to start a new branch from scratch?

Can you disable the shadows and see if it works?
I think i had the same issue.

corycohen wrote:Did I understand correctly?

No, the string is the namespace and name of the index.

Basically something like this:
QHash<QPair<QString, QVariant>, ModelItem*>

corycohen wrote:I'm open to other ways of achieving our own unified keying mechanism.

For the editor i was thinking about namespacing the indices.

Nice, i like the theme.

jedd wrote:My plan is then to keep on tweaking and optimizing as time goes by and, if possible, make a few modifications to the blog's code and design too.

Maybe we should put the blog and forum theme into a github repository so that optimizing it can be a collaborative effort.

Certainly you can have multiple view classes for a single model(-interface) in Qt, right. Yes, i currently use the same viewmodel [model(-interface)] for the filtertree and the combobox in the idlist. I just don't see what such an all all-encompassing tree view would be good for. It is a fast and e...