[ACK] 4.0c Beta 1: Report typo dialog box doesn't stay up if you Alt+Tab away from Logos and then Al

Select a word that has a typo in it (for example, search for haiti in Nicene and Post-Nicene Fathers, First Series; it should be "had").

Type in what you think the correction should be.

Alt+Tab away to Web browser (I was going to copy the URL and cite page number from Google Books where I found the correct word).

Alt+Tab back to Logos.

The dialog box has disappeared and you have to bring it up again, which is a pain because it's a long wait for the right-click menu to be populated enough for Report typo to show up at the bottom left. [:(]

Find more posts tagged with

Comments

Melissa Snyder

This is by design, to avoid making it a modal window, which would retain the focus so you couldn't interact with the rest of the program until it's closed.

NB.Mick

https://community.logos.com/discussion/comment/109789#Comment_109789

This is a longstanding bug (to be honest, I hadn't even known about something like Logos when Rosie reported this back in 2010). It is still unchanged in 6.3 Beta 3 and it 'bugs' me everytime I want to report a typo that requires copy&paste of anything, such as the correct spelling or context in the explanation field.

This is by design, to avoid making it a modal window, which would retain the focus so you couldn't interact with the rest of the program until it's closed.

I know I've read that before and thought it was an explanation, but it isn't. If I understand Melissa correctly, the design for this box was explicitly made so we could interact with the program. This at first sounds like great thinking, since I might whish to copy the correct spelling from another place when reporting a typo:

However, the implementation doesn't match: the moment I switch focus away from the report typo box, e.g. to NA 27 here, the box vanishes. Therefore I need to:

go to the other resource first, copy the to-be text, go back to the erroneous word, select it, right click, scroll until Report Typo becomes visible, click - now I can paste it in.

So, in this case, the design goal of interacting with the rest of the program might have helped (if implemented). However normally it is not as necesssary as with the rest of my PC - in this case I'd rather have copy-pasted a link to the thread where representation of Greek kappa is discussed as a systemic error in the resource. Okay, this works just as above: abort the typo report (which is easy, just go anywhere else on the screen),

go to the browser tab with the discussion, copy the URL, go back to Logos, go to the erroneous word, select it, right click, scroll until Report Typo becomes visible, click - now I can paste it in.

I can give even a slightly longer explanation - but wait, there's nothing in the to-be box. Just copy from NA27 - stop. If I act too fast on this thought, the report typo box with all the explanation is gone. Hm, I might just exchange chi with kappa - I can type Greek, just need to switch the keyboard from current language layout to DE to EL - focus lost again. Whoa, so:

go and change keyboard layout to EL (for the Greek kappa later). Go to the browser tab with the discussion, copy the URL, go back to Logos, go to the erroneous word, select it, right click, scroll until Report Typo becomes visible, click - now I can paste it in.

I can even fill in the to-be box - but can't give the explanation this time, after all, my keyboard is still in Greek. But somehow, reporting a typo has become more of a nuisance than the typo itself. @Eli Evans, help!

Some ideas for a better design:

I'd rather have a keyboard shortcut to bring it up in addation to the right click menu
The position in the right-click menu is too far down, it needs to be visible without scrolling
The "box" needs to be persistent and not go away, destroying my information
But why a box? Since Faithlife likes these smaller tabs that facilitate lots of things (mostly by use of an in-built browser), why not have a UI like Community Notes/Ask the author -

then the typo would be linked to the word just as fine
I can write up the typo report with to-be line and as much info I like to give (or leave it out) before sending it
even see which typos I already reported,
can potentially someday edit my typo report and re-send, e.g. if I come up on additional information
even delete it when I find I was wrong and reported e.g. an unusual spelling that was in the resource.
In this case, there would be a menu item "open Report Typo" and we would save this line completey from the overcrowded lefthand-side of the right-click menu (I'd still like a keyboard shortcut, though)

Such a typo reporter could perhaps someday queue sent reports when people are working offline and just sync them when connectivity is restored

Dave Hooton

https://community.logos.com/discussion/comment/720378#Comment_720378

Any comment from Faithlife?

Thomas Ball

https://community.logos.com/discussion/comment/725553#Comment_725553

Any comment from Faithlife?

I'll report this and see what happens. :-)

Dave Hooton

https://community.logos.com/discussion/comment/726076#Comment_726076

Bump - FL

Thomas Ball

https://community.logos.com/discussion/comment/729291#Comment_729291

Bump - FL

It looks like this should be fixed in 6.3.

NB.Mick

https://community.logos.com/discussion/comment/729795#Comment_729795

It looks like this should be fixed in 6.3.

in SR1 ? or was this (how fittingly) mistyped for 6.4?

At least I'm not seeing a change to how it behaved since 4.0c Beta 1.

Thomas Ball

https://community.logos.com/discussion/comment/729842#Comment_729842

in SR1 ? or was this (how fittingly) mistyped for 6.4?

Oops. I was looking at the wrong Report Typo bug. The one that is fixed was regarding a crash when opening up the Report Typo menu a second time on Mac. Sorry for the false hope. Ryan was able to replicate the behavior (as I was) so there is hope yet.

Eli Evans (Logos)

https://community.logos.com/discussion/comment/729849#Comment_729849

There's still an open ticket for the original bug, not yet resolved.