-
Does this problem only occur on anchors you've just added, or do you also see it when viewing older anchors/notes? If the latter, would you mind posting your log files?
-
Thanks for the logs and repro steps! I tracked down the problem and will have a fix in the next beta release. The issue is actually with some poor handling of the all-caps styling on "PERSONIFICATION" in your example.
-
Thanks, Petah. I'll look into it. I would also expect to see the tooltip always reflecting the selection.
-
Sorry for the delayed response on this! I have filed a bug and will try to investigate soon.
-
Greg, thanks for the great videos, and for your patience as we iron out some of these kinks. I've filed a bug for fixing panel zoom in notes tool. I agree this is a poor experience now. We're also aware of the reference linking bug, and are working on a fix. The SR-1 release this week included fixes for some of the bugs you reported previously, which
-
Sorry for the trouble, Vincent. We're working on an issue that can cause this when you have multiple copies of the same resource open. Does the problem go away if you close other tabs showing the same resource you're trying to highlight? We're working on this now and hope to have it resolved soon.
-
Thanks for the report. I'll file a bug and try to take a look soon.
-
Thanks for the report, Tim. That's definitely some strange behavior :-) I've filed bugs for both the ctrl+space issue, and the unexpected tagging. I'll try to take a look soon. You should have a "clear formatting" toolbar button at the end that looks like a T with a slash through it. It seems we neglected to attach the keyboard binding.
-
Thanks for the report, David. We have a fix ready that will be included in the next release.
-
Thanks, Tim. Looks like a bug to me. I've created a case to track it and will try to take a look soon.
-
We have a fix for your editor issue ready for the next service release. I'm sorry about the hassle, and I appreciate the bug report & video.
-
Thanks for the report! I'll investigate.
-
Hi, Jim. This is definitely a bug, and we're working on a fix now. Sorry, and thanks for reporting the issue.
-
[quote user="Bryan Smiþ"]If you click on the passage paragraph and increase its indent by one level, the list numbering should resume as expected.[/quote] I've made this change, and it will be included in the next release. Thanks again for the feedback.
-
We intentionally designed the automatic list numbering to be interrupted by non-list paragraphs. Clicking that button automatically inserts a passage paragraph at the same indent level as the paragraph that the reference appeared in. If you click on the passage paragraph and increase its indent by one level, the list numbering should resume as expected
-
Sorry for the slow response on this. Graham, do you get the result you expect when you have fewer bullet points? The content will break onto multiple slides when it won't fit on one. This is different than in Proclaim, where text is scaled down as small as necessary to fit and you are responsible for telling it where to break. We did this because the
-
[quote user="Jon Winkelman"]Also if the sentence is in bold, the fill-in option will not work regardless of wether it is a heading or regular text.[/quote] Thanks for the report, Jon! This will be fixed in the next service release (expected next week). [quote user="Jon Winkelman"]However, I noticed that now when making a "heading 1" the slide that is
-
Thanks for the report, Graham. [quote user="Graham Criddle"]the date on the second one has changed from 20th to 19th.[/quote] It looks like a silly timezone bug. 7.4 beta 4 should include the fix, as well as improved date parsing behavior to support non-US formats. Thanks, Bryan
-
We do (finally) have someone actively working on improving RefTagger. One of the primary goals is to refactor the code to make localization possible, and we do plan to add support for at least Spanish. Unfortunately I don't have a time estimate available, but we'll be sure to post in this forum as soon as we have a working beta ready. Thanks, Bryan
-
Hi John, The blacklist functionality you describe serves a different need. It sounds like what you want is to run reftagger on specific elements in the page instead of on the whole document. You can do this by passing a reference to the element to Logos.ReferenceTagging.tag(). Here's an example that uses jQuery to find all elements with a class of