Is the call order guaranteed for multiple SetWindowSubclass against the same window?

Question

I am using SetWindowSubclass to set up two different subclass procedures against a control (in this case, a multiline edit field).

One subclass "edit" functionality specific to edit controls and the other "base" functionality specific to any control. It seems that no matter what order I apply these in "base" is being called before "edit".

Has anyone else hit this issue?

Answer 1

There is no guarantee of order, sorry.