                                                                                                                                                                                                                                                                
Received-SPF: neutral (google.com: 62.127.194.20 is neither permitted nor denied by best guess record for domain of and...@papablues.com) client-ip=62.127.194.20;
Message-ID: <50641727.40605@papablues.com>
Date: Thu, 27 Sep 2012 11:06:47 +0200
From: Anders Karlsson <and...@papablues.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120907 Thunderbird/15.0.1
MIME-Version: 1.0
To: scintilla-interest@googlegroups.com
CC: Neil Hodgson <nyamaton...@me.com>
Subject: Re: [scintilla] Call tips extending beyond the bottom of the Scintilla
 Windows cases an immediate SCN_DWELLEND
References: <505F3641.4090...@papablues.com> <98E03896-6824-4CD7-999F-71654B152...@me.com> <5060B3B0.3040...@papablues.com> <5060B6F8.3060...@papablues.com> <3C394C13-58CF-44EB-A037-02A4F3DC8...@me.com> <50635BE9.1080...@papablues.com> <0AD35125-16E9-4E4A-BA70-B66C1146C...@me.com>
In-Reply-To: <0AD35125-16E9-4E4A-BA70-B66C1146C...@me.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I have created a W/O for this behavior which might be useful for someone 
else who wants to show a larger calltip window, and it's actually quite 
simple.

What I do is that I ignore the DWELLEND, instead on DWELLSTART, in 
addition to showing the calltip, I also set a global flag that I am 
showing a calltip and I get the mouse position (using GetCurrentPos()) 
in another global. Then I use WM_MOUSEMOVE to cancel the CALLTIP, but 
before that I check that a calltip is showing and the the mouse position 
is now different from when the calltip was shown.

For a larger calltip, say with multiple lines (say a description of the 
keyword), this has the advantage that the mouse can now be moved 
"inside" that window, which can make the text easier read, and while 
reading this slightly longer text, this will not disappear until the 
mouse moves bat to the editor window. I think, for this purpose, this 
looks and works nicer (but probably not do when used as simple CALLTIP 
providing, say, function arguments).

/Karlsson
On 9/27/2012 01:26, Neil Hodgson wrote:
> Anders Karlsson:
>
>>    Actually, I'm sure I'd like to regard this as a bug partly because ot used to work in previous releases (which is no guarantee that is should work the same in more recent releases, I know) and partly because this is no easy fix.
>     I don't think anything relevant has changed recently. It is likely that having another window open under the mouse has always caused a mouse leave.
>
>     You could try an old version and if that behaves differently then binary search to find the modification that changed the behaviour.
>
>     Neil
>