[Patch] Window history
Paulo Moura Guedes
moura at kdewebdev.org
Tue Feb 13 14:08:06 UTC 2007
On Tuesday 13 February 2007 08:24, Jens Dagerbo wrote:
> On 2/13/07, Paulo Moura Guedes <moura at kdewebdev.org> wrote:
> > Navigation history seems a little broken here. And it doesn't remember
> > switches via tabwidget IIRC.
> I reacted to "and".. Navigation history only tracks calls through
> PartController::editDocument(). The reason is KMDI* - there was no
> other approach that had any chance of working while we were still
> carrying that monstrosity. Now that we're finally rid of it, we could
> try to fix this. Is there any other breakage in Navigation history?
> I'm not aware of any.
I remember that some times it took me into unexpected places but I don't have
use case right now, sorry.
> Btw, there is at least one document change scenario left that doesn't
> come with a tabwidget change: changing between documents open in a C++
> header/source split view. (This is a very annoying special case - you
> can turn it on in project settings -> C++ - > Navigation.) Your patch
> doesn't handle this. I'm not sure it's even a good idea to try.. the
> resulting code will be a mess. :(
That's true. I found that feature I few days ago btw, but ctrl-tab makes me
more productive :)
> It does handle regular split views, right? I realize now I didn't test
Neither do I. I just tested and it doesn't work with split views :(
> > Window menu is also a different navigation method (sorted
> > alphabetically). The file list is duplicated stuff IMHO. There is someone
> > using that? Quick Open is very cool and something unique when looking at
> > other IDEs.
> I'm happy to remove the Window menu. It's more or less useless and
> doesn't scale. The FileList does and can be interacted with (it
> exposes FileContext so any action hooked onto that will be available)
> and navigated by keyboard.
True, I vote for that too.
> > I can't answer for the users but this is a navigation method that doesn't
> > exist yet in KDevelop (no duplication)
> That's technically correct, but the differences are somewhat subtle.
From a usability point of view I think they are anything but subtle :)
> Speaking of subtle.. I think your Next action does what I expect it
> to, but I couldn't really understand what Previous did, or why it's
> needed. Care to educate me? :)
The previous goes in the other way around. Like the window manager
ALT-SHIFT-TAB. Just standard behaviour.
More information about the KDevelop-devel