[bt-devel] [ bibletime-Bugs-1337338 ] lexicon display window accpets illegal keys by drag&drop

[SourceForge.net]

Bugs item #1337338, was opened at 2005-10-25 11:45
Message generated for change (Comment added) made by eelik
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100954&aid=1337338&group_id=954

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Frontend / GlossaryLexicon display window
Group: new bug
Status: Open
Resolution: None
Priority: 2
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Gary  Holmlund (gholmlund)
Summary: lexicon display window accpets illegal keys by drag&drop

Initial Comment:
I opened a lexicon (like StrongsGreek or Naves) and a bible. Then, I 
moved a bible key onto the lexicon by drag&drop. The lexicon accepted it 
(e.g. John 17:20) and shew a page with that heading but no contents.  
 
This is probably unintended as no such page is shown if you type in this 
key into the key chooser of a lexicon window. And, Bible display windows 
make their first key their current key if one drags&drops an illegal key on 
them (e.g. from a lexicon window). 
 
Perhaps it is possible to indicate by the pointer shape (e.g. "") if a key 
can be dropped into a particular display window or not? And if one drops 
an invalid key nonetheless, nothing would happen. This drag&drop 
behaviour is what users know from other applications, I think. 
 
This bug was experienced with BibleTime 1.5.1. 

----------------------------------------------------------------------

>Comment By: Eeli Kaikkonen (eelik)
Date: 2009-12-03 07:54

Message:
There is one usability problem here, and possibly to different use cases.
The usability problem is what to do when a non-existing key is entered. The
two use cases are as described in the report: d'n'd and manual entering.

Expected behaviour would be to indicate in some way that the wanted key
isn't found. One possibility is to just show either the next or previous
one alphabetically, but which one? And it could be confusing because user
gets something he didn't want. On the other hand, I can find one handy use
for "show the previous one" behaviour: user could drag a reference from the
Bible window and get the closest description for the word in the key. E.g.
John 1:1 would return John in a lexicon. However, even that wouldn't hit
the point in most cases. I think the most informative behaviour would be to
show some text: "Entry "<key>" was not found. Previous alphabetical entry:
<xxx-link>. Next alphabetical entry: <yyy-link>. This should be of course
applied to d'n'd as well as other key entering methods.

----------------------------------------------------------------------

Comment By: Kang Sun (k486)
Date: 2009-11-25 19:54

Message:
I think this is related to the parallel lexicon crash.

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2009-11-14 18:19

Message:
Bug still present.

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2008-05-17 09:08

Message:
Logged In: YES 
user_id=169722
Originator: NO

Eeli, can you implement this (can be later than 1.7)?

----------------------------------------------------------------------

Comment By: Eeli Kaikkonen (eelik)
Date: 2007-09-29 22:29

Message:
Logged In: YES 
user_id=1031029
Originator: NO

With the new d'n'd system this should be reasonably easy. When drag moves
the underlying widget accepts/rejects possible drop in an event handler.
It's couple of lines of code to check if the key is supported by the module
type, I think.

----------------------------------------------------------------------

Comment By: Martin Gruner (mgruner)
Date: 2006-02-25 12:28

Message:
Logged In: YES 
user_id=169722

This will require bigger changes to the DND system, but is 
not so urgent--later.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100954&aid=1337338&group_id=954