3.2.10 Bug Report / Feedback Thread
- Thread starter mikelove
- Start date
Alexis
状元
Hi Mike,
Would it be possible to have the C-E search toggle (to the right of the search field), only search Mandarin, only search Cantonese, or both? Perhaps CM to only search Mandarin, and CC to only search Cantonese, and C For the existing functionality (both). Only would show up if user also had Cantonese dictionaries installed.
Would it be possible to have the C-E search toggle (to the right of the search field), only search Mandarin, only search Cantonese, or both? Perhaps CM to only search Mandarin, and CC to only search Cantonese, and C For the existing functionality (both). Only would show up if user also had Cantonese dictionaries installed.
Hi,
I noticed earlier in this thread posts about tone colors - are there still known bugs with tone colors and flashcards? Tone colors are not working consistently in the flashcard module, including:
On a side note: after updating to the latest KEY dictionary, I noticed that the definitions for some flashcards were missing/unlinked, and I had to manually relink them. Not really a big deal, though.
I noticed earlier in this thread posts about tone colors - are there still known bugs with tone colors and flashcards? Tone colors are not working consistently in the flashcard module, including:
- Not displaying tone colors when the card is first shown (pinyin is shown).
- Not displaying tone colors after revealing the card answer, or removing the tone color after the answer is revealed.
- Not displaying tone colors for some dictionary entries when cycling through dictionary definitions from the flashcard screen.
On a side note: after updating to the latest KEY dictionary, I noticed that the definitions for some flashcards were missing/unlinked, and I had to manually relink them. Not really a big deal, though.
Sorry I didn't realize you had replied. I will forward a backup of my database separately.
Two minor issues in the flashcards module:
1. I wanted to map my custom card for 一般而論 to a dictionary entry. When I tapped "Convert to dict-based", Pleco suggested to map it to the entry for 多心, apparently because 多心 uses the phrase 一般而論 in its first example sentence. Took me a while to figure out how I got to a completely unrelated card... Maybe the matching algorithm for "Convert to dict-based" should ignore example sentences and just tell me that my dictionaries don't have a card for 一般而論? (A good opportunity to upsell me better dictionaries, too
)
2. Deleting cards via the "card info" screen ("delete card" button at the bottom) from inside a flashcard session results in a white/empty flashcard screen. (At this point I am usually scared to lose data and just cancel the session immediately...) Deleting cards via the dedicated "delete card" button in the flashcard area works and skips ahead to the next card. Deleting a card from inside "card info" should simply do the same.
1. I wanted to map my custom card for 一般而論 to a dictionary entry. When I tapped "Convert to dict-based", Pleco suggested to map it to the entry for 多心, apparently because 多心 uses the phrase 一般而論 in its first example sentence. Took me a while to figure out how I got to a completely unrelated card... Maybe the matching algorithm for "Convert to dict-based" should ignore example sentences and just tell me that my dictionaries don't have a card for 一般而論? (A good opportunity to upsell me better dictionaries, too
)2. Deleting cards via the "card info" screen ("delete card" button at the bottom) from inside a flashcard session results in a white/empty flashcard screen. (At this point I am usually scared to lose data and just cancel the session immediately...) Deleting cards via the dedicated "delete card" button in the flashcard area works and skips ahead to the next card. Deleting a card from inside "card info" should simply do the same.
gr is empty
goldyn chyld
状元
How is 3.2.11 coming about? (Or is it going to be the big update 3.3?)
Looking like it'll be 3.3, or we may even call it 4.0 since the scope of it is pretty massive - I'd say about 2/3 of the known-bugs-that-a-significant-number-of-people-care-about can only be fixed by large changes that demand beta testing, so unless something else pops up in iOS 9.3 (unlikely, we've already got hundreds of people using it happily) or 9.4 or the early iOS 10 betas it's unlikely we'll do another minor update before that.
And while the full feature list is very much subject to change I can say the big tentpoles so far are a flashcard / user dictionary data revamp (as I've alluded to in a few other places - custom "fields" at last, embeddable media, etc) and App Extensions (finally!). Also just added text editing support to our custom text view last week, so it should now be possible to edit large text files in Pleco very quickly and without losing your place.
And while the full feature list is very much subject to change I can say the big tentpoles so far are a flashcard / user dictionary data revamp (as I've alluded to in a few other places - custom "fields" at last, embeddable media, etc) and App Extensions (finally!). Also just added text editing support to our custom text view last week, so it should now be possible to edit large text files in Pleco very quickly and without losing your place.
It's just really hard to do new features incrementally on iOS in an app as complicated as ours - on two different occasions in 2015 we released a minor update with a few feature changes that turned out to introduce a serious bug for some % of our users that they then had to live with for a week because of App Review. So every time we flirt with the idea of releasing a few nice features at a time in monthly updates, the realities of App Store development push us back to these big, heavily-beta-tested releases with the endless waits between them.
On Android, if we screw things up we can have a fix out in a few hours, which is why despite running on pretty much the same version of our cross-platform engine code Android is on version 3.2.26 and iOS is on version 3.2.10, but except when we're doing something Android-specific like Screen Reader we're pretty much stuck following the same schedule so that the two versions maintain file compatibility / (approximate) feature parity / etc.
On Android, if we screw things up we can have a fix out in a few hours, which is why despite running on pretty much the same version of our cross-platform engine code Android is on version 3.2.26 and iOS is on version 3.2.10
, but except when we're doing something Android-specific like Screen Reader we're pretty much stuck following the same schedule so that the two versions maintain file compatibility / (approximate) feature parity / etc.
goldyn chyld
状元
It's just really hard to do new features incrementally on iOS in an app as complicated as ours - on two different occasions in 2015 we released a minor update with a few feature changes that turned out to introduce a serious bug for some % of our users that they then had to live with for a week because of App Review. So every time we flirt with the idea of releasing a few nice features at a time in monthly updates, the realities of App Store development push us back to these big, heavily-beta-tested releases with the endless waits between them.
On Android, if we screw things up we can have a fix out in a few hours, which is why despite running on pretty much the same version of our cross-platform engine code Android is on version 3.2.26 and iOS is on version 3.2.10
Thanks, sounds good Mike.
Is there any way CC-CEDICT could get updated on a more regular basis (say, at least once every 2 months)?
@Shun - yeah, we have to add an alternate indexer for languages where diacritical marks matter - current one is built around English where most of our diacritical marks come from loan words like résumé and tête-à-tête and do not differentiate them from other English words with otherwise identical letters.
@goldyn chyld - we usually do keep up at least that pace for much of the year, it's only when we get deep into a big update like the one we're working on now that the updates tend to get stalled a bit.
We're actually thinking about offering weekly CC-CEDICT (and PLC, and CC-Canto) updates as one of the perks of the new cloud service we're working on.
@goldyn chyld - we usually do keep up at least that pace for much of the year, it's only when we get deep into a big update like the one we're working on now that the updates tend to get stalled a bit.
We're actually thinking about offering weekly CC-CEDICT (and PLC, and CC-Canto) updates as one of the perks of the new cloud service we're working on.