[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-10-02 Thread RJVB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #9 from RJVB --- I think that what happens is that the review and debug areas have its own setting for the documentation visibility, and that somehow the visibility isn't restored properly when going back to the code

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-11 Thread RJVB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #8 from RJVB --- (posted too fast) Wouldn't that give a hint at what's going here, i.e. "simply" a lack of persistence of the documentation view's settings? -- You are receiving this mail because: You are watching

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-11 Thread RJVB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #7 from RJVB --- Well, I thought I could simply work around this issue by removing the Documentation button from my toolbars. While that's true I have to repeat the action each time I restart KDevelop because that damn.

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-07 Thread RJVB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #6 from RJVB --- Indeed, same thing when the debugged application terminates and the debug view is closed. Could this be something like a missing variable initialisation? I've already encountered situations where that

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-07 Thread Aleix Pol via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #5 from Aleix Pol --- Could be a problem upon restoring the session. Do you get the same problem when debugging and getting back to code? -- You are receiving this mail because: You are watching all bug changes.

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-07 Thread RJVB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #4 from RJVB --- Created attachment 100966 --> https://bugs.kde.org/attachment.cgi?id=100966=edit screen recording showing the issue Sorry for the slightly nauseating hand-held video; I don't do this often enough to

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-07 Thread RJVB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 RJVB changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|INVALID

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-06 Thread RJVB via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 --- Comment #2 from RJVB --- I agree it doesn't make any sense, but still it is what's happening. With all due respect, what's the point in accepting bug reports if you leave it to the reporter to figure out what's going on, and

[kdevplatform] [Bug 363494] closing a Patch Review via (git) commit opens the documentation view

2016-09-06 Thread Aleix Pol via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=363494 Aleix Pol changed: What|Removed |Added Resolution|--- |INVALID