BUG: No way to recover accidentally deleted passage list

Please can Logos be improved to support (even basic) undo support. I
recently accidentally clicked on the little X to the right of a passage
list row (in the File menu) and deleted it by accident. This was a passage list that I've
added passages to steadily over the course of study through a book that
I've been reading. After one click on the wrong spot my passage list is
gone with no way to retrieve it.

Undo/redo support is a
basic function in any program that allows editing (such as notes,
clippings, passage lists, etc). Each action that manipulates
user-created data should be undoable. If previously deleted things
(passage lists, etc) were stored in a "Trash" or "Recycle Bin" database
table then previously deleted items could be restored even after an
application restart.

Please can such support be added to Logos. I truly think it will greatly improve the user experience.

Find more posts tagged with

Comments

Jack Caviness

I
recently accidentally clicked on the little X to the right of a passage
list row (in the File menu) and deleted it by accident.

Perhaps a change to match the action of L4 Win would prevent such accidental deletions in the future. There deletion of items listed under the File Menu requite a selection from the Right-Click Menu.

Please can Logos be improved to support (even basic) undo support

[Y] Agreed. This has also been a matter of frequent complaint among users of L4 Win, so it is probably a core feature that needs immediate attention.

If previously deleted things
(passage lists, etc) were stored in a "Trash" or "Recycle Bin" database
table

While I agree that basic Undo support is needed, I would not like this feature. When I delete an item, I want it gone. I don't want to be forced to delete it again.

Stuart Robertson

This has also been a matter of frequent complaint among users of L4 Win, so it is probably a core feature that needs immediate attention

What is needed to get Logos to address "a matter of frequent complaint"? There is a symbiotic relationship between Logos and its users that I haven't seen with many other software houses... Logos gets the benefit of a large beta-testing community that catches regressions quickly, provides feedback and suggestions about improvements, etc. All of this ultimately benefits Logos by making a better product. The users also benefit by getting to have a (small) say in features they'd like to see, changes they'd like made, etc. For the most part this works well. I understand the need for Logos to "steer the ship", so to speak, and to combine users' wishes with Logos' long-term direction. I understand that balance is important and that Logos needs to maintain momentum with their vision for the Logos product range. What I fail to understand, however, is why things that are basic to almost every Windows application alive today (such as undo), and which are a "matter of frequent complaint" have to be that - a matter of frequent complaint.

If anyone from Logos reads this post, please (pretty please) can proper (or even basic, for the interim) undo support be added to Logos.

The Command Pattern (see http://en.wikipedia.org/wiki/Command_pattern) is the standard way to implement actions in an undoable fashion. This is not very difficult (technically), even if data is stored in a database as is the case with Logos, since commands can store state (see the Memento Pattern - http://en.wikipedia.org/wiki/Memento_pattern) and thus can support undo logic.

David Mitchell

What is needed to get Logos to address "a matter of frequent complaint"?

Well, we don't have an "official procedure" or anything like that, but we do pay a fair bit of attention to http://logos.uservoice.com/. Anyone can go and vote on (or propose) features that they'd like to see implemented in our app. Not only does it give an objective (if somewhat artificial) view of how highly demanded each feature is, it also limits the number of votes per user, which in a way mirrors the limitations of our finite development resources.

After looking through the items on the site, the only thing I could find related to undo was an undo feature for highlighting. It's currently listed at the bottom of page 4, with 11 votes (the most popular feature has 655).

I'm not arguing that undo would not be a welcome or useful feature, but it has yet to attract a great amount of attention.

Stuart Robertson

Thanks David. I'll take a visit to uservoice.com and add my 2c worth. :-)