I have a customised edit control - the non client area is modified to display what looks like a button (eg like a combo box).
This works perfectly with both dynamic creation and subclassing.
Now I would like to extend the functionality and allow an action based on this 'button' click even when the edit box is disabled. Unfortunately the disabled window does not receive any mouse messages (at least I've not found where they are being filtered out) so the idea is shot down in flames.
Question. (I think any of the following would be suitable.)
How can I force the disabled window to receive mouse messages?
Where are the mouse messages being filtered out - how to disable that filtering?
How can I disable the client area of a window but still leave the non client area enabled?
Any other alternative?
The average business loses $13.5M per year to ineffective training (per 1,000 employees). Keep ahead of the competition and combine in-person quality with online cost and flexibility by training with Linux Academy.
With most software applications trying to cater to multiple user needs nowadays, the focus is to make them as configurable as possible. For e.g., when creating Silverlight applications which will connect to WCF services, the service end point usuall…
For most people, the WrapPanel seems like a magic when they switch from WinForms to WPF. Most of us will think that the code that is used to write a control like that would be difficult. However, most of the work is done by the WPF engine, and the W…