Hi Odd,
Did you read my other posting where I give reasons to try and keep things collected?
Yes, and i try to kept informed of the xaaes development, so yes i know the WF_OPTS stuff.
Splitting up and having more than one function deal with the same thing is not good I think.
agree
I would opt to keep things classified as 'window options' configurable via the obvious call, in this case wind_set()
My point is that the particular WM_REPOSED message (or 'extended' WM_SIZED message) is not a 'window option', that's why i don't like that much the usage of wind_set() for this particular feature.
best regards, Arnaud.