Dictionary
Dictionary copied to clipboard
Current Dictionary not identified
I use two dictionaries for the same language because some words can only be found in one, others in the other. So I often switch between the two, without knowing which one is currently active.
- The active dictionary is only identified via the flag, which is obviously the same for both dictionaries. (Not counting the info via "About dictionary...")
- In the dictionary list the active dictionary is not highlighted.
- Selecting the active dictionary from the list is not quicker than switching to any other. If it was I'd know that I haven't switched.
I propose to implement any of these (in descending preference):
- fix https://github.com/rdoeffinger/Dictionary/issues/31
- highlight/deactivate/grey out the active dictionary in the dictionary list
- skip the switching process if the active dictionary is selected
- add an info about the current dictionary in the dictionary view
Why don't you just use the flag toggle to see what the other language is?
highlight/deactivate/grey out the active dictionary in the dictionary list
sounds like a very reasonable suggestion though. Even if I know Android little enough that it might be non-trivial to actually implement.
skip the switching process if the active dictionary is selected
I actually don't truly understand the advantage that would have for you?
add an info about the current dictionary in the dictionary view
Didn't come up with a good way for that so far (in particular, not wasting space).
One thing I considered though was to let the dictionary open at a random word instead of at the start by default. I'd think in many cases you'd then see from the translation which language it is, plus you wouldn't each time see the "messy" entries at the start. But I wasn't sure if this is really a good idea or this would maybe just be annoying users, which is probably the major reason I haven't done it yet.
Why don't you just use the flag toggle to see what the other language is?
See my 1st paragraph. My issue is when I use, for example, two English dictionaries. The problem is not to know if it's English or German but which English it is.
skip the switching process if the active dictionary is selected
I actually don't truly understand the advantage that would have for you?
If it behaves like as if tapped return (quick) I'd know that I haven't changed the dictionary. I know which one I just tapped, so I'll tap the other one. If it takes a while to load the dictionary I'll have to look again at the search result, if it's different from what I just saw. Sometimes it's very similar, so I switch back and forth...
My phone is a slow single core, so maybe on modern phones that doesn't even make a difference.
But I wasn't sure if this is really a good idea or this would maybe just be annoying users, which is probably the major reason I haven't done it yet.
Yep, guess so. Please don't.
See my 1st paragraph. My issue is when I use, for example, two English dictionaries. The problem is not to know if it's English or German but which English it is.
Oh, you don't mean a English-to-something and a English-to-something-else, but e.g. the included English dictionary and one you created yourself from a different source. Sorry, I completely misunderstood. The random word thing would be complete nonsense for that of course. I don't like that loading the dictionary is slow though, even if it's an old slow phone, I kind of think it shouldn't be...
Well, you're right given the power in my device (even though a little outdated now) compared to the technology of a decade ago. Actually, the phone is quick enough, but often it's busy with something else. But let's not get started with that rant...
Anyway, it's not like it's taking ages to load a dictionary. Then I wouldn't use the app. But you know, if you routinely and frequently use a device you get quite swift and any second of delay, which is irrelevant for sporadic use, becomes annoying.
Changed in c9012e8abcdbd2d68f348eefe72f7faae979d5d5 so that the button for the active directory is shown pressed in the list. Apart from that, it likely should be possible to improve dictionary load performance. I am mostly surprised since it is not too bad even on the emulator. Possibly the biggest issue I see there is the collation/transliteration loading, which is necessary for the search. That is not handled intelligently and should probably be cached as there is no reason to re-load it when not switching languages.
Nice, thanks!
Well, your emulator runs on a big CPU and doesn't have to handly Whatsapp, Push-E-Mail, Facebook and whatnot along the way. Maybe my Android 4.4 is not really designed to run on single cores.
No need to reload anymore now!