BUG? Highlighting Labels & Features
The upgrade to Logos 10 has broken my ability to Search across the labels & features I have built for my highlighting palettes.
I have a highlighting palette for the work that I did when my wife and I wrote: Greek Prepositions in the New Testament: A Cognitive-Functional Description for Logos 9.
I use labels and features regularly for annotating the LXX & NT, as well as annotating linguistic data onto texts that are not morph tagged. And I've been working on extending our analysis data for prepositions into the Oxyrhynchus papyri. But now, the following search does nothing:
label.περί:TR/LM:(conceptualDomain:Location)
Related: previously, all my labels and attributes from highlights would show up in the Info pane as other references. Those are now gone.
Labels & attributes in the highlighting palette are the most powerful and useful research tool in Logos and its now completely broken.
I've attached a screenshot with another example from the NT.
I'll be uninstalling Logos 10 and using Logos 9 until this is fixed.
Comments
-
Let's try this screenshot thing again:
0 -
But now, the following search does nothing:
label.περί:TR/LM:(conceptualDomain:Location)
The screenshot only confirms that the label syntax is not correct, so it would help to see the L9 original.
If it is a label you created, the syntax is:
label:(labelName AND conceptualDomain:Location AND ....)
----> not sure what label.περί:TR/LM is
Dave
===Windows 11 & Android 13
0 -
The screenshot only confirms that the label syntax is not correct, so it would help to see the L9 original.
That's why it's a problem. The label syntax in the screenshot that you're saying is wrong was created by Logos 10 via the context menu. I didn't type it.
My desktop, which I just had to repair hasn't yet been updated to Logos 10. I'll see about getting a Logos 9 screen shot from it tomorrow for comparison.
0 -
That's why it's a problem. The label syntax in the screenshot that you're saying is wrong was created by Logos 10 via the context menu.
I see what is going on after doing the same with a label of mine. FL have introduced a new (unknown) syntax for user labels...
With label.περί:TR/LM:(conceptualDomain:Location) ---> the labelName is supposed to be περί:TR/LM but I see it is related to a Palette name (without the colon). Can you provide a screenshot of a highlight in that Palette, showing the Label attributes.
At a guess you could try label."περί TR/LM":(conceptualDomain:Location)
Dave
===Windows 11 & Android 13
0 -
Well, there's nothing to be done, beyond changing all my work so that my labels don't have colons in them.
And since (so far as I know) Faithlife never bothered to build any bulk edit features for labels & attributes anyway, I'm probably going to have redo this data from scratch. For now, I'll just just an installation of Verbum 9 along side Logos 10 while I finish this particular research project and then delete everything and start again. The grunt work of starting from scratch is going simpler than manually editing every entry.
Had Faithlife included me in beta testing (this was the first time in 15 years that I wasn't invited), maybe I wouldn't be in this mess.
0 -
Well, there's nothing to be done, beyond changing all my work so that my labels don't have colons in them.
We'll take a look at this. We don't want to break existing support (especially not for you, Mike!).
0 -
Well, there's nothing to be done, beyond changing all my work so that my labels don't have colons in them.
We'll take a look at this. We don't want to break existing support (especially not for you, Mike!).
Thanks, Mark!
The good news is that I've been frustrated enough with my organization of labels that I was already thinking about changing this.
On face value, the simplest fix might be just adding bulk editing to labels/attributes in Notes.
That'd be a win regardless of the change to search syntax since it'd also make it possible on the fly restructure the datasets that I'm creating—both for myself and for Faithlife in the future. It'd also mean I could just start fresh with better labels on my prepositions projects and then simply bulk edit the old data whenever bulk editing is added.
0 -
Thanks, Mike. We'll want to fix it anyway, as it may also be an issue for others.
The problem occurs when there is a colon in the palette or style name. There will be a forthcoming fix (not sure whether it will be 10.1 or 10.2) whereby complex palette/style names can be wrapped in quotes to ensure they're parsed correctly.
0 -
Appreciate it, Mark!
0 -
Thanks, Mike. We'll want to fix it anyway, as it may also be an issue for others.
The problem occurs when there is a colon in the palette or style name. There will be a forthcoming fix (not sure whether it will be 10.1 or 10.2) whereby complex palette/style names can be wrapped in quotes to ensure they're parsed correctly.
Mark, then I should add: I found a similar bug colon-motivated bug that already existed in L9.
Here is one with the colon:
Here is one without the colon:
0
