Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Chris

Pages: 1 ... 10 11 [12] 13 14 ... 16
Stackz - New Feature Requests / Re: Kanjibrowse and EPWING Support
« on: October 08, 2006, 08:14:38 AM »
Thanks for this hint, we'll investigate it!

Stackz - Solved Issues / Re: Kanjibrowze and Japanese Sample Sentences
« on: October 08, 2006, 08:13:44 AM »
This feature is on top of the todo list, we'll come up with a solution for that in the next version.

Stackz - New Feature Requests / Re: Stackz dictionary - direct opening.
« on: October 08, 2006, 08:12:30 AM »
Excellent idea, we'll think about it.

Have you noticed the tray icon? It might accelerate your task with the currently available functions in the meantime, double-clicking on it starts a dictionary search with the clipboard content, a right-button click opens a menu with other options.

Stackz - Solved Issues / Re: The Back button in the Learn dialogue
« on: September 27, 2006, 03:38:08 PM »
1) Entry B is declared as unknown, and stays at #13.

To "declare as unknown" means "re-classify the entry by moving it to a different stack on the left".
If an entry is declared as unknown, it leaves the learn dialog.

An entry can't be declared as unknown and stay in the dialog in the same time. According to my previous post, you probably mean "Entry B stays at #13 and is not allowed to be declared as known anymore".

Stackz - Solved Issues / Re: The Back button in the Learn dialogue
« on: September 27, 2006, 03:10:07 PM »
Ah NOW I see what you mean!  :o Sorry for the misinterpretation.

The undo action takes the focus away from the entry that was inserted during the erroneous declaration action.
This lost focus turns it to a "not allowed to declare as known" state!

Detail description:
On PocketStackz, after an erroneous declaration, the undo action adds the previously declared entry ("A") back to the local stack, without removing the entry that replaced it during the erroneous declaration ("B"). After the undo action, "A" is selected in the list and its attributes are displayed. When the new entry "B" then is selected, the "declare as known" button is disabled for this entry because it is selected for the second time now, and "declare as known" is only permitted at the first selection to avoid positive declarations out of an iterative learning session.

We will try to find a solution to this problem.

In the meantime, the entries that are added before an undo action can't be declared as known in a learning session indeed. They are best put back on the same stack instead, which does not alter their statistics. Note that another session can be started directly afterwards to catch up on classifying the missed entries, a test session would be more appropriate than a learn session in this case.

PalmStackz / Re: Zaurus 3100
« on: September 08, 2006, 06:30:14 PM »
Unfortunately we don't support the Zaurus platform at this point in time, and there is no such plan at the moment.

Stackz - Solved Issues / Re: Larger entry font
« on: September 08, 2006, 06:29:21 PM »
Where do you notice this restriction?
In the normal font definition dialog bigger sizes can be chosen without problem.

Stackz - Solved Issues / Re: The Back button in the Learn dialogue
« on: September 01, 2006, 06:10:20 AM »
Yes, that's the intention of an undo button - but only if you pressed "declare as known" before.

Stackz - Solved Issues / Re: The Back button in the Learn dialogue
« on: August 13, 2006, 12:30:26 AM »
I'm not sure if i understand your concern correctly.

1) There is an undo button, which will undo your last classification.
2) The arrow-up button has the function "put back on same stack".
3) The arrow-left button has the function "declare as unknown".

There is no "back" button that should act like an undo button... I guess you are referring to the arrow-left button, which seems to work exactly as described in the manual.

Stackz - New Feature Requests / Re: Change to mark right/wrong
« on: July 13, 2006, 05:43:30 PM »
The speed does not change if the cards are split into lessons. All cards are updated because this is necessary in some situations, e.g. if you use the FailureCount ColorMode and increase the maximum failure count with your action, then the color of all cards will have to change.

This complete update has never been considered as an issue so far. My biggest file contains 6400 cards and a test action on my 2.5 GHz 512 MB ram PC takes way less than a second - around the time needed to pronounce the word "hop", and I assumed that noone would ever use a file that big in reality...  :)

Speed improvements are certainly possible, the simplest way is the suggested update prevention. More advanced things like partial update only where needed are of course possible as well. The additional complexity and potential error source did simply not seem to be necessary so far. We will investigate this and provide a solution in an upcoming version.

Is it running faster if you hide the main window during testing? You can do so by holding down the ctrl key when opening the test dialog. I'm not sure how the system reacts on your PC since I can't duplicate the slow behavior in the first place, but it might be faster by chance...

KanjiBrowze / Re: Korean Dictionary
« on: June 26, 2006, 06:06:38 AM »
I am not aware of any Korean dictionary in the EDICT format. Maybe another user knows something? Please post it here.

KanjiBrowze is only a dictionary tool, it is not foreseen to create Stackz Wordlists with the standalone tool.

To create Wordlists from a Japanese or Chinese EDICT formatted dictionary, the Kanjibrowze Version that is built in Stackz or the free StackzListEditor must be used.

Stackz - Solved Issues / Re: Lesson maintainance
« on: June 25, 2006, 08:48:58 AM »
Thank you for your idea!

Improved Lesson content management is among the features that will be improved in the next version.

Thank you for reporting that problem.

"not working" - do you mean that there is simply no reaction at all? I am very surprised about that. It has always worked on my PC and there was no problem when I checked this morning and this problem has never been reported in the past.

  • Are you sure that Korean support works properly on your system with other applications?
  • I assume that your "Language Toolbar" is the IME provided by XP (MS-IME 2002) and that it is active during your activities. Is there a difference in behavior with disabled Korean Input? Maybe removing and reinstalling this one helps?
  • Did you change anything in the Stackz font assignment of Korean text? Please try hitting the "Reset Languages" button in the Stackz Language dialog (Menu Options -> Stackz Options) to try reverting to a working configuration.
  • Do you have the chance to try Stackz on a different PC? Maybe there is some other sort of side-effect that only appears with a certain configuration.

Question to the other users: Did anybody experience a similar behavior?

If all fails, please upload a small sample file, maybe it contains some further indication of the problem that I can investigate.

I assume you refer to the "Import entries from file" command which does currently not offer importing from unicode formatted files.

  • You can copy the content to the List Import Wizard, copy/paste of UNICODE is supported.
  • Alternatively, you can convert the file to UTF-8 with any tool or editor, e.g. MS Word before using the import command.

I added the UNICODE import filter to the todo list.

Good to hear that it works!

And yes you are correct that the previous text is not deleted as one would expect it. I will change that for the next release.

Pages: 1 ... 10 11 [12] 13 14 ... 16