BUG: Cmd+C sometimes doesn't work (B8)

I've been doing a lot of research and note preparation recently, copying and pasting passages of Scripture from L4 Mac (b8) to OpenOffice. Fairly frequently (I haven't yet established the pattern) I switch to L4, select some text with the mouse and press Cmd+C, switch back to OpenOffice and press Cmd+V and find that the previous text that I copied is still on the clipboard - that is, that the newly selected and "copied" text never got copied to the clipboard. At this point the only thing that seems to work is to switch back to Logos, re-select the text of interest, right-click and select "Copy" from the popup menu... this works but is much slower than using the keyboard.

Find more posts tagged with

Comments

Michael McLane

I have experienced this phenomena as well. At first I thought it was just me and that I had forgotten to copy, but now that I have read your post I realize that it was not operator error. It is happening a little too often for coincident. For me, this is actually good news. Now I know that I am not quite as absent minded as I had thought.

Levi Durfey

https://community.logos.com/discussion/comment/167089#Comment_167089

I am also having this problem. I can't find a pattern for when it works and when it doesn't, so I've pretty much switched to using the right-click and copy method.

Famille Thevoz

This is a bug due (I assume) to incorrect panel focus.

See my analysis and report here :

http://community.logos.com/forums/t/22260.aspx

I hope that it can be fixed until the official release.

Stuart Robertson

https://community.logos.com/discussion/comment/167190#Comment_167190

Might be, but I'm not convinced. Because sometimes I focus a window by clicking in it, using the mouse to select text and then press Cmd+C, and then when I paste into Open Office I find the old text still on the clipboard...

Famille Thevoz

https://community.logos.com/discussion/comment/167196#Comment_167196

Interesting. On my side I had observed that clicking in the panel first, before making the selection, would always lead to Cmd-C properly copying the selection. That this was a proper workaround. Others rely on right-click then copy in menu, which they attributed to the same effect : a click in the resource that properly sets the focus prior to selection.

But if you experience the issue even with taking this extra click, than I agree that the real cause may be something else then panel focus.

Let's see what Logos development team may figure out.

Jack Caviness

https://community.logos.com/discussion/comment/167102#Comment_167102

I am also having this problem. I can't find a pattern for when it works and when it doesn't, so I've pretty much switched to using the right-click and copy method.

FWIW, I have experienced the same thing in L4 Win and adopted the same solution/work around.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/167374#Comment_167374

I am also having this problem. I can't find a pattern for when it works and when it doesn't, so I've pretty much switched to using the right-click and copy method.

FWIW, I have experienced the same thing in L4 Win and adopted the same solution/work around.

If anyone can provide steps for which this problem consistently manifests itself, we would love to have them. I don't think any of the developers have been able to reproduce it.

Famille Thevoz

https://community.logos.com/discussion/comment/167455#Comment_167455

Hi,

I provided steps for the Cmd-C issue here, it's very easy to reproduce :

http://community.logos.com/forums/t/22260.aspx

See other seemingly related issues here :

http://community.logos.com/forums/p/22399/167457.aspx

and here :

http://community.logos.com/forums/t/21974.aspx

Hope this helps to identify and fix this annoying bug.

Many thanks for your great work! :-)

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/167459#Comment_167459

Perfect. Thanks.

Famille Thevoz

https://community.logos.com/discussion/comment/167468#Comment_167468

By the way, did developers notice that timelines are broken in B8 and B9 ?

See : http://community.logos.com/forums/t/22254.aspx

I haven't see any reaction so far.

Michael McLane

https://community.logos.com/discussion/comment/167475#Comment_167475

I believe that they do know.

Tom Philpot (Faithlife)

https://community.logos.com/discussion/comment/167475#Comment_167475

By the way, did developers notice that timelines are broken in B8 and B9 ?

See : http://community.logos.com/forums/t/22254.aspx

I haven't see any reaction so far.

No. We didn't know. Thanks for the reminder. This will be fixed in the next beta.