Bug 450316 - Unable to Copy File Into the Same Directory using Projects Viewer
Summary: Unable to Copy File Into the Same Directory using Projects Viewer
Status: RESOLVED DUPLICATE of bug 435235
Alias: None
Product: kdevelop
Classification: Applications
Component: UI: general (show other bugs)
Version: git master
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-02-15 16:31 UTC by Edward Kigwana
Modified: 2022-02-18 16:08 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Edward Kigwana 2022-02-15 16:31:46 UTC 
Copying a file into the same directory causes the "File Already Exists" dialog to popup and provide the user and opportunity to rename the file. Before a user can get around to renaming the file, a modal Kdevelop "Copying" dialog pops up and blocks input to the file rename dialog. This last pop up is a copy progress indicator with a pause and a stop button.

STEPS TO REPRODUCE
1. Open a project
2. Using the Projects UI viewer right click a file and choose copy in context menu
3. Using the Projects UI viewer right click directory containing file in previous step and select paste

OBSERVED RESULT
- Rename dialog pops up but user cannot interact with it.
- Kdevelop copying notification block forever until it is stopped.

EXPECTED RESULT
- Rename dialog modal to Copying progress dialog which is turn modal to Kdevelop main window
- Ability to rename file
Comment 1 Igor Kushnir 2022-02-18 09:25:54 UTC 
This report is very similar to Bug 435235. But if the user is able to dismiss the dialog (if the dialog can be interacted with), then that's already better than the previously reported bug :)
Comment 2 Edward Kigwana 2022-02-18 12:56:26 UTC 
I was unaware of the that bug. This is a duplicate.
Comment 3 Igor Kushnir 2022-02-18 16:08:31 UTC 
*** This bug has been marked as a duplicate of bug 435235 ***