Visual Copy Will Not Send to PPT after Yosemite update
Hi all. Except for frequent freezing, Visual Copy worked well for me until a few days ago, when Logos insisted I upgrade my Mac to Yosemite. I did so, and It then started up again nicely, except that Visual Copy will no longer send to my PPT for Mac (2011). I can Paste Special, through PPT, as a work around. Anyone else experienced this, or know a solution?
Thanks.
Comments
-
What version of Logos are you running? The was a problem with visual copy and the Yosemite platform early in L6 but it was resolved.
0 -
6.4
0 -
I have not seen anything recently identifying that problem. I am on windows and not mac so I can't really be much help. I try to get one of the mac folks to jump in.
0 -
I am experiencing this problem starting with the 6.4 update. I posted to the Forum with my log file attached.
0 -
Werner Krutzler said:
I am experiencing this problem starting with the 6.4 update. I posted to the Forum with my log file attached.
I looked at you logs and saw where you executed a visual copy request, but I did not see where it failed on the Logos side of the event.
0 -
Given that this error is occurring immediately after the upgrade to Yosemite, it's possible it's on Mac's end. For some reason, ppt is no longer accepting the copy directly from Logos, but one is able to Paste Special inside ppt, and the copy will appear.
0 -
The error for me did not occur after a Mac OS upgrade. For me it occurred on a new MacBook Pro that came with Yosemite. It worked with Logos 6.3 and Yosemte, but not with 6.4. It still works fine with my HP laptop running Windows 8.1 and Logos 6.4.
0 -
Werner Krutzler said:
The error for me did not occur after a Mac OS upgrade. For me it occurred on a new MacBook Pro that came with Yosemite.
Yes, but what version of Yosemite are you running now?
0 -
Bradley said:
except that Visual Copy will no longer send to my PPT for Mac (2011).
This has been fixed internally and will be fixed in the next update.
0 -
Good to hear. Thanks!
0 -
Angela Murashov said:
This has been fixed internally and will be fixed in the next update.
6.4 SR-3 is now available with this fix.
0
