-
Thanks for the replies. There was no product key that came with it. It was an insert in the back of the book. Probably need to contact Logos. I just thought there would be some way to do it without a product key.
-
I found a CD in one of my books that has a library from Libronix on CD. I am using a Mac, so putting the CD in my drive only shows a setup.exe. I found a resources folder and thought about adding them to my Logos 7 Resource folder, but I would expect something more needs to be done. Anyone have experience adding Libronix resources like this (there was
-
I noticed the recent build of Logos 7 addressed the scaling issue and did so effectively. Is there any chance a future build could address this issue. Since the macro seems to address the issue (minus my being able to get it to work with a keystroke), is there the ability for Logos to do something on their side to overcome what appears to be something
-
Thanks Jon...yes. The Macro from Logos is in Normal.dotm...I thought there was a separate step at the end of the instructions to save the Normal.dotm again. This just doesn't make sense why the keystroke thing isn't working...
-
One additional bit of info... I recorded a basic macro myself...created a key stroke for it...it worked. Makes me think there is something with the steps of the Logos one that just isn't jiving with the new builds of Word?
-
Jon, I still can't get it to work. I did misread your steps. You said to not skip the "close document" and "open" new one. I followed those instructions, and it still won't execute a macro based on the keystroke I assigned. It does say on the screen images to "save Normal.dotm". Doesn't it save automatically? If not, how do I "save" Normal.dtm?
-
What you described is what I am trying to achieve. I can run the macro in that existing documents/sermon notes context, but the keystroke will not work. It will only work in that original macro document with the keystroke.
-
Jon - i tried your approach. So, here's the deal: 1. It Works - only when I use the original document with macro and select "Enable Macros" before it opens. 2. It Doesn't Work - if I try to use existing documents (my sermon notes with all the styles and keyboard shortcuts I have built over the past couple years) and then run the macro through the keyboard
-
Very helpful...I'll give that a shot. Thanks!
-
Additional Info - the macro runs great when I manually run it. For some reason, Word will not run it via any combination of keyboard strokes I assign..
-
Philana - thanks so much for putting this together. Unfortunately, I can't get it to work. I have it created as a macro, copied it to the Normal template, assigned Cmd+Option+V (unassigned previously), closed out of Word 2016 (Mac 15.30 build) and opened a new document. Went in to L7 and copied a line from BDAG . Went back to my Word document (after
-
That worked! Thanks so much! Didn't realize the naming of the style was crucial. Apparently it is.
-
I read the Wiki and read through a few threads, but I still am having issues. I created a word document with custom chapter headers as my header that I am creating my TOC in Word from. However, when I build my PBB, the headers and formatting looks great, but Logos doesn't pull in my TOC. Am I missing something?
-
Bradley, There seems to be two different topics being covered by this thread now. My original post was that: 1. Before the recent update build to Mac Word 2016, I could copy a section of anything from Logos 7 (Scripture, commentary, journal, etc...). Then when I pasted into Word, it automatically generated a footnote formatted according to my designated
-
Thanks!
-
Philana, Given the recent build released by Word (15.29.16120401) and your comment that there is an open case, is there any update from Faithlife? I continue to avoid updating Word until either their release notes mention their addressing the issue or Faithlife announcing they have a work around. Thank you!
-
Just saw a new build came out for Word 2016 Mac. Anyone tried this paste issue with the new build?
-
Bless you!
-
Glad you figured it out, Bruce. Has anyone from Faithflife acknowledged the issue? It seems like the issue is on the Microsoft side. However, given Erick's comments, it seems like there could be a coding change on the Faithflife side that could be a workaround. Given there are several Logos users who are experiencing this - and given the fact that I
-
Just restored 15.27 from Time Machine...worked like a charm. Hoping MS returns to this function in future builds.