The suggested tags are a nice step in library management. Noticed two things that seem like bugs:
1. The suggested tags do not appear if done from the resource info screen rather that the library panel
2. The suggested tags appear only if a single resource is selected in the library panel. If multiple resources are selected (e.g. a commentary series) no suggestions appear
Logging Tool
Fredc:The suggested tags appear only if a single resource is selected in the library panel. If multiple resources are selected (e.g. a commentary series) no suggestions appear
yep, found the same.
Also, to input a new (or suggested) tag, it has to be confirmed by hitting return, which makes it into this button appearance. I found only by try and error.
The downside of the new way is there's no way to edit an existing tag, it's always delete and input anew.
Running Logos 9 latest (beta) version on Win 10
Fredc: 1. The suggested tags do not appear if done from the resource info screen rather that the library panel
This appears to be a Windows issue. I will make sure a case is written for this.
Fredc:2. The suggested tags appear only if a single resource is selected in the library panel. If multiple resources are selected (e.g. a commentary series) no suggestions appear
I believe there is a case for this; if not, I'll write one.
NB.Mick:Also, to input a new (or suggested) tag, it has to be confirmed by hitting return, which makes it into this button appearance. I found only by try and error.
If I'm reading the spec correctly, this is a bug. I'll make sure there is a case for this.
NB.Mick:The downside of the new way is there's no way to edit an existing tag, it's always delete and input anew.
This seems less than useful; I'll write a case for this.
There a lot of cases floating around for the Library panel at this point (as you might imagine), and tagging improvements are already being worked on for beta 2 so some of these might be fixed already.
Diagnostic Logging
Thanks Tonya. MERRY CHRISTMAS to you and the Logos team.
Item #1 (listed in the original post) seems to have been fixed. However the edit option and existing tag overlap.
Item #2 remains an issue.
The need for a hard return after entering a new tag also remains an issue. In addition to the need for a hard return, there is a significant delay (several seconds) after hitting return.
Bump
Fredc:Item #1 (listed in the original post) seems to have been fixed.
Yes this has been fixed in 5.2a Beta 2. Sorry we forgot to update you about this fix.
Fredc:However the edit option and existing tag overlap.
I can reproduce this on Windows and I will create a case for Development.
Fredc: Item #2 remains an issue. The need for a hard return after entering a new tag also remains an issue. In addition to the need for a hard return, there is a significant delay (several seconds) after hitting return.
There are still active cases for these issue in Development. I will make sure this forum post to the cases so when they are fixed we will update this thread.
Angela Murashov: Fredc: (...) The need for a hard return after entering a new tag also remains an issue. In addition to the need for a hard return, there is a significant delay (several seconds) after hitting return. There are still active cases for these issue in Development. I will make sure this forum post to the cases so when they are fixed we will update this thread.
Fredc: (...) The need for a hard return after entering a new tag also remains an issue. In addition to the need for a hard return, there is a significant delay (several seconds) after hitting return.
(...)
Please clarify in these cases: hitting Return after entering = typing myself a new tag may be considered as [user] "works as expected" and may be considered okay (I share Fredc's sentiment that L5 should recognize the new tag much faster), whereas the need to hit Return after the user selected an existing tag from the drop-down list is the issue.
NB.Mick: the need to hit Return after the user selected an existing tag from the drop-down list is the issue.
Thank you for that clarification I will definitely clarify it in the case as well.
Tonya J Ross: NB.Mick:The downside of the new way is there's no way to edit an existing tag, it's always delete and input anew. This seems less than useful; I'll write a case for this.
You can edit the most recently added tag by pressing Backspace (or on a Mac keyboard, the Delete key to the right of the = key.)
Angela Murashov: Item #2 remains an issue. The need for a hard return after entering a new tag also remains an issue. In addition to the need for a hard return, there is a significant delay (several seconds) after hitting return. ]
Angela Murashov: Item #2 remains an issue. The need for a hard return after entering a new tag also remains an issue. In addition to the need for a hard return, there is a significant delay (several seconds) after hitting return.
This should be fixed in 5.2a Beta 4.
When TAB, ENTER, or semicolon is typed to finish a tag, or when a tag is chosen from the entry helper, it is applied and enclosed in a pod.
Angela Murashov: Fredc:However the edit option and existing tag overlap. I can reproduce this on Windows and I will create a case for Development.
This will be fixed in 5.2a Beta 5.