Bug cleanup

As I hope you've seen, during the last year, we've been focusing quite a lot on bugs. For an upcoming release, we're considering focusing our bug fixes on one particular feature or area of the app. But what should that be? Is there one feature or aspect of Logos that you think is especially buggy and deserves our attention? Or should we continue fixing bugs more generally?

(Please don't post individual bugs here! We're very much looking for areas to focus on rather than individual bugs to move up the priority list.)

Find more posts tagged with

Comments

MJ. Smith

I'm torn as I don't know the bugginess of the various functions. But judging from the forums, I suspect that either print/export or the resource panel is the best place to focus your resources.

NB.Mick

https://community.logos.com/discussion/comment/1272533#Comment_1272533

print/export

Yes, this seems to be a largely neglected, buggy area of the software. Many users who need to either go on using Logos results in other applications (like word processors, presentation software) or want to have a non-electronic version of their stuff in hand - in a study group, pulpit for archiving or as a backup in case the device/connectivity fails - need to rely on this and it often fails due to bugs.

Bootjack

https://community.logos.com/discussion/comment/1272547#Comment_1272547

You know about this particular thread and problem, seen here...

Logos Version 28 is significantly slower than V.27 - Logos Forums

Is it true the fix only comes out on a six week cycle or can we expect something quicker?

Joseph Turner

https://community.logos.com/discussion/comment/1272556#Comment_1272556

You know about this particular thread and problem, seen here...

Logos Version 28 is significantly slower than V.27 - Logos Forums

Is it true the fix only comes out on a six week cycle or can we expect something quicker?

This is by far my biggest frustration right now.

Pitrell

The atlas is not (meaningfully) usable on Windows due to its severely limited performance. It works blazing fast on the Mac and in Logos Web but not on Windows Desktop.

The issue has been described here and seems to have been hanging in the loop for a long time:
https://community.logos.com/forums/p/217405/1265966.aspx

Bill

Priorities should change depending on the bug. Sometime a fix in one tool or feature creates a bug in something else.

Crash/freeze issues should always be #1
Overall performance issues- speed- usability #2
Prioritize the tools and features for those who use them to make their living, assuming you have that data-Clergy,etc. #3
Focus on issues in tools and features frequently used by everyone #4

Beyond that:

Speed
Print/Export
Sermon Builder
Visual Filters (disappearing)

Dave Hooton

https://community.logos.com/discussion/comment/1272556#Comment_1272556

You know about this particular thread and problem, seen here...

Logos Version 28 is significantly slower than V.27 - Logos Forums

Is it true the fix only comes out on a six week cycle ...?

No. See my response here.

scooter

https://community.logos.com/discussion/comment/1272574#Comment_1272574

Prioritize the tools and features for those who use them to make their living,

I am not comfortable with this. I pay for Logos, too, even though I make no living from it's fruit.

I study from the app, multiple hours a day. My concerns are just as valid, as I am doing my part to make my life better studying the works I have purchased herein.

We are all at the front of the line, Bill. Which means there is no line.

Bill

https://community.logos.com/discussion/comment/1272727#Comment_1272727

I am not comfortable with this. I pay for Logos, too, even though I make no living from it's fruit.

Hi scooter.

I apologize that my statement made you uncomfortable. I may have stated it incorrectly by giving an emphasis on monetary living value.

Like you I too use Logos daily multiple hours, and mostly for personal study, although I do lead a small group study on a weekly basis.

I simply meant, as I see on the forums, pastors and others who preach and teach groups and congregations caught in a bug at the last minute before having to perform their services for the Lord and others, whether paid or not.

As far as my suggested priorities between #3 and #4 are concerned, If we think about it the tool and feature use margin is probably pretty slim between the two and likely both would see the same attention anyway.

scooter

https://community.logos.com/discussion/comment/1272772#Comment_1272772

I am not comfortable with this. I pay for Logos, too, even though I make no living from it's fruit.

Hi scooter.

I apologize that my statement made you uncomfortable. I may have stated it incorrectly by giving an emphasis on monetary living value.

Like you I too use Logos daily multiple hours, and mostly for personal study, although I do lead a small group study on a weekly basis.

I simply meant, as I see on the forums, pastors and others who preach and teach groups and congregations caught in a bug at the last minute before having to perform their services for the Lord and others, whether paid or not.

As far as my suggested priorities between #3 and #4 are concerned, If we think about it the tool and feature use margin is probably pretty slim between the two and likely both would see the same attention anyway.

Bill, thank you for your apology. It is certainly accepted!

Those that use Logos in their Christian duties should be able to have confidence it works. And so should all who use it.

All the best re your Bible study over the coming months.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1272556#Comment_1272556

You know about this particular thread and problem, seen here...

Logos Version 28 is significantly slower than V.27 - Logos Forums

Is it true the fix only comes out on a six week cycle or can we expect something quicker?

A fix is available now: https://community.logos.com/forums/t/218550.aspx

Bootjack

https://community.logos.com/discussion/comment/1272785#Comment_1272785

Thank you Bradley. All seems to be operating within normal parameters!

Jack Caviness

https://community.logos.com/discussion/comment/1272574#Comment_1272574

Crash/freeze issues should always be #1

YES! YES! YES!