This is a long-standing bug in Logos for Mac that should be addressed. Every window in L5.0b RC-1 is closed and has been closed for several minutes, and Logos has been running in the background for almost the entire time. The popup shown in this screenshot cannot be dismissed without opening some Logos resource. Even more irritating is the fact that this popup will overlay any window of any application that is above the Logos screen. It is inexcusable that Logos has failed to address this bug for months.
Enable-and-Submit-Log-Files | Install
Agree with Jack! Irritating and annoying. Please fix.
Agree!
Thought I would revisit this post after using L5 tonight. The experience was annoying to say the least.
Just didn't want to leave me alone. My pet pop-up.
There's also:
I don't have the energy to check which of these still remain, but I would imagine that most do.
Btw, since you're on an RC, wouldn't it be better to post in the Beta forum? It's so much easier to get Logos' attention there. In fact, I'm tempted to update just to get that privilege...
"The Christian way of life isn't so much an assignment to be performed, as a gift to be received." Wilfrid Stinissen
Mac Pro OS 10.9.
fgh:Btw, since you're on an RC, wouldn't it be better to post in the Beta forum? It's so much easier to get Logos' attention there.
Ahh, details... yes, that would be a sensible thing to do. In justification however, this behavior happens in all forms of releases.
fgh:In fact, I'm tempted to update just to get that privilege...
Yes! Please do. The "devs" need all the help they can get.
fgh:Btw, since you're on an RC, wouldn't it be better to post in the Beta forum?
Will do, and link to this thread
Jack Caviness: This is a long-standing bug in Logos for Mac that should be addressed. Every window in L5.0b RC-1 is closed and has been closed for several minutes, and Logos has been running in the background for almost the entire time. The popup shown in this screenshot cannot be dismissed without opening some Logos resource. Even more irritating is the fact that this popup will overlay any window of any application that is above the Logos screen. It is inexcusable that Logos has failed to address this bug for months.
I am able to reproduce this persistent popup, and will report it to Development.
Anon: Thought I would revisit this post after using L5 tonight. The experience was annoying to say the least.
I haven't been able to reproduce this persistent popup. From what I can tell, it looks like the popup came from the collection/resource selection box in your text comparison window. If you have specific reproduction steps, that would be appreciated.
Brisa Calderon:I haven't been able to reproduce this persistent popup.
That is amazing since I cannot escape it.
Brisa Calderon: it looks like the popup came from the collection/resource selection box in your text comparison window
These persistent popups come from practically every popup in L4-L5.
Brisa Calderon:If you have specific reproduction steps, that would be appreciated.
Just selecting a popup works for me, about 25% of the time.
fgh: There's also: Please help: Logos is everywhere! BUG: popups once again BUG: Another repeatable case of popups that don't go away BUG: Yet another lingering popup (clause search) and probably quite a few more
I have responded in the original threads that were not already marked as resolved. Thank you for continuing to point out the persistent popups you encounter, it is helpful in tracking them all down.
Brisa Calderon:Thank you for continuing to point out the persistent popups you encounter, it is helpful in tracking them all down.
Will try to report each one. do you want new threads, or report them here?
Brisa Calderon:I haven't been able to reproduce this persistent popup. From what I can tell, it looks like the popup came from the collection/resource selection box in your text comparison window. If you have specific reproduction steps, that would be appreciated.
Brisa, no specific steps for reproduction of this; however, I agree the pop-up looks to be from text comparison. Main point for this pop-up is that I did not have text comparison open - this just popped up when I moved my cursor over the info panel.
Thanks for checking.
Jack Caviness:Will try to report each one. do you want new threads, or report them here?
New threads make issues easier to keep track of. Also, the links back to the forum in release notes are easier to understand if each issue has its own thread.
This issue was fixed in 5.0b SR-1.
Brisa Calderon:This issue was fixed in 5.0b SR-1.
No, it wasn't:
fgh: Brisa Calderon:This issue was fixed in 5.0b SR-1. No, it wasn't:
I'm having some trouble reproducing this issue. It is possible that you are using a different resource than the original reported persistent popup on this thread, which is why the popup you are seeing isn't fixed.
What were the reproduction steps to generate this persistent popup?
Brisa Calderon:It is possible that you are using a different resource than the original reported persistent popup on this thread
Most likely, since I've actually never noticed this particular persistent popup before. I just saw it today, took a screenshot, and posted it in this thread, which I knew was about parsing popups.
Brisa Calderon:What were the reproduction steps to generate this persistent popup?
All I did was to open SBLGNT and click the circled 'i' to check the Support info for another post. My punishment for trying to be helpful was finding two bugs, this one and the one at http://community.logos.com/forums/p/66246/464883.aspx#464883.
It looks reproducible, because I can reproduce it now.
Btw, I much preferred when the parsing was at the bottom and not in a popup!
Hmm, this is a very persistent popup:
I don't even have the SBLGNT (or any GNT) open any more!
Brisa Calderon:I'm having some trouble reproducing this issue. It is possible that you are using a different resource than the original reported persistent popup on this thread, which is why the popup you are seeing isn't fixed.
Does this mean that every popup has different coding, and that each popup will require a separate fix?