Unable to edit index entry

[jsbien]

It is impossible to move cursor to the edit field.

This and #144 observed on a single computer with Debian wheeze. djview4poliqarp has been compiled several month ago and then workd OK, but the system has been updated, so the culprit seems to be a library.

[Michał Rudolf]

Does it happen every time? What is Qt version there?

[jsbien]

Looks like it happens now all the time (but when the entry is being created the field can be edited). Problem reproduced on another computer:

-- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64)

Kernel: Linux 3.12-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

Versions of packages djview4poliqarp depends on: ii libc6 2.17-97 ii libdjvulibre21 3.5.25.4-3 ii libgcc1 1:4.8.2-16 ii libgl1-mesa-glx [libgl1] 9.2.2-1 ii libqt4-network 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-opengl 4:4.8.5+git209-g718fae5+dfsg-1 ii libqt4-xml 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtcore4 4:4.8.5+git209-g718fae5+dfsg-1 ii libqtgui4 4:4.8.5+git209-g718fae5+dfsg-1 ii libstdc++6 4.8.2-16

[jsbien]

Reproduced on my home computer. This is probably an old problem which simply was not noticed earlier.

[jsbien]

Have you tried to reproduce the problem?

[jsbien]

I enclose a sample index, which cannot be edited. Perhaps the culprit is e.g. a strange character in the initial file?

[Michał Rudolf]

I will have a look this week.

[jsbien]

Perhaps it's a feature, not a bug? The entry is the key field in the database, so it cannot be edited simply as a text field?

[jsbien]

Duplicate keys are allowed in the index when input from a file, and this is correct, because allows for intuitive handling of homonyms. However creating by hand a record with a duplicate key is impossible, which is inconsistent.

[jsbien]

Moreover any changes made to a duplicate key affects all of them, which make difficult using them for homonyms. I make a separate issue about handling duplicate keys.

[Michał Rudolf]

Rewrite handling of index entries. Closes #145 and #171. Now items are identified by their position in the file, not by the entry itself. Therefore homonyms are possible now. Entries are now fully editable, but for now the sort order won't be updated automatically if the word is edited and alphabetic/atergo order is used.

Please look for regressions as plenty has changed.

→ <<cset dba42b4fa318>>