This seems to be a .Net Framework bug. Does anyone know if a fix is in the
pipeline or of a workaround?

The problem arises if a WinForms TreeView is placed on top of a form which
in turn is on another form. In this situation the tooltips that normally
appear when a treenode is too long to be displayed in the treeview are not
shown properly; they are clipped by the main form.

e.g. Arrangement is like this...

MainForm
    ChildForm [TopLevel = false, DockStyle.Right]
        TreeView [DockStyle.Fill]

My theory, based on some Spy++ investigation, is that two Win32 tooltip
windows are created, one for the mainform and one for the childform, but in
this situation the treeview prefers the tooltip window of the childform,
which is before the mainform in the windows z-order. So the tooltip gets
clipped by the MainForm.

Gary Leighton



KSS Ltd
A division of Knowledge Support Systems Group plc
Seventh Floor  St James's Buildings  79 Oxford Street  Manchester  M1 6SS  England
Company Registration Number 2800886 (Limited) 3449594 (plc)
Tel: +44 (0) 161 228 0040       Fax: +44 (0) 161 236 6305
mailto:[EMAIL PROTECTED]            http://www.kssg.com


The information in this Internet email is confidential and may be legally privileged. 
It is intended solely for the addressee(s). Access to this Internet email by anyone 
else is unauthorised.

If you are not the intended recipient, any disclosure, copying, distribution or any 
action taken or omitted to be taken in reliance on it, is prohibited and may be 
unlawful. When addressed to our clients any opinions or advice contained in this 
Internet email are subject to the terms and conditions expressed in the governing 
engagement letter or contract.

This email message and any attached files have been scanned for the presence of 
computer viruses.  However you are advised that you open any attachments at your own 
risk.


You can read messages from the Advanced DOTNET archive, unsubscribe from Advanced 
DOTNET, or
subscribe to other DevelopMentor lists at http://discuss.develop.com.

Reply via email to