It would be nice to have this bug resolved some time ......
And what is a reasonable time frame for bug resolution, 6 months, 1 year, 2 years, or more......?
I forget... Is this a personal book? Is it a custom highlighting pallet?
Custom highlighting palette.
Here is another example I cooked up in 5 minutes with a random book selected and a completely new custom palette which has one style. This style has an image set to lead the text being highlighted with this style. The image has been selected from the default image pulldown list under edit style options.
As you can see from the test case below this generates a number of text / line formatting errors. Line wrapping, hyphenation etc.
Clarification: the images I refer to in my example are the default Logos images supplied under "right click on a style" Edit ➤Image.
In any case custom or default images make no difference. The result is the same. The formatting errors also occur when leading label text is added to a style with ➤Label Text. See example below (the three arrowed images are from the default Logos image set, the Dove is a custom image).
How to recreate the error:
Edit a highlighting style. Open ➤Image and add any default Logos image to the style. Then highlight text with this style near the right end of any line of text or just resize the window width slowly for the line wrapping errors to appear.
This bug has been reported to Logos in a live hookup with them almost a year ago. In the ensuing discussion the person on the other end of the hookup admitted Logos had been aware of the "problem" for "quite some time".
Personally I am more a shade of "disappointed." There have been genuine "improvements" in Logos4Mac. Stability has improved from a almost every session scenario to a maybe once a week crash. But there are still instances of detached pull-down menus and the application is, in my opinion, hopelessly slow. Screen updates and populating some menu lists can have me looking for the coffee cup and highlighting text is still... well you get the picture.
==on=the=side==
Some one once said bug fixing was not a priority for Logos. This smacks of someone out of touch with the industry but it does seem as though there have been improvements in this regard. Maybe the message is getting through because from personal experience as a programmer many eons ago, bugs and bug fixing make or break companies. Ask anyone who has published apps in the iTunes Store. Buggy apps are avoided like the plague. A close second in the plague category would be useability (attention to detail, consistency, smooth work flows and or smarts which help to reduce the number of steps required in repeated work flows etc.) / speed of execution.
How would you rate Logos4 Mac/Windows on a scale of 1-5 in these two areas alone?
For me, 3 (up from 0.5, 12 months ago) & 1.5 (up from 1, 12 months ago).
It's not rocket science; stable usable apps garner stable reliable customers.
Ugh. [:S]
I think how someone would rate Logos attentiveness to "fixing bugs" would depend upon what "bugs" them most, and what bug fixes they notice being fixed. I am a beta tester for the iOS apps and have generally seen things fixed very quickly. Most of the things that I want "fixed" aren't bugs, but things that aren't designed how I think they should be. And THAT bugs me. [:P]
Yeah design & aesthetics are not the same as stability but they often go hand-in-hand. I.e. Well designed product = good stability. [8-)]
I think how someone would rate Logos attentiveness to "fixing bugs" would depend upon what "bugs" them most, and what bug fixes they notice being fixed. I am a beta tester for the iOS apps and have generally seen things fixed very quickly. Most of the things that I want "fixed" aren't bugs, but things that aren't designed how I think they should be. And THAT bugs me.
Things aren't always so subjective. Ok in my case the "bug" is not a show stopper. On the other hand the fact that Logos4Mac still crashes with monotonous, but thankfully decreasing, regularity is not a good sign of a well designed product. [;)]
.jpg)
.jpg)
.jpg)
