Just like i update the data for an existing item's column , such as with a blake3 hash, i can also get an existing treenodemodel column's data using a similar function.
I just had this epiphany, which i should have though about long before, but if this works then i can possibly go back through my code and replace a good chunk of the slower treenodemodel->match() functions for a given itemid and just use my call which goes through the treenodemodel's qhash function and simply get's the value.
This could be a big speedup in a lot of places....
Just like i update the data for an existing item's column , such as with a blake3 hash, i can also get an existing treenodemodel column's data using a similar function.
I just had this epiphany, which i should have though about long before, but if this works then i can possibly go back through my code and replace a good chunk of the slower treenodemodel->match() functions for a given itemid and just use my call which goes through the treenodemodel's qhash function and simply get's the value.
This could be a big speedup in a lot of places....