Page 2 of 3
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Wed Jul 15, 2015 6:44 pm
by Jon
You tell me. I haven't heard of any other problems.
Jon
Sonny Software
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Wed Jul 15, 2015 7:07 pm
by thecritic
Will do.
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Thu Jul 16, 2015 6:01 pm
by swilcox
Another solution is to create a set of Applescript macros using KeyboardMaestro. Assign a hot key trigger and restrict them to work only in Microsoft Word.
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Wed Aug 05, 2015 11:15 am
by alango
I read all the news in this forum "MS Word 2016 Mac" and Bookends - but I really don't understand: What do I have to do, that bookends and Word work together?
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Wed Aug 05, 2015 11:31 am
by Jon
The AppleScripts for Word are in a folder in the Bookends folder (get to it via the Bookends Help menu). You can run them by double clicking on them and running in Script Editor. Or you could run them via apps others have suggested for executing AppleScripts. So, for example, run Scan a Document and Bookends will scan the open Word document.
Once Microsoft has stabilized Word 2016 we'll see what the best way to handle these scripts is.
Jon
Sonny Software
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Tue Sep 15, 2015 10:10 am
by mchapman
This worked just fine for a while.
However, today when I went to scan a document I got the following error:
Error Number: -1728
Microsoft Word got an error: The object you are trying to access does not exist
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Wed Sep 16, 2015 7:34 am
by Jon
That's a Word error, not Bookends. If it was working before, something happened with Word (or your OS). You can reboot the Mac, that can fix AppleEvent issues. If that fails, reinstalling Word might help.
Jon
Sonny Software
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Wed Sep 16, 2015 7:35 am
by Jon
That's a Word error, not Bookends. If it was working before, something happened with Word (or your OS). You can reboot the Mac, that can fix AppleEvent issues. If that fails, reinstalling Word might help.
Jon
Sonny Software
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Wed Sep 16, 2015 8:34 am
by mchapman
Ah, I will restart and see what happens.
Thanks,
Mark
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Fri Sep 18, 2015 12:20 pm
by mchapman
Restart fixed the problem until I did a proofreading scan. Then the problem returned.
I was using Fastscripts but switched to the regular scripts menu. I get the error with Fastscripts. With the Scripts menu nothing happens and no error is provided. Of the five Bookends scripts only scan and unseen don't work. The other three work as per normal.
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Fri Sep 18, 2015 4:17 pm
by Jon
I don't know what that error means. Certainly the type of scan (proofreading or not) is irrelevant here. I'd reboot again if that worked once. AppleEvents can break very easily I've found (it's an OS thing, nothing to do with Bookends).
Jon
Sonny Software
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Fri Sep 18, 2015 5:17 pm
by mchapman
I'll try another restart
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Thu Oct 15, 2015 7:45 am
by uncletoff
Is there anything new around this issue? Apple script works, but it is not very comfy to use. Is there a better solution ahead in order to integrate BE into Word? Chris
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Thu Oct 15, 2015 11:08 am
by Jon
I'm working on it, I think most of the issues are ironed out but it's not there yet. I hope to have this done for the next update.
Jon
Sonny Software
Re: MS Word plugin – will it work with the new 2016 release?
Posted: Thu Oct 15, 2015 11:11 am
by uncletoff
Thanks! This helps. Cheers, Kris