Bug: Least Significant Bug EVER Reported in the History of Logos Bible Software

Well, we all have to excel at something. I'll lay claim to having picked the tiniest nit in the history of Logos Bible Software. [;-)]

If you…

1. Launch Logos Bible Software 5 for Mac

2. Change it to full-screen mode as soon as it is available

3. Click on your daily Bible reading assignment

4. Switch to the main desktop screen context while Logos continues loading the passage in its own full-screen context

…then you'll know when Logos is finished, even while it is on the other full-screen, because Logos will draw the little yellow star flare animation in the proper location but on the wrong screen.

Now, can you imagine how much better the software will be for future generations because of my careful work on this matter?!

Find more posts tagged with

Comments

Rosie Perera

Hee hee, what a great way to make your entrance onto the forums. Welcome! (Or are you just coming back again with a new email address? I don't recognize your name as a forum regular.)

Bart Barber

https://community.logos.com/discussion/comment/521128#Comment_521128

I'm a genuine n00b. Thanks for the welcome!

Lee

https://community.logos.com/discussion/comment/521135#Comment_521135

n00b?

Sometimes systems and institutions need guys like you to spot problems everybody missed.

JT (alabama24)

https://community.logos.com/discussion/comment/521145#Comment_521145

n00b?

A "newbie" or a "beginner in the forums."

Lee

https://community.logos.com/discussion/comment/521147#Comment_521147

Knew that already! [:)] Hence, my previous post.

JT (alabama24)

https://community.logos.com/discussion/comment/521193#Comment_521193

Gotcha. [:)]

Bart Barber

https://community.logos.com/discussion/comment/521145#Comment_521145

Thanks, Lee!

Doc B

https://community.logos.com/discussion/comment/521135#Comment_521135

I'm a genuine n00b. Thanks for the welcome!

I think I recognize your name from the blogosphere, unless there are multiple Bart Barbers out there.

In any case, welcome to the forums.

Bart Barber

https://community.logos.com/discussion/comment/521510#Comment_521510

That's me, Doc. Thanks for the welcome.

Tonya J Ross

Well, we all have to excel at something. I'll lay claim to having picked the tiniest nit in the history of Logos Bible Software. [;-)]

I actually reported this issue to Development a few months ago. [:)] Although, I found it by having the app reading aloud while I was on a different desktop.

I'll add a link to this thread to the case though so you can still get some of the credit. [;)]

Lee

https://community.logos.com/discussion/comment/522523#Comment_522523

My interest is piqued. Why does it take a few months to fix a focus bug like this?

Doc B

https://community.logos.com/discussion/comment/522639#Comment_522639

Why does it take a few months to fix a focus bug like this?

I don't work for Logos and I can answer that one. Priorities. When you have less manpower than there is work to be done, you squash the big bugs first.

For a company like Logos to pay attention to little problems like this brought forth by a small customer, even when it takes a few months, is pretty impressive in the world of when-I-want-your-opinion-I'll-give-it-to-you corporations.

Lee

https://community.logos.com/discussion/comment/522665#Comment_522665

For a company like Logos to pay attention to little problems like this brought forth by a small customer, even when it takes a few months...

Not to put too fine a point on it, but it was discovered internally, and it shouldn't be too much trouble to fix. And, left unfixed, who knows what kind of knock-on consequences it could have...

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/522876#Comment_522876

I highly recommend the following article: My life as a Code Economist (http://www.ericsink.com/articles/Four_Questions.html)

This is a low-severity, low-frequency bug. I don't know the cost of fixing it, but I'm going to guess it's non-trivial (otherwise, it probably wouldn't occur in the first place).

You could make a list of dozens (maybe hundreds?) of bugs like this that would go unnoticed if you blinked while it was happening. (AFAIK, this is the second report of this bug in the history of Logos 4/5, and it's probably been a bug since Lion was introduced.) Instead of chasing down every single one of these kind of bugs, we invest the money you spend (on book purchases) fixing high-priority bugs and implementing new features that benefit all our customers.

Milford Charles Murray

https://community.logos.com/discussion/comment/522925#Comment_522925

Peace, Bradley! *smile* Thank you! Well-written indeed! And thanks much for that great link ... .... will be smiling a few times today as I reflect on some of the concepts you've shared with us ...

Lee

https://community.logos.com/discussion/comment/522925#Comment_522925

This is a low-severity, low-frequency bug.

I mostly agree with you there. There's just a tiny possibility that it could have some nasty knock-on consequences later.

I don't know the cost of fixing it, but I'm going to guess it's non-trivial (otherwise, it probably wouldn't occur in the first place).

I don't follow the logic of that. Sounds circular.

Thanks for the reply, though.

Bart Barber

https://community.logos.com/discussion/comment/521510#Comment_521510

I failed to ask before, Doc, but since you know me from the blogosphere, do I know you? (You've got to admit, "Doc B" is a bit less descriptive ;-) )

JT (alabama24)

https://community.logos.com/discussion/comment/523173#Comment_523173

I don't know the cost of fixing it, but I'm going to guess it's non-trivial (otherwise, it probably wouldn't occur in the first place).

I don't follow the logic of that. Sounds circular.

He means that the fix would be expensive or difficult or potentially problematic, i.e. "non-trivial." (It took me a couple of reads as well [:)])

Lee

https://community.logos.com/discussion/comment/523185#Comment_523185

Yes, he means:
1. The cost of fixing it must be non-trivial.
2. If the cost of fixing were trivial, you wouldn't see such a bug...

I've heard better! [:D]

Doc B

https://community.logos.com/discussion/comment/523178#Comment_523178

since you know me from the blogosphere, do I know you?

I doubt it. I'm nobody of import. 'Doc B' is what I use when commenting on blogs whose authors I don't know, so you may see that around. (It's a nickname given to me by my students many years ago and has stuck.)

Very few other than my Mom read my blog, so I can still go to Starbucks and not get mobbed. ;-)

Doc B

https://community.logos.com/discussion/comment/523207#Comment_523207

One can usually tell who in a group have managed people and resources in their career and who hasn't.

Milford Charles Murray

https://community.logos.com/discussion/comment/523257#Comment_523257

since you know me from the blogosphere, do I know you?

I doubt it. I'm nobody of import. 'Doc B' is what I use when commenting on blogs whose authors I don't know, so you may see that around. (It's a nickname given to me by my students many years ago and has stuck.)

Very few other than my Mom read my blog, so I can still go to Starbucks and not get mobbed. ;-)

Well, Doc B, *smile* I'd like to read your blog along with your Mom -- at least once! Can one get there from here?

Psalm 29:11

DavidR

https://community.logos.com/discussion/comment/523173#Comment_523173

There's just a tiny possibility that it could have some nasty knock-on consequences later.

And a slightly less tiny possibility that fixing it will break something else. That's the way life is...

Lee

https://community.logos.com/discussion/comment/523258#Comment_523258

One can usually tell who in a group have managed people and resources in their career and who hasn't.

If you're referring to me, no need to get personal. It's snarky, not to mention a rash conclusion.

Just to make this clear for those who can't read: I'm not pushing for this "least significant" bug to be fixed. The only possible knock-on effect is if the loss of focus leads to some kind of broken program call which which is subsequently layered onto the code. Not likely at all.

But a process which does not clean up loose ends when internally discovered, and a process that says "we don't fix bugs that, if they should have been fixed, we would have fixed long ago" that is something that I have encountered before. Sometimes it's liveable, an acceptable compromise, sometimes it leads to a downward spiral.

Who in a group have managed people, etc. etc.

I can instantly spot those in a group has worked in a diverse leadership team before, and those who haven't, but what of it? I've also been wrong before. [:)]

Rosie Perera

https://community.logos.com/discussion/comment/523355#Comment_523355

One can usually tell who in a group have managed people and resources in their career and who hasn't.

If you're referring to me, no need to get personal. It's snarky, not to mention baseless.

I would have taken it as a compliment, even if it was an inaccurate guess, and not assumed snark was intended.

You are easily able to decipher developers' responses as to how hard it would be to fix a bug. I've been in the development world, both as a developer and a manager, and I thought you did a very good job. Then again, I thought Bradley's response was obvious and didn't need to be deciphered, but maybe that's because I was a developer. Evidently someone else didn't get it, and you made it clearer. Fairly simple, Doc's response doesn't seem like it was meant to rub you the wrong way.

Lee

https://community.logos.com/discussion/comment/523356#Comment_523356

Bradley's response was obvious and didn't need to be deciphered.

Yes his comments were clear. I did know what he was getting on about. Just the way he said it could be applied to all bugs that are still open, and have not been fixed for months if not years. Applying that reasoning strictly leads to who knows what.

I did not take Doc B's comment as a compliment. I guess it was because the comment was written as an "aside" rather than a direct remark. In fact I reacted more to the asideness. Direct criticism is always welcome! Direct compliments, even more!

By the way, I have edited my post. I usually do that when I am writing posts that may come across as negative, to refine my expression. If I may trouble you to read it again?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/523355#Comment_523355

a process that says "we don't fix bugs that, if they should have been fixed, we would have fixed long ago"

If that was intended to be a paraphrase of my remarks, it's incorrect.

I was simply guessing (with zero research) that this would be a non-trivial fix (and stated it was a guess). This is not how bugs are normally triaged. (This bug isn't assigned to me; I didn't look it up in the bug database before posting. Sorry for the confusion.)

Lee

https://community.logos.com/discussion/comment/523364#Comment_523364

Point taken. Sorry for having jumped to a "rash conclusion"! [:)]

Doc B

https://community.logos.com/discussion/comment/523270#Comment_523270

Can one get there from here?

www.blogergism.blogspot.com will get you there, I think.

Doc B

https://community.logos.com/discussion/comment/523356#Comment_523356

Thanks for reading me right, Rosie!!

Lee

https://community.logos.com/discussion/comment/523500#Comment_523500

Sorry to you too, for having misread your post. [:)]

Milford Charles Murray

https://community.logos.com/discussion/comment/523498#Comment_523498

Can one get there from here?

www.blogergism.blogspot.com will get you there, I think.

Peace, Brother!

Absolutely loved your Abercrombie and Fitch humour! Thank you, and God Bless you! *smile*

P.S. Edit! As a Lutheran I'm most pleased also to see you reading about Martin Luther! :-)

PPS - Edit! Also, I DID enjoy a pleasant reading of your blog ... lots of good things well-done! .... look forward to visiting again!