1. Huh, if the bug has been there all along, and I have just noticed it (and it corrected itself), then it's not a priority. Nobody else complained.
2. Here is what I mean. In zten variant (or zdict), when you perform search, you see a search results window on the left and the entry window on the right. If you press the right arrow key (on your joystick), then the entry window maximizes almost fullscreen to take over the space from the results window (the left button does the same but for the search results window). If you press the OK button it also switches the views. In zdict there is an icon for the same function (the OK key also works but not as well as in ztenv).
This option could make the examples window even more useful. Currently, if there is lots of text in there it's hard to scroll up and down and we can only see two or three lines of text at a time. With that option we could maximize the window (it would take over the Entry Word and Translation Word windows to examine the examples/comments window by using the joystick and then return back to the regular view.
By the way, what is the limit for the examples/comments field? I presume there must be some sort of limit, right?
Hm. I have not asked for images and sounds thinking that it would complicate the program but I see that Frederic is actually thinking about it:
The idea to add images (and why not, sounds) is good. Thanks! It's not my priority but I may implement it eventually.
Maybe do that when implementing support for images/sounds as packaging will be needed.
This will open some new opportunities. For me, I will be able to insert stroke order charts in the example window (that's when we will need an option to maximize the example/comment window. However, it would complicate the simple file format for the study lists (I presume xml would include links and images/sounds would be kept in a container file separately.
Once's this is all done there will be nothing else left but to add a search functionality to make it a dictionary in itself
Here are some ideas from my brainstorming:
1. the tomotko could keep track of the progress (number of errors for each word) for each session;
2. based on this progress report, the user could have tomotko unselect all the words with 0 (or 1, 2 ... set by the user) errors, and run the test again only with cards that have generated 1 (or 2, 3, ...) errors. Alternatively, the tomotko could automatically create a new study lists containing words with 1 (or 2, 3, 4...) errors.