Unfortunately, it is hard to reproduce the problem because it occurs rarely or maybe fortunately. Therefore, I do not exclude the possibility of a problem related to my script. I reproduced the bug in Windows Vista Ultimate - it is the same transparent tooltip without text.
Back to Issues. Reply to quoted posts Clear. Register now! Username or email:. I've forgotten my password Forum Password. Remember me This is not recommended for shared computers. Quote from: 3am on February 13, , pm. It's possible that you are getting something different because you are using Classic Shell Explorer instead of the default Explorer. I know it says it's already white but it looks like and shows up as a pale yellow unless you change it.
You will still need to use the TreeItem textcolors for the rest. I don't know whether this will work. Otherwise I'm out of ideas. If you don't believe me just change all the TreeItem textcolors to different colors and then test and see for yourself what happens.
Thanks Mike , quite so like simple control set the ToolTip property of the button in designer. But the other control like ListView , as we all know ,if set the ToolTip property of the ListView , the ToolTip would be shown only mouse on the first column ,this is not welcome. The ToolTip shows on the second column is what I want. SetToolTip listView1, selection. In addition , Mouse Enter event causes that the ToolTip shows as long as the mouse enter the control. Fortunately , I solved the problem.
This way seems like a little stupid. Declare variable x and y stand for x and y coordinate ,when trigger the mouse move event ,compare x and y with the new coordinate ,if equal and then do nothing otherwise show the tooltip. That way can avoid flickering tooltip. Y return;. I played a bit more with this and it seems is not a rendering problem but a problem with the MouseMove message.
If you move the mouse over an item the tooltip is shown and another MouseMove message is delivered to the ListView without the mouse being actually moved. I saw another thread on another problem but that also caused MouseMove message to be delivered without the mouse being actually moved and that resulted in this kind of loop so I suppose it's a problem in the current builds of Vista and hopefully it's going to be fixed in the final build.
The content you requested has been removed. Ask a question.
0コメント