When composing a message, the mouse cursor disappears as soon as one starts to type.
However, randomly, the mouse pointer will disappear and never return until you move the mouse pointer outside of the compose window entirely.
This means that highlighting text, copying and pasting are effectively impossible -- as, you have zero idea where the cursor is.
Debian Jessie, 3.14.1 backports and 3.11.1 both exhibit this problem.
"Randomly" means "randomly, during the compose session". Every single time I compose an email, this happens, but it does not happen instantly.
I have not yet seen a pattern which is visually apparent depending upon the text I type. For example, I thought perhaps the spell checker might cause some code to fire, which borked the "re-appear when moved" cursor code -- but no.
As well, if you right click (to bring up the menu), or left click -- the cursor will reappear when you move it.
Older versions of claws, it seems to be, simply re-exhibited the pointer. Like all other apps do.
Never encountered that, and never seen it reported previously. Looks like a local problem. I think if you tried those other versions of claws-mail I'd bet they now do the same on your system.
And yet -- absolutely no other application behaves this way on my system.
There are indeed particulars to my system, which are unique. All systems are this way. For example, I use a 4k display. It could be that DPI or screen size is somehow messing up claw's algorithm that determines when to make the mouse cursor re-appear.
Yet -- no other app seems to hide my cursor, then never allow it to re-appear until I move outside of its compose window.
This indeed seems like a claws bug.
Do you have no other answer, no other information you would like -- instead of simply closing INVALID? This seems to be jumping the gun a bit...
> When composing a message, the mouse cursor disappears as soon as one starts to
Same here, always considered that as a feature, especially as gvim behaves the same: as soon as you start type, mouse pointer is hidden and you need to move the mouse to have it back.
> However, randomly, the mouse pointer will disappear and never return until you
> move the mouse pointer outside of the compose window entirely.
> When composing a message, the mouse cursor disappears as soon as
> one starts to type.
That's normal. Other editors, such as GEdit or Emacs, do that, too, so the cursor doesn't disturb your view. Simply moving the mouse makes the pointer reappear.
Btw, unconfirmed and dubious issues like this are better discussed on the mailing-list instead of entering a bug report right away.
(In reply to comment #3)
> And yet -- absolutely no other application behaves this way on my system.
What other GTK2 apps on your system do not show this?
Can we cut the 'it's supposed to disappear!' comments? Yes, of course it is. At no time did anyone, including me, state that it shouldn't disappear.
It's merely *information*, to aid in the debug flow.
And while we're at it, could we cut the 'it's never happened to me!' comments? Clearly, if it happened to "you", you'd have filed a bug. Or looked at the code. Or, you know, said or done something.
Back to the bug, instead of all of this cross talk...
Paul -- gvim (debian's vim-gtk package) exhibits this behaviour correctly. I start to type, cursor disappears. I move the mouse, cursor reappears. No clicking is required to make the mouse cursor reappear.
Same user account, same system.
This has been going on for about a year -- but, I've finally had some cycles to deal with this now.
With all this cross talk, and pointless "me too!" and "it's supposed to disappear" blather, enough. You were right to close this bug, Paul.
After all, there is zero movement on your end to actually think about it, ponder it, or debug it. Or, you know, even take bug reports seriously.
Marked 'resolved' because "fuck this noise".
(In reply to comment #7)
Thank you not-your-domain-name@your-domain-name for your patience and kind words. The behaviour you described by mixing your terms is how GTK works, this is why it is INVALID.
> gvim (debian's vim-gtk package) exhibits this behaviour correctly.
> I start to type, cursor disappears. I move the mouse, cursor reappears.
> No clicking is required to make the mouse cursor reappear.
Earlier you've only claimed you need to move the mouse pointer out of the window completely for it to reappear, now you have to click somewhere?
> All systems are this way. For example, I use a 4k display.
"All systems"? What are the notable differences between the systems, their hardware and runtime portions?
Which window managers or desktop managers have you tried so far?