[ACK] BUG: Copy Bible Verse broken
6.4 Beta 3 Mac OS 10.10.3
Attempted to copy 1 John 1:9 from KJV into an open MS Word document. Nothing happened. Attempted to copy and paste, but the clipboard was empty.
Switched source version to NKJV. Logos now pasted the verse from the KJV into the MS Word document.
Could not make it copy to Word again, even with multiple attempts.
Comments
-
Jack Caviness said:
Attempted to copy 1 John 1:9 from KJV into an open MS Word document.
Does It work if Word is not open?
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Jack Caviness said:
Attempted to copy 1 John 1:9 from KJV into an open MS Word document.
Does It work if Word is not open?
No, but it has never worked unless a Word document is already open.
I had not tried CBV in a few weeks, so I do not know when this bug was introduced in the Mac version.
0 -
This is a known issue having to do with Yosemite. You should still be able to do a Command+V into Word or right click and paste.
0 -
Steve Workman said:
This is a known issue having to do with Yosemite.
Then, when can we expect a fix?
Steve Workman said:You should still be able to do a Command+V into Word or right click and paste.
Only if I first do a Cmd-C in Logos. As I stated in the OP, the clipboard was empty. The tool is very dead.
0 -
That's strange, I'm able to copy to the clipboard using the Copy Bible Verses tool. I tested this on 10.10 Stable and Beta versions of Logos 6.
Since I can't reproduce your exact behavior, would you please provide some logs of this?
0 -
Steve Workman said:
That's strange, I'm able to copy to the clipboard using the Copy Bible Verses tool. I tested this on 10.10 Stable and Beta versions of Logos 6.
Well, it copied normally this morning. Don't know why it did not work previously. If it happens again, I will post logs.
Can we expect a fix for the real problem in the near future?
0 -
Jack Caviness said:
Can we expect a fix for the real problem in the near future?
It seems the root issue is with Apple's API in Yosemite not working correctly; we can't fix that. It seems back in 6.0a Martin was able to improve the behavior a bit, so I'll make a case to see if there's anything more we can do. I wouldn't be surprised if we can't, but we'll check.
0 -
Dylan Rondeau said:Jack Caviness said:
Can we expect a fix for the real problem in the near future?
It seems the root issue is with Apple's API in Yosemite not working correctly; we can't fix that. It seems back in 6.0a Martin was able to improve the behavior a bit, so I'll make a case to see if there's anything more we can do. I wouldn't be surprised if we can't, but we'll check.
Can't say for certain, but if my memory is correct, I have successfully used CBV with Yosemite prior to 6.4—probably in 6.1 or 6.2.
0 -
I know it worked fine before the update. I used it almost every time I used Logos. It was working with word 2016 preview too. After 6.4 it stopped working.
Dr. Kevin Purcell, Director of Missions
Brushy Mountain Baptist Association0 -
Kevin A. Purcell said:
I know it worked fine before the update. I used it almost every time I used Logos. It was working with word 2016 preview too. After 6.4 it stopped working.
Thanks for the confirmation, Kevin. That is what I thought, it did work with Yosemite prior to 6.4. It's not Apple's fault; the fault lies in 6.4.
0 -
Maybe if they are working on CBV they can address this bug too.
0 -
I agree Kevin, I use the copy and paste feature for my sermons all the time. It is my most used feature in sermon prep! After the update, the "copy and paste" button does not work. However, I found that I can still click "copy" then go back to my Word document and click paste. I really hope this problems gets resolved.
0 -
Joey K. Rountree said:
I agree Kevin, I use the copy and paste feature for my sermons all the time. It is my most used feature in sermon prep! After the update, the "copy and paste" button does not work. However, I found that I can still click "copy" then go back to my Word document and click paste. I really hope this problems gets resolved.
I agree too.
0 -
This was broken in 6.4.
We have an active case for this in development and we will update this thread once this issue is fixed.
0 -
Angela Murashov said:
This was broken in 6.4.
[:D]
Angela Murashov said:We have an active case for this in development and we will update this thread once this issue is fixed.
Thank you, Angela
0 -
Angela Murashov said:
This was broken in 6.4.
We have an active case for this in development and we will update this thread once this issue is fixed.
This should be fixed in 6.4 SR-3, which is now available.
0 -
Dylan Rondeau said:Angela Murashov said:
This was broken in 6.4.
We have an active case for this in development and we will update this thread once this issue is fixed.
This should be fixed in 6.4 SR-3, which is now available.
But this is the Beta forum. From another thread, saw that the fix will be in 6.5 Beta 2.
0 -
Jack Caviness said:
But this is the Beta forum. From another thread, saw that the fix will be in 6.5 Beta 2.
[:$] You are correct, my apologies. When replying to threads for the release notes, I tend to get in a groove and sometimes forget to tailor the information to the particular forum.
The fix will be available on the beta channel with 6.5 Beta 2. Sorry for any confusion!
0 -
Dylan Rondeau said:
You are correct, my apologies.Let him who has never made a mistake cast the first stone [;)]
0 -
Dylan Rondeau said:
The fix will be available on the beta channel with 6.5 Beta 2. Sorry for any confusion!
Confirmed fixed with MS Word [Y] [<:o)]
0
