Tip to use CTL-F to find tags
While we await (hopefully soon) the completion of the tag functionality (the ability to retrieve them through searches), here is one tip that can be used provisionally and to find one-term tags (no complex searches):
Prefix your tags with a tag identifier. For example, instead of using "Christology" as tag, use T-Christology (likewise, T-Moses, T-David, etc). When you want to find corresponding entries, CTL-F accordingly "T-Christology" will find the tags, not the texts where the word Christology might otherwise appear.
It's a band-aid I admit. But there may be others like myself who cannot be waiting indefinitely to see the feature improved and yet need to make use of it. This is one way.
Perhaps there are other (better?) ways.
Comments
-
Pros: make tags findable.
Cons:
- Unless one is prepared to keep special formatting permanently (which may, as it does for me, violate one's sense of neatness), when tags are finally made into what they need to be by Logos, one may want to remove special formatting = more work.
- If one has already tagged without special formatting a lot of entries, then there is the difficult decision: does one go back and retag everything (= a lot of work!) or only new entries.
Conclusion:
- Works best with new projects.
- It remains a less than ideal though workable solution.
- Really what we need is for Logos to do it right!
0 -
A follow-up to my previous posts: now I have done enough of this, it turns out that Logos does not like it one bit. When I use CTL-F to find my T-tags, they are found indeed, but Logos keeps freezing (the not responding message) as I seek to scroll down between clippings.
Sigh...
Just fix it, Logos, quickly, please. I cannot get my work done.
0 -
Logos keeps freezing (the not responding message) as I seek to scroll down between clippings.
You're running Logos on Windows, right? We have a new sampling tool for Windows that can help the developers track down performance bugs; please try it out on this problem:
https://www.logos.com/support/logos6/windows/report-performance
0 -
Now THAT is a good one!
[B]
0 -
Hi Francis, I am the developer who worked on this performance tool. I can't seem to figure out what is going on or reproduce the behavior you are seeing and unfortunately, Microsoft's documentation on their xperf tool (which is what our tool uses under the hood) is not the greatest, particularly when it comes to error -1073blahblahblah
. I would love to be able to help you figure out what is going wrong so we can get the data we need to diagnose the performance issue you are seeing. Do you get this error every time you run the tool? Could you take a screencast from when you launch the tool until you get the error? Lastly, what are your machine's specs and which version of Windows are you running? I'm guessing 64-bit Windows 8.1, but I want to double-check all the details.
Thank you!
0 -
Francis, why not use a standard search rather than a simple string match?
Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."
0 -
Look at the results on the left and what happens on the right when I click on the results link:
What's the point of searching if you don't get a filtered list?
0 -
FYI, I sent a sample to support@logos.com. I could not post the file here. I tried three times and got an error each time. The file must be too large.
0 -
I'm glad you were able to run the tool successfully. I've received your log files including the sampling data and we will take a look at it. Thanks for sending it in!
0 -
Chris, I think we share a BC/SK connection if you see what I mean...
I should explain what the problem in my first attempt to run the sampling tool, so that others will be aware of what not to do and perhaps the tool explanation page can provide a warning about this.
When the tool is run, a script runs in a command window. But it is not clear to the user what is happening and all the more so as the box with the begin and stop sampling command appear before the script is done running in the box. The same thing happens at the end of the process. The command window reopens when one clicks on stop sample but then nothing seems to happen (you just see a blinking cursor in the command window). The first time I ran the tool, I thought it was over and that I needed to close the window. This time around I waited to the end (which does not come instantly).
So this is something others might want to be aware of when using the tool.
0 -
Haha, yes, it appears we do. It's been a long time, but I went to all of high school there and did a year of part-time studies at the college as well (my dad used to teach in the seminary and college).
Thanks for explaining what happened. I will talk to the appropriate people to have the instructions updated accordingly. Thank you!
0 -
If you ask your dad about a Francis who is doing postgraduate studies on John, he'll fill in the blanks for you. Then you can tell him how much of a bad boy I've been on the forums! [;)]
0 -
The instructions should be updated now. My dad hasn't worked there in quite some time, so I'm not sure he would recognize you
0 -
We're friends and remain in touch.
0 -
Ah, I see. I talked to my dad and mentioned you and he says hi.
0
