Rename in WT browser launches default action incorrectly

Bug #521605 reported by Ian Clatworthy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
QBzr
Confirmed
Medium
Gary van der Merwe

Bug Description

As implemented, the Rename context menu action requires the User to press Enter to complete the new name. However, the tree widget also listens out for the Enter key and tries to run the default action when encountered. In qbrowse, this throws an error to the terminal, e.g.

ian@wallaby:~/Projects/scm-play/repo with spaces/trunk$ bzr qbrowse .
Error showing url: Error stating file '/home/ian/Projects/scm-play/repo with spaces/trunk/zz': No such file or directory

When embedded in Explorer, the outcome is more distracting: the (old) file is opened or edited.

Inside Explorer, I've tried keeping track of when the renaming action is active and ignoring calls to do_default_action() during that time. Unfortunately, that hack doesn't work because the keyEvent is processed after renaming thinks it is finished. It looks like this must be addressed in the QBzr layer (somehow).

Changed in qbzr:
assignee: nobody → Gary van der Merwe (garyvdm)
importance: Undecided → Medium
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.