bump in hopes of getting a response
Thank you for the feedback, Dave. I will make sure it gets passed along to the team and create cases for some of those issues noted.
Corresponding Text in other books this needs a verb i.e. Show Corresponding Text in other books should it be "from" rather than "in"?
I understand why this change is being made, since a powerful feature was hidden under an ambiguous name. However, this new name is really wordy. The old "Text Selection" option was concise. Now you have to select "Corresponding Text in Other Books" and "Text Selection."
Perhaps "Corresponding Text in Other Books" could be shortened to "Corresponding Text" and "Text Selection" could be shortened to "Selection".
Also, I want to register my complaint about making substantial changes in commands in a minor release version. I do not think it to be a good practice, since it can create confusion. I expect and look for substantial changes in major program releases. But it is apparent that subtle changes could happen in any minor version.I train seminary students to use Logos in several of my courses. A change like this means that I need to revise my handouts and rerecord portions of course videos and change quiz questions. It is definitely going to add confusion in my classes.
Agreed with Harry on this matter. This change could be considered important for some and at the same time it helps uncover a great yet unknown feature. Breaking changes, such as modifications to class names, function names, or argument order, can be introduced by additional minor version upgrades. Minor versions, however, do not have to break changes in order to deprecate or add new functionality. That is what Logos did hear as far as I can tell. Additionally, minor versions keep backward compatibility intact, meaning that programs developed with the last minor version can typically function flawlessly with the current one. The confusion for teachers is the worst part of this change.
Breaking changes, such as modifications to class names, function names, or argument order, can be introduced by additional minor version upgrades. Minor versions, however, do not have to break changes in order to deprecate or add new functionality. That is what Logos did hear as far as I can tell.
I'm not sure what FL 'heard'. My complaint is that they have changed names and the order of commands for no real benefit. Had the Reformat sub-menu remained in the top of the VF menu, the effect of renaming would be minor. Shortening and stretching names does nothing for clarity. And then we all have to make changes to documents we produce for the education of other users.
But your comment on minor versions/major versions is confusing because these changes were introduced in Logos 34.0. The minor versions (if any) are bug/stability fixes e.g. Logos 33.2 BTW, the (Free) Support requirements have undergone a major change since May 21:
why did FL drop the explicit requirement of versions supported by MS?
Because it was thought confusing that an explicit version wasn't listed. It will still align with the versions supported by MS.
My complaint is that they have changed names and the order of commands for no real benefit.
Agreed Dave. That is my complaint as well.
Had the Reformat sub-menu remained in the top of the VF menu, the effect of renaming would be minor. Shortening and stretching names does nothing for clarity. And then we all have to make changes to documents we produce for the education of other users.
This is correct and stubbornly hard to deal with in context.
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
