4.0c BUG: Highlighting run amuck
I'm pretty sure this has happened since upgrading to 4.0c RC1/2...but I can't say 100% for sure since I haven't done any inductive highlighting for about a week. I opened my Isaiah inductive layout this morning and discovered huge sections of extra highlighting that I know for sure I didn't put there (nor did anybody else in my household).
99% of the yellow highlighting shouldn't be there...and there are several random sections that look like this:
Comments
-
If it helps, I just discovered something else...the first example doesn't show it (because it is a large area that doesn't show the start or end points) but this one does. It seems that any place this has happened, the indiscriminate highlighting starts and ends with something that is highlighted correctly...so in the following example, "in that day" at both the start and end of the highlighted section should be highlighted with the green outline, but everything between those two instances should not. So it is as if the "tag" or whatever that tells the program to stop highlighting at a certain point has been erased:
0 -
The other book that I've done some highlighting in (Jonah) exhibits the same problem. That inductive layout hasn't even been opened for 3-4 weeks and I know it didn't look like that last time I was in there.
0 -
Had you applied any custom highlighting to that whole section of text, then deleted that custom style?
0 -
Have you tried rebooting the computer?
Dave
===Windows 11 & Android 13
0 -
Ron Keyston Jr said:
If it helps, I just discovered something else...the first example doesn't show it (because it is a large area that doesn't show the start or end points) but this one does. It seems that any place this has happened, the indiscriminate highlighting starts and ends with something that is highlighted correctly
I can reproduce this; thanks very much for this helpful update.
We're going to look into it; the best thing you can do right now is not change/apply/delete any highlighting. At the moment, the highlighting should have the correct data, but is only displayed incorrectly. If we can fix the display bug, the highlighting should be put back to how it was. Changing the highlighting will save the incorrect data back to disk, making the results of this bug permanent (until you manually correct it).
0 -
Melissa Snyder said:
Had you applied any custom highlighting to that whole section of text, then deleted that custom style?
Nope, and it is in multiple places where I'm 100% positive that I've never highlighted whole sections before.
EDIT - I answered this before noticing that Bradley said he could reproduce it.
0 -
Bradley Grainger said:
I can reproduce this; thanks very much for this helpful update.
We're going to look into it; the best thing you can do right now is not change/apply/delete any highlighting. At the moment, the highlighting should have the correct data, but is only displayed incorrectly. If we can fix the display bug, the highlighting should be put back to how it was. Changing the highlighting will save the incorrect data back to disk, making the results of this bug permanent (until you manually correct it).
Perfect! I was worried it would be some bizarre, hard to reproduce issue. I had only "fixed" one small section so far, so I will just leave the rest alone. If I end up having to delete all my highlighting and start over, it will be sad, but not a critical loss of any kind. Thanks for looking into this [:)]
0 -
Ron Keyston Jr said:
Perfect! I was worried it would be some bizarre, hard to reproduce issue. I had only "fixed" one small section so far, so I will just leave the rest alone. If I end up having to delete all my highlighting and start over, it will be sad, but not a critical loss of any kind. Thanks for looking into this
We will release an RC3 to fix this bug.
The problem is just in the display of the highlighted text, so it should be fixed automatically just by upgrading to RC3. However, modifying any highlighting in the resource saves all the highlighting back to disk (not just what you edited), so the problem may already have been made permanent (in this resource).
0 -
Bummer...thanks for the update though.
0 -
RC3 completely fixed the problem, despite the fact that I had fixed the problem in Jonah and done some more highlighting earlier today in Isaiah. Thanks Bradley!
0 -
Ron Keyston Jr said:
RC3 completely fixed the problem, despite the fact that I had fixed the problem in Jonah and done some more highlighting earlier today in Isaiah. Thanks Bradley!
Isn't that wonderful how fast these guys work? Thanks Bradley.
Bohuslav
0
