Logos 4

Maybe it's just me.

However, I do miss the ability to view what is being loaded into Logos 4. I really appreciated this feature in Logos 3. I would highly suggest that this feature (the ability to view and select "optional updates") be reinstated in Logos 4.

Thank you for your time.

ron tillman

Find more posts tagged with

Comments

Dave Hooton

Many will agree about the need to view what is available for download (if Auto download = NO) or what is being/has been downloaded. But Logos have consistently refused to consider any download as optional.

Rosie Perera

https://community.logos.com/discussion/comment/124101#Comment_124101

More specifically, you can put off indefinitely doing any download, and Logos isn't opposed to that. But they do say once you're ready to download, you've got to take all or nothing. They do not plan to reintroduce selective downloading, as it was a support nightmare in the past. However, many users have pointed out that all they want is for Logos to let users know ahead of time what is being updated, not give fine control over what to download. That way users can decide whether it's important to take this download now or whether to wait until a more convenient time. There's a request about this on the UserVoice site if you'd like to vote for it: http://logos.uservoice.com/forums/42823-logos-bible-software-4/suggestions/676089-add-an-info-window-that-tells-you-what-is-being-up

JimTowler

https://community.logos.com/discussion/comment/124103#Comment_124103

Rosie,

Who's "side" are you on? Don't encourage them please ... [:)]

Yes there are many calls here for "What" but there are also many calls for "Choice" of downloads: For reasons of speed, size (think Netbook) or traffic charges.

I noticed the "Logos Speaks" page does the same thing, and seems to favour "reading" of some posts that I feel are unbalanced.

I dont think selective downloads have to be that kind of nightmare. I suggested elsewhere, some might accept having NO access to non-updated resources until they update it, if the engine needs the new version to operate. Of course, Logos should only set that lockout flag if the change was of a critical nature. Not minor metadata, spelling, adding pictures or even Reverse Interlinears.