TPropertyTag.nValueLength encoding RequestParmSize

[petemoore]

Just a short question. I noticed that TPropertyTag.nValueLength is set to the property tag request value size (with bit 31 cleared) here. The mailbox property interface wiki page defines these bits as reserved ("b30-b0: reserved") so I had been setting these bits simply to zero. I had a look at Linux to see what it was doing, and I saw it is also just setting the whole word to zero, e.g. here. I was mostly curious what the reason was to specify the property tag request length here, and what led you to encode that value rather than just set it to zero. Was it by inspecting the mailbox response after the VC update, and realising that bits 0 to 30 were just the request tag value size?

No worries if you have forgotten, I see the last update was 6 years ago! It also looks not too important since both ways work, was mostly just out of curiosity! Thanks Rene. :-)

[rsta2]

My property mailbox code was initially written somewhere in mid 2013, when the firmware wiki page was probably showing this. This should explain the difference.