BUG: Highlighting Image Coloring Not Displaying Properly
When I create a new highlight in L6 I cannot get the actual highlights image to match the color displayed in the "Highlighting" tool menu. Please see the steps I am using to create the highlight and the screenshot below.
Step 1: Create a new highlighting style called "Command"
Step 2: Use "Click to choose" image sector from the "Image" drop menu to attach PNG image downloaded from www.thenounproject.com
Step 3: Use "Image Color" selector from the "Image" drop menu to select a bright red color
Note: The highlighting tool created a bright red image.
Step 4: After saving the highlight stye, apply new highlight to Biblical text.
Note: The applied highlight appears as a faded red image.
Comments
-
A follow-up question:
Is it normal (and intended) behavior for the image from the highlight to display twice as shown in the screenshot above?
0 -
Jonathan said:
A follow-up question:
Is it normal (and intended) behavior for the image from the highlight to display twice as shown in the screenshot above?
Yes, that is the normal/intended behavior. I personally don't think it's the most helpful/visually-pleasing; however, improvements in this particular area will likely not occur in the very immediate future as it would require significant behind-the-scenes changes.
As for your original issue, we can reproduce it and I've created a case to investigate. I'll post back here with any updates. Thanks!
0 -
Chris Culy (Faithlife) said:
we can reproduce it and I've created a case to investigate.
Additional datapoint: see this thread https://community.logos.com/forums/p/94015/652891.aspx#652891
Have joy in the Lord!
0 -
Chris Culy (Faithlife) said:
As for your original issue, we can reproduce it and I've created a case to investigate. I'll post back here with any updates. Thanks!
This has been fixed in 6.0b Beta 1.
0 -
Angela Murashov said:Chris Culy (Faithlife) said:
As for your original issue, we can reproduce it and I've created a case to investigate. I'll post back here with any updates. Thanks!
This has been fixed in 6.0b Beta 1.
6.0b is now shipping to stable users.
0
