| Summary: | adding a new folder in konqueror sidebar does not work at once | ||
|---|---|---|---|
| Product: | TDE | Reporter: | Denis Prost <denis.prost> |
| Component: | tdebase | Assignee: | Timothy Pearson <kb9vqf> |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | CC: | bugwatch, darrella, denis.prost, michele.calgaro |
| Priority: | P5 | ||
| Version: | 3.5.12 [Trinity] | ||
| Hardware: | i386 | ||
| OS: | Debian Squeeze | ||
| Compiler Version: | TDE Version String: | ||
| Application Version: | Application Name: | ||
|
Description
Denis Prost
2010-10-27 01:22:16 CDT
Problem exists in GIT (2013-05-22). I have no trouble creating a new directory from the sidebar and seeing that new directory appear immediately in the file pane. The new directory does not appear immediately in the sidebar. I have to double-click on the parent directory in the sidebar to see the new directory. This seems familiar to the problem fixed in bug report 1515 with commit 3a3d1875. I'm sorry, I'm using Debian Wheezy now and trinity does not seem ready for it yet (unless there is an install process I don't know : trinity wiki only gives information for lenny and squeeze : I tried to replace lenny/squeeze by "wheezy" in the sources.list lines, but I get a 404 not found error when performing apt-get update). Denis, are you referring to a new folder button on the sidebar? Is still bug still valid? >I have no trouble creating a new directory from the sidebar and seeing that new >directory appear immediately in the file pane. The new directory does not >appear immediately in the sidebar. I have to double-click on the parent >directory in the sidebar to see the new directory.
Darrell, what you described is a bug, but I think Denis was referring to a different thing.
I suggest you create a separate bug report for the issue you observed, which BTW I confirm as well.
(In reply to Michele Calgaro from comment #3) > Denis, are you referring to a new folder button on the sidebar? Is still bug > still valid? Yes Michele, that's what I was reffering to. And no, the bug is not valid anymore, I tested 3.5.13.2 and everything looks OK, so marking it as resolved ! > And no, the bug is not valid anymore, I tested 3.5.13.2 and everything looks
> OK, so marking it as resolved !
Good! Also in pre-R14, I could not reproduce the bug :)
|