[EMAIL PROTECTED] wrote: > *Type* info > *Title* Window loses methods > *Posted by* [EMAIL PROTECTED] > *Affected* ..., > *Effective from* warnings01 > > > > /*Summary*/ > > > -BOOL Window::IsUICaptured() const; > -BOOL Window::IsUserActive( USHORT nTest = USERACTIVE_ALL, BOOL bChilds = > FALSE ) const; > -ULONG Window::GetLastInputInterval() const; > > > > /*Description*/ > > these methods were never used and the implementation just calls the > respective Application methods anyway - so no functionality lost
I'm not sure wether this is the right move. The mere fact that nobody uses the Window methods doesn't mean that they are superfluous, perhaps it's a bug that they aren't used (though perhaps not an important one). AFAIR these methods have been introduced to supplement the Application methods because it is a valid assumption that in some cases one is interested wether user interaction is done in a particular window. As an example, there is no need to prevent a window from closing if user input is pending in another one. If the Window methods call the Application methods my question is: do they do this because it is not possible to implement the methods as expected or was it just not done? In case it's the first reason then of course removing the methods make sence. In case it's the latter I miss an explanation why the methods quoted above should be removed at all instead of implementing (and using) them correctly. Could you please explain? Ciao, Mathias --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
