On 05.04.2017 16:26, Stefan Dösinger wrote:
Am 2017-04-05 um 14:53 schrieb Nikolay Sivov:
Maybe I don't see a full picture yet, but doesn't this duplicate 'id' flag? We use it for ListView/Header combined sequences for example.
It's not exactly the same, "id" is more a generic extra payload field. The pager test e.g. uses it to communicate a message id in a WM_NOTIFY message.
In the tests I currently have no extra payload, so I could use the id mechanism instead of extending the parent / control flag.
I think it's better, and will match what we're doing already for other tests.
I could also
use it in patch 6 to deal with the WINDOWPOS structures. But I'll need both child1/child2 info and WINDOWPOS in the same lines, so I can't do both.
Do you really need to test it this way? Could it be tested right in window procedure while processing POSCHANGED?