You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often when I search for a word, the definition contains another word I don't know and copying the definition and then removing all the parts that are not the word is about at tidious as copying the word letter by letter.
I do see that this is a very small issue, but it would be nice if there was an easy way to look for the definitions of words that are themselves part of a definition.
As an example i wanted to know the definition of "slink". Which came back as "(intransitive) To sneak about furtively." where I didn't know the meaning of "furtively".
I also don't know of any good way to implement this, so feel free to ignore it of you don't either.
The text was updated successfully, but these errors were encountered:
Currently long press of the row opens up share intent. Perhaps this can be changed so that long press causes the text inside meaning box part to be selectable. This way if there is a word not clear users can long press and select the word to select notification dictionary from context menu inside the app like other apps. This feels little longer solution but this is one approach I thought might help in solving this.
Often when I search for a word, the definition contains another word I don't know and copying the definition and then removing all the parts that are not the word is about at tidious as copying the word letter by letter.
I do see that this is a very small issue, but it would be nice if there was an easy way to look for the definitions of words that are themselves part of a definition.
As an example i wanted to know the definition of "slink". Which came back as "(intransitive) To sneak about furtively." where I didn't know the meaning of "furtively".
I also don't know of any good way to implement this, so feel free to ignore it of you don't either.
The text was updated successfully, but these errors were encountered: