BUG: Serious font slider malfunction in Library
Can't say it's started well: it only took me seconds to find the first bug in L5... 
As I had forgotten to Close All, L5 happened to open with Library open. A Library which I was almost unable to read. At first I thought the font slider setting had been changed, or the new font was smaller, but, no, no amount of magnification alters any font size but in the Title column:
Please fix this quickly, I kind of need to be able to see what I have in the Library.
Mac Pro (late 2013) OS 12.6.2
Comments
-
Mac or Win?
I cannot reproduce this on Win Logos 5.0a SR-2. I change the Default Text Size in Program Settings to 120% and the text in all the library columns gets larger. Same results if I change Program Scaling instead to 120%. Same results if I drag the font slider in the Library panel menu.
0 -
Mac.
Mac Pro (late 2013) OS 12.6.2
0 -
Bump
Mac Pro (late 2013) OS 12.6.2
0 -
Bump
Mac Pro (late 2013) OS 12.6.2
0 -
Same problem here, the title font is augmented in relation to the fonts of other columns.
0 -
Bump again.
Mac Pro (late 2013) OS 12.6.2
0 -
And again.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:
Bump again.
I guess the Mac developers aren't monitoring the forums lately, or maybe only the beta forum. Try emailing one of them. I think David Mitchell ([redacted; David can be found on https://faithlife.com/logosdocuments/activity]), Tom Philpot (tom.philpot AT you-know-the-rest), Cameron Watters (don't know his Logos email but you can find a couple of his personal email addresses by Googling him) are Mac devs.
0 -
Posted => Feature Parity: Logos 5.0b Beta 1 Library Font Slider on OS X only changes Title font size in Logos Desktop Beta forum.
Keep Smiling [:)]
0 -
Rosie Perera said:
I think David Mitchell ([redacted]), Tom Philpot (tom.philpot AT you-know-the-rest), Cameron Watters (don't know his Logos email but you can find a couple of his personal email addresses by Googling him) are Mac devs.
Noticed Bradley Granger has responded to a number of Logos 5 issues on Mac and PC. Suspect Martin Potter and Tom White are current Mac developers. Cameron Watters has more recently been doing Web site development. David Mitchell has been working on documents.logos.com web site. Tom Philpot focuses on Proclaim.
Keep Smiling [:)]
0 -
Cameron Watters has more recently been doing Web site development. David Mitchell has been working on documents.logos.com web site. Tom Philpot focuses on Proclaim.
Isn't it wonderful that Mac development is such a high priority with Logos? [:@]
0 -
Rosie Perera said:
I guess the Mac developers aren't monitoring the forums lately
You're a bit behind.[:)] It's been a long time since Mac devs regularly showed up on the forums. It's generally Brisa, Ann or Tonya who answer my bug threads. They do a very good job when they show up, but it tends to take a month or so on average before they do. Not that I blame them personally, I presume it's Bob who allocates too little staff for the job. But it's extremely frustrating. I find so many bugs I don't even want to open Logos any more, There's no way I could report even half of them. And what's the sense, when no one seems to have time to even file cases for the I few I report now? And that's just the first step. Then they have to be fixed as well, which probably takes a year on average. My list of active bugs just keeps growing and growing and growing.
Rosie Perera said:Try emailing one of them. I think David Mitchell...
I know David's e-mail. I also know he's explicitly said he doesn't want it on the forums.[;)]
Thanks. Let's hope that gets some more attention than this has.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:Rosie Perera said:
Try emailing one of them. I think David Mitchell...
I know David's e-mail. I also know he's explicitly said he doesn't want it on the forums.
Oops, I didn't realize that. I googled it and Google found it on a Logos forum page, so I figured it was fair game. But I didn't follow through and realize that he'd responded to someone posting it on that thread by requesting it be removed. It's too late for me to edit my post now. I'll have to request that someone else redact it from my post.
0 -
fgh said:
it's Bob who allocates too little staff for the job.
I share your frustration. Some of my bug reports were never acknowledged, first on L4 and now on L5.
0 -
fgh said:Rosie Perera said:
Try emailing one of them. I think David Mitchell...
I know David's e-mail. I also know he's explicitly said he doesn't want it on the forums.
To be clear, I have no objection to being contacted directly when there's something that I can help out with. It's just that my email address is usually attached to a team in forum posts, and I may or may not be working on the same team two years from now when someone runs across the post recommending that they contact me. [:)]
David Mitchell
Development Lead
Faithlife0 -
I'm unable to replicate what you're seeing, fgh, nor have I seen any other customer's have the same issue. It is like the text size slider in the panel menu has been increased greatly, but is only affecting the resource titles. What do you have the panel menu text slider set to, and what do you have your Fonts Text size set to? Does this only happen on launch, and when the library panel was open when you shut down Logos 5? Can you post Logo 5 logs, and the All Messages log from Console recording the behavior?
0 -
Actually, this issue has already been looked at, and should be fixed for beta users in 5.0b Beta 3, and in general when 5.0b ships to the stable channel. [:)]
0 -
-
Tonya J Ross said:
should be fixed for beta users in 5.0b Beta 3
That's good to hear, but why Beta 3 when Beta 2 has not even be released yet?
0 -
Jack Caviness said:Tonya J Ross said:
should be fixed for beta users in 5.0b Beta 3
That's good to hear, but why Beta 3 when Beta 2 has not even be released yet?
That's probably a hint that Beta 2 is coming very soon, and it's too late to put the fix into that.
0 -
Tonya J Ross said:
Actually, this issue has already been looked at, and should be fixed for beta users in 5.0b Beta 3, and in general when 5.0b ships to the stable channel.
I'm very glad to hear that, but I would really have appreciated if you could have informed me/us -- and Tommy! -- a bit earlier that you were aware of the problem. Apart from all the frustration, I just spent an hour or more writing a reply for Tommy -- only to find out just before posting that I had wasted all that time. And it's not the first time either. I have spent many hours writing completely unnecessary replies to Tommy.
Mac Pro (late 2013) OS 12.6.2
0 -
fgh said:Tonya J Ross said:
Actually, this issue has already been looked at, and should be fixed for beta users in 5.0b Beta 3, and in general when 5.0b ships to the stable channel.
I'm very glad to hear that, but I would really have appreciated if you could have informed me/us -- and Tommy! -- a bit earlier that you were aware of the problem. Apart from all the frustration, I just spent an hour or more writing a reply for Tommy -- only to find out just before posting that I had wasted all that time. And it's not the first time either. I have spent many hours writing completely unnecessary replies to Tommy.
Hi fgh,
I'm sorry for your wasted time. I actually talked to Tonya about a this case, and it sounds like she was approached by the developer who fixed the problem you're having.
0 -
Rosie Perera said:Jack Caviness said:Tonya J Ross said:
should be fixed for beta users in 5.0b Beta 3
That's good to hear, but why Beta 3 when Beta 2 has not even be released yet?
That's probably a hint that Beta 2 is coming very soon, and it's too late to put the fix into that.
That was initially the case. We had to pull a new candidate, so the fix for this issue should now be in Beta 2.
Please let us know if this happens again after updating to that build.
0 -
Tonya J Ross said:
Please let us know if this happens again after updating to that build.
Unless I completely misunderstand this problem, it is still present in Beta 2
0 -
Jack Caviness said:Tonya J Ross said:
Please let us know if this happens again after updating to that build.
Unless I completely misunderstand this problem, it is still present in Beta 2
Concur Logos 5.0b Beta 2 on OS X 10.8.2 has font slider adjustment for only the Title in Library so feature parity issue is not (yet) fixed.
Keep Smiling [:)]
0 -
Jack Caviness said:Tonya J Ross said:
Please let us know if this happens again after updating to that build.
Unless I completely misunderstand this problem, it is still present in Beta 2
Concur Logos 5.0b Beta 2 on OS X 10.8.2 has font slider adjustment for only the Title in Library so feature parity issue is not (yet) fixed.
Keep Smiling
I apologize for the confusion. We got our wires crossed somewhere, but the issue really should now be fixed in Beta 3. Please let me know if you see otherwise.
0
said:
