-
I am able to reproduce the issue and will create a case; however, I'm not positive this isn't just a side effect of some of the 'by design' behavior regarding renaming layouts.
-
The title field has been set specifically not to wrap. This brings the Mac platform in parity with the Windows platform. More importantly, this is important for note items correctly syncing to other platforms like iOS and Android.
-
We are working to improve the citation information in Logos, and this is an example of one area that does need improvement. I will create a case for Development for investigation.
-
We're investigating this issue, but so far we haven't been able to reproduce it. It would be helpful to get a screenshot of your Program Settings panel that displays the Accessibility, Fonts, and Notes sections. Do you have your Notes panel set to the default text size using the slider in the panel menu (three ticks from the left)?
-
[quote user="Keep Smiling 4 Jesus :)"]Learned Logos 5.0b Beta 1 on OS X 10.8.2 does not have Sympathetic Highlighting in NA28 and NA27:[/quote] [quote user="Keep Smiling 4 Jesus :)"]Feature parity issue since Logos 5.0b Beta 1 on Windows 7 does have Sympathetic Highlighting in NA27 and NA28[/quote] I'm not able to reproduce this in any version of the
-
[quote user="Dave Hooton"] [quote user="Tonya J Ross"]There's no screenshot from Graham, but yours, fgh, shows that you don't have a resource selected. [/quote] In Windows the preferred bible is automatically listed with a new PL, and the added passages appear in Full view. [/quote] This is the case on Mac as well, though there is a bug which I didn
-
Development wasn't able to glean much about the issue from the logs, and I haven't been able to reproduce it. Please let me know if you see the issue occur again, especially if you come across some reliable repro steps.
-
I've gone back as far as I can and this is always how the Passage List 'Add Versions' has worked, as far as I can tell. When you have no resource selected it does not show the verse text. There's no screenshot from Graham, but yours, fgh, shows that you don't have a resource selected. Are you sure you're not confusing it with the 'Add Versions' hyperlink
-
I'll pass your logs on to Development for investigation. Thanks Rosie!
-
I'll create a case for Development to consider the issue. Thanks Mark.
-
The case for this issue is still active.
-
I'll create a case for this issue.
-
[quote user="fgh"] [quote user="Brisa Davis"] [quote user="fgh"]Furthermore, the boxes need to increase in size when the font does.[/quote] This issue will be fixed in 5.1 Beta 2 for beta users, and in general when 5.1 ships to the stable channel. [/quote] Is this Logos definition of fixed? [/quote] I'll re-report the issue.
-
[quote user="Keep Smiling 4 Jesus :)"] Also can replicate long title truncation using Logos 5.1 Beta 9 on OS X 10.8.3 [/quote] I am also able to reproduce this issue in 5.1. I've created a new case to have the issue examined again.
-
[quote user="Mark Barnes"] [quote user="Tonya J Ross"]I would imagine this has to do with the resource display font not supporting italic small caps (as the 'L' is using a capital letter, not a small cap). This is true of the default font; is that the font you are using? [/quote] Yes, you're right, but Dan's right, too. The italic version of the default
-
I would imagine this has to do with the resource display font not supporting italic small caps (as the 'L' is using a capital letter, not a small cap). This is true of the default font; is that the font you are using?
-
Development is considering implementing a 'Send to Kindle' feature for resources in your Logos library. Before investing a significant amount of time on this item, we would like to assess user interest based on the fact that this feature would not support sending notes/highlights to or receiving notes/highlights from Kindle devices/apps (which is mentioned
-
There is a case for this issue in our system. The resolution for the issue would be to constrain the tag input box to alphanumeric characters -- since 'mytag' is a filter, it has to be a valid search engine query, which won't support symbols -- but since the issue doesn't seem to be very common there hasn't been a move to fix it. I know that this isn
-
[quote user="Jacob Hantla"] We can click "Report Typo" on those missing links but I don't know if that is obvious for all readers (and I'm not sure if it is the most efficient way to report missing links). SUGGESTION: Add a "Report Missing Link" item to the menu under "Report Typo". This would be "Fix Incorrect Link" when a link is inaccurate. This
-
Neither Brisa, Kelly, nor I can recall having seen this behavior recently. I'll pass your logs on to Development to see if they can uncover the issue. Thanks Jack!