The patch is pretty intrusive, since it does that behavior for *any* code asking the editor manager to open something. Not only 'follow symbol' et al but also opening a file from e.g. the projects tree, from locator and File > Open. So I'm not sure that it's the right thing. With the patch, if a file is already open somewhere, the only way I see to explicitly open the file again in the *current* split is through the documents combo box above the split...
An option in the sense of something in Tools > Options is not an option IMO. Br, Eike -- Eike Ziller Principal Software Engineer Nokia, Qt Development Frameworks Nokia gate5 GmbH Firmensitz: Invalidenstr. 117, 10115 Berlin, Germany Registergericht: Amtsgericht Charlottenburg, Berlin: HRB 106443 B Umsatzsteueridentifikationsnummer: DE 812 845 193 Geschäftsführer: Dr. Michael Halbherr, Karim Tähtivuori ________________________________ From: qt-creator-bounces+eike.ziller=nokia....@qt-project.org [qt-creator-bounces+eike.ziller=nokia....@qt-project.org] on behalf of ext Typz [thet...@gmail.com] Sent: Wednesday, May 30, 2012 18:42 To: Jonathan S. Shapiro Cc: qt-creator@qt-project.org Subject: Re: [Qt-creator] Some thoughts about 2.5 Hello, Regarding the "focus" issue, i have a quite simple patch which solves this: when opening an editor, it checks if there is a view showing the same file already and re-uses it if found; otherwise, the current view is updated. It all happens here: https://codereview.qt-project.org/27493 Should this be the standard behavior, or should there be an option (and where) ? Best regards, -- Francois On Tue, May 29, 2012 at 7:10 PM, Jonathan S. Shapiro <s...@eros-os.org<mailto:s...@eros-os.org>> wrote: Geronimo: I welcome your suggestions and questions about QtCreator, but I am finding your posts very disruptive to read. I would like to make two suggestions: 1. Please try to avoid strongly negative value words, except where they describe a technical problem. Words like "caponize" have no place in a productive technical discussion. 2. I think that your requests and goals would be clearer if you focus on what it is you want to have happen in QtCreator, rather than on the details of your background and your specific project. For example: "When I do <action>, I would like QtCreator to be doing XYZ". Making those descriptions simpler and more focused, and avoiding distracting details, will make it easier for people to understand what you suggest. That will allow them to evaluate your suggestion[s] more effectively. For example, here are three features that I would really like to see: 1. Given a selection, an entry on the right-click menu that will let me see all of the keyboard shortcuts that I could be using for that selection. I'm pretty new to QtCreator, and I keep seeing emails go by that say "oh, just use the XYZZY shortcut". It would be really nice to have a way to see what shortcuts are relevant in a more localized way. Don't know how easy/hard this would be. 2. When following symbol definition: if the file is already open in another window, move to the definition in that window and shift the focus to there. 3. An option I could set somewhere to prefer that the result of any "context changing" operation (find symbol and so forth) occur in another window. As you can see: each of these gives a clear description of what I want (or at least what I *think* I want). Others can now look at them and say "that's a dumb idea", or "hey, I want that too", or "that's too hard", or "that's doable, but it isn't as important as other things, and we're probably not going to get to it." Keeping the discussion technical helps it move forward. Respectfully, Jonathan _______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org<mailto:Qt-creator@qt-project.org> http://lists.qt-project.org/mailman/listinfo/qt-creator
_______________________________________________ Qt-creator mailing list Qt-creator@qt-project.org http://lists.qt-project.org/mailman/listinfo/qt-creator
