BEHOLD!! The SERIF font in the note window produces a SANS SERIF output in the note pop-up!!
BEHOLD!! The SANS SERIF font in the note window produces a SERIF output in the note pop-up!!
This is stupid.
Ever since L9 came out, it has been riddled with inanities and process-breaking gremlins that have put a drastic crimp in my workflows. WHY are these things allowed to continue for years without being resolved?
WHY are these things allowed to continue for years without being resolved?
Limited resources.
The look of text is not considered to be a serious bug by Logos development evidently. "Process-breaking gremlins" and "drastic crimp in my workflows" is a bit of hyperbolic melodrama for a wrong font error of this nature, don't you think? If nobody has reported it before, then they might never have noticed it. And even if it has been reported before, it's obviously not a showstopper.
"Process-breaking gremlins" and "drastic crimp in my workflows" is a bit of hyperbolic melodrama for a wrong font error of this nature, don't you think?
If nobody has reported it before, then they might never have noticed it.
My impression is they get real excited about presentation. Fonts, spacing, amount of white space and so on. But that was when they had a goodly amount of staff pursuing that world. Now, it's getting a bit rough around the edges. Yesterday I noticed a lengthy horizontal scrollbar on a panel, almost black (serious Logosian violation!). The button for multiview is almost indistinguishable (on/off/busy sequence).
OTOH, hebrew is always a Logosian yawner. They never did calm down the sizing, so it doesn't break up the text flow so badly.
Why? Because we users continue to spend our hard earned money on this product regardless of how many bugs it has. I'm very disappointed in Logos and their lack of concern and quality control. There is not a competing product, they know it, this what we get.
Ever since L9 came out, it has been riddled with inanities and process-breaking gremlins that have put a drastic crimp in my workflows. WHY are these things allowed to continue for years without being resolved? The look of text is not considered to be a serious bug by Logos development evidently. "Process-breaking gremlins" and "drastic crimp in my workflows" is a bit of hyperbolic melodrama for a wrong font error of this nature, don't you think? If nobody has reported it before, then they might never have noticed it. And even if it has been reported before, it's obviously not a showstopper.
I would agree with his overall point about Logos 9 though. It has been the single most workflow-disruptive upgrade for me in terms of the impact of the bugs/flaws/changes/inconsistencies (I came in on Logos 6 for context). Logos 9 has caused me to turn off automatic updates for the first time since I've been a Logos user, and I'm normally someone who has automatic updates turned on for pretty much everything else on my computer.
It's sad because I feel like Logos 9 was a bit of a bait and switch because it didn't seem like it was going to be a drastic overhaul the way Logos 8 was. But Logos 9 has literally changed the way I use Logos in numerous ways just because of the various bugs (especially ones relating to scaling and small screens) and how they have changed the toolbar (bolting on more and more buttons).
End of rant.
Hi David,
I was able to reproduce this and I've created a bug report.
Hi David, I was able to reproduce this and I've created a bug report.
[Y]
I understand this frustration, and I'm sorry. We'd love to be able to accommodate everyone's suggested changes. In reality, of course, that's impractical. In the last few months, we have begun a long-term strategy to help us fix more bugs, so we hope that you'll start to see some improvements over the next year or so.
To answer your question specifically, WHY are these things allowed to continue for years without being resolved? I checked our bug tracker, and we've resolved 96 bugs in the last 30 days. So a lot of bugs are getting fixed. But why do some not get fixed, or not get fixed for a long time? It could be one of several reasons. These are not specific to Faithlife/Logos. This would be the case for any software developer.
At the moment, this bug is in category (6).
After reading this, I counted to 10. I was still pissed, so I counted to 100. I was still and even more pissed.
The look of text is not considered to be a serious bug by Logos development evidently.
I read this again and counted to 1000 and then 10,000 (so to speak) and it only got worse, so I just left the pissy-sounding reply I was typing (because I was really pissed) incomplete, and that window is still open in my browser over a week later. Had no idea so many replies had been made to this thread until just now.
Oh, but it has been...and you were there.
And even if it has been reported before, it's obviously not a showstopper.
[It's at this point where I revert to a portion of the comments I resisted posting before...]
{Oh, do many "shows" where you present Hebrew characters, Rosie? I do, and yeah, it kinda is a showstopper. Literally...the show isn't going on, because blocky sans serif Hebrew is simply not easy to read...not for me and not for my audiences. Just wondering...if your notes were all suddenly, out-of-the-blue, presenting in one of those 70s digital fonts or a circus font, would you be okay with that? Would you really feel accepting of FL's months and years-long inattention toward getting things back to normal and just silently think, well, I guess it's really "not a serious bug"? Doubt it.}
But again, is it just this one thing that I'm being overly dramatic about? No, and I've been complaining about it for some time. There's this whole thread. Notes are completely TRASHED. I mean that in the usual sense--they used to have order and a certain (occasionally illogical) dependability, but features that have long (like a decade long) been incorporated just vanished with 9's advent, leaving chaos in their place. As that last link shows, in the desktop app, simply copying the contents of a note and then repasting it below the note results in the complete loss of most formatting. Why???? How???? For a bit of panorama, I'll toss in this issue. But these are just the beginning of sorrows.
As seen below, Logos decided to multiply my notes all on its own. Each of the yellow highlights is a place where Logos doubled the note twice. There are THOUSANDS OF THESE, each of which I have to go through and delete individually. But get this--I ALREADY did that! I literally spent 6 months last year during COVID going from Genesis to Revelation deleting all of the doubled notes and otherwise cleaning them up. I'm talking at least 40 hours a week (probably closer to 80 most weeks) doing nothing but finally getting my thousands of notes straight and clean. Then, presto!, out of the ether thousands of the deleted gremlins just reappeared. But that's not all! As you can see (in green), Logos also decided (for what reason? and how?) to randomly jack up the font size of many of my Hebrew entries to 95 points rather than the 18 points I chose when creating the notes. And then, of course, there is the omnipresent issue that I addressed in the OP (in blue), where the font used in the note window is the exact opposite of what appears in the note pop-up. If I were to change the font in the input window to a sans serif font, that would cause the pop-up to switch to a serif font.
We're just getting started. In the pic below, notice how the presence of a marginal notation number in the text triggers the spelling check highlight. I use my notes for presentations and CANNOT have every single footnote littered with red graffiti. I was told by FL over a year ago that this behavior is indeed a bug and was told a "ticket" was being made to correct the problem...but as you can see, it persists.
Scrolling down just half-a-page in my NASB95, notice that all of the yellow highlighted notes below are part of a file (blue highlight) called Tohraah (2)...A FILE I NEVER CREATED. For some random and bizarre reason, when Logos decided to improvise and double (and triple) my notes, it created this doubled file as well. I have over half-a-dozen such doubled files. I know that there are people who are already prepared to tell me that all I have to do to remove the doubled and tripled notes is to delete this doubled file--but I can't do that. While each of the first two notes in the previous pic (look two above) that shows tripled notes is part of this Tohraah (2) file, if I deleted that file to remove those notes, then I would also erase each of the highlighted notes below, which are single, unique notes. Thus the necessity to edit each of the 20,000+ notes I have individually at a considerable and obscene expense of my time. Also, there are numerous cases of my notes having randomly added spaces (green highlights), which were not present when I originally created my notes. Just going through and fixing this one "innocuous" problem of added spaces would take me weeks of time and effort, even if it were the only issue...which obviously isn't the case.
[Slogging on...] Paging down in my Bible once brings me to this note below ("drew"), which again shows the issue addressed in the OP, where the yellow highlighted text is presented in opposite font styles in the input windows and pop-up windows. But unlike the pic we saw above, where the Hebrew text was boosted to the obnoxious 95 point font size, the text in this note is only 12 points like the text around it, EVEN THOUGH THE FONT SIZE BOX SAYS IT IS ACTUALLY 95 POINTS (sadly, I cut that portion of the pic). Notice the cursor under the pink box--the font box at top said this was 95 point text, which is obviously not the case. But here's the kick in the pants...as I said before, I ALWAYS set the Hebrew text in my notes at 18 points, so that I can see the vowel points clearly. So the yellow entry and the blue text beneath should all be 18 pts, but it appears as 12 pts (the size of the surrounding text) while the font size box insists they are all 95 pts. Ridiculous! And to top it all off, when I cleaned up my notes last year, I deleted all of the unnecessarily duplicated text in the orange box, but miracle or miracles!, here it is, risen from the digital grave.
Okay, so hold on to your hats, because this is going to be freaky as hell. See in the above pic the 4 yellow boxes in front of verse 10? I checked and two were duplicates but one was blank, so I deleted it (yellow highlight below). Then I clicked back on the dark gray note for "drew" and now feast your eyes upon the insane nonsense that magically transpired! Remember I said that the font box that I accidentally cut off the above pic was saying the Hebrew text was 95 pts even though it appeared to be 12 pts? Well, guess what...there's no mystery about the font size now! The text (in blue) is now in full agreement with the font size box (in green). This ridiculous bs is happening in real time!!! The note window above and note window below are the exact same note, and it changed its contents all by itself!! Simply deleting a completely unassociated note changed the visible size of the text in this note!
This is out of control. What I've shown here is just a drop in the bucket. Just to be clear, I picked a point in my Bible at random and found all of these example in just two chapters. NOTES ARE DRASTICALLY BROKEN AND THEY NEED TO BE FIXED YESTERDAY.
I'M 100% SERIOUS ABOUT THIS...FAITHLIFE NEEDS TO HIT THE KILLSWITCH ON ALL ITS ACTIVITIES AND RESOLVE THIS FUNDAMENTAL USER EXPERIENCE AND WORKFLOW ISSUE NOW.
If all caps is shouting, is this beyond the decibel level safe for human ears? Seriously, you are absolutely right iff (not a typo) the behavior is representative. However, while I know how I can make Logos duplicate notes, I have never had it happen spontaneously; I have never had it create a file spontaneously ... and I'm not certain I could trick it into it. The font problem can be replicated.
To sort out what happened would be a big hassle, but the place to start would be for you to provide the following information:
Provide screen shots providing this information and I can determine what the next step in debugging will be.
I know where to find the creation/update data in L3, but not in L9. Where is it located?
In default view for center column:
While I gather MJ's requested info, here's another massive headache-inducing issue. The pic below is from the desktop app. Note each of the yellow highlighted sections and specifically notice the color sequence of the notes.
Compare those color sequences to the same passage on my tablet app.
Notice how the color sequences are all different in the corresponding sections. THIS IS A PROBLEM...because when I created these notes, they were meant to be reviewed in order, often with second and third notes building on info presented in the first note. For years, this method worked with no problems--although getting them in the correct order did require some juggling (copying and pasting). Now, as you can see, that whole methodology is shot to hell. Not only is it obvious that the sequential order is discombobulated from one app format to the other, but I am no longer certain that I can rely on either one to present the proper sequence. The notes were almost all created in the desktop app, but I also have noticed in the recent and not so recent past that sometimes the order on desktop seems out of whack.
Also, note the green highlight in the top pic--the six notes there are all yellow, but if they were different colors, there is a significant likelihood that there would be a mixed-up order with them, as well.
Obviously, this is a major BUG.
