2.1 - Right Click (frequently) not working

[BetterRed]

Originally Posted by therealjoeblow

SOLVED... (I think)
...
Anyway, sorry for the false alarm, looks like my problem is solved.

@therealjoeblow - IMO no apologies needed, silver star for tracking it down, gold star for letting us know

In post #5 it was suggested it might be a 3rd party program

You could also try closing down all other programs including those in the tray/notify area, and/or try running in Safe Mode

BR

[theducks]

Andy is not so handy

[Divingduck]

Originally Posted by Divingduck

I have an additional observation. If I open a book via book list from the main window, the book will not stay highlighted blue in the book list (on the face of it) after it open in the ebook viewer. ...

Kovid,
This one is solved. Thanks

[Divingduck]

Originally Posted by kovidgoyal

@Divingduck: What that sounds like is not a right click not registering, but registering too fast. So what happens is when you press the right mouse button, the popup menu opens, if the mouse moves a little, the cursor goes over one of the entries in the menu, then when you release the button, that entry is activated. In your case this would likely have been the Cut text menu entry.

This one is still there in the new version. I can do it now repeatedly: Deleting some text in a paragraph then clicking in an other paragraph. It looks like calibre is jumping most time to the first popup menu entry and sometimes to an other one w/o giving the user a chance to make a selection in the menu.

[kovidgoyal]

Originally Posted by Divingduck

This one is still there in the new version. I can do it now repeatedly: Deleting some text in a paragraph then clicking in an other paragraph. It looks like calibre is jumping most time to the first popup menu entry and sometimes to an other one w/o giving the user a chance to make a selection in the menu.

I cannot reproduce it. A "normal" right click does not activate any items in the menu. Is your mouse old? It could be generating "bounce" clicks.

[BetterRed]

@Divingduck - if its a wireless mouse you may need new batteries, my mouse misbehaves when they're running low. And the low battery led stopped working soon after I got the darn thing Ψ²

BR

[Divingduck]

It is an older wireless logitech mouse, but it's working w/o problems in any other programs (and so fare with calibre). I changed the battary two days ago, so they will have power. My normal change period is every 4 to 5 weeks. But I will check with new batteries later today, see what happen and then come back.
... and also check with an other mouse.

[JSWolf]

Originally Posted by DrChiper

Not particularly a mouse problem, but I have noticed that while using some edit-book buttons, like find, replace, and such, sometimes nothing seems to happen (no visual feedback when it is expected). Clicking again solves this always thereafter and all works perfectly thereafter. It is like calibre is missing the click event.
I admit, I click fast, but I did not change my habits when I switched from 1.48 to 2.1, and I never encountered it in the past before.

All on Win 7 64 bit, using calibre 2.1

I've seen similar issues like this before (not with Calibre) and the problem was a failing mouse button. So yes, please do try a different mouse.

I recently had a Microsoft Wired mouse that kept disconnecting from the USB port and reconnecting right away. I moved it to different USB ports and the same thing happened. I swapped it out for a wireless Logitech M325 mouse and all is well. My wife had her wired mouse suddenly die on her.

[JSWolf]

Originally Posted by therealjoeblow

SOLVED... (I think)

I noticed when using the mouse wheel in the editor to fast-scroll through a document that I got a popup from a program called "HandyAndy.exe" that said that there were several hundred hotkeys detected in the last 1200ms or something like that, and asked did I want to keep monitoring.

I checked what HandyAndy.exe is, it's a component of the Andy Android Emulator, I guess what HandyAndy does is look for mouse movements and translate them into touchscreen emulated gestures for the android emulator to work.

I task-killed HandyAndy and all seems to work fine in Calibre. Funny thing is that this does NOT affect anything else and never seemed to affect Calibre v1.xx either, only started when I upgraded to v2 this week.

Anyway, sorry for the false alarm, looks like my problem is solved.

Thanks
-TRJB

Seems HandyAndy and Qt5 just don't get along together which is why it worked with Calibre 1.x as Calibre 1.x used Qt4.

[mirzok]

Hi all,

I have been having the exact same issue as TRJB has described since upgrading to 2.7. Killing Handy Andy solved the problem for me as well!

Thank you all!