@CJha The problem is that you can't just replace something in a file if new value has different lenght than the old one. In this case you need to read the file into memory, replace the value and write it back. To read such an ini file and replace something there Qt needs to know how to interpret the data it reads.

I should probably mention that i'm writing this in PyQt5 and therefor tried not to mention the code too much. Since the first thing you mention is the code, does that mean that you think architecturally it should work fine with a standardItemModel? I can always code my way around the crash, but i'm more interested in good architecture for this problem. Do you need more information about the data?

Thanks for the reply :)

@Christian-Ehrlicher said in Support for QStandardItem proxies?:

But only when Qt was compiled in debug mode

Yes, as the docs say using invalid indexes remains undefined behaviour, I am just trying to help users spot these cases

Unless you go into very specific obscure cases

Another software design possibility would be to fiddle with proxies for data models (and their items), wouldn't it?

@elfring said in Support for constructing QStandardItem objects from QVariant references?:

I would appreciate if I can reuse existing functionality from a higher level base class.

Sorry! I just re-read this line and realized you said "higher level base class". In this case, please ignore what I said about choosing pros and cons.