[Qt-creator] Cross-debugging Win-Linux // project-session issue

[André Pönitz]

On Monday 07 March 2011 05:36:28 ext andy fillebrown wrote:
> On Sun, Mar 6, 2011 at 12:12 PM, Andre Poenitz
> <andre.poenitz at mathematik.tu-chemnitz.de> wrote:
> > On Sun, Mar 06, 2011 at 11:04:07AM -0500, andy fillebrown wrote:
> >> I tend to agree with Patrick.  I rarely launch and app to open a file
> >> from inside it (unless I absolutely have to).  I prefer double
> >> clicking a file in the file explorer.  When I do this with VS, no
> >> problem -- session info loads.  With QtCreator, session info does not
> >> load.  It would be nice if it did.
> >
> > The problem is to find out which session is meant. Maybe just creating
> > a list of matches and let the user select (and auto-open if there's
> > only a single one) would already work.
> 
> That would be an improvement, but I'd rather have the option to put a
> session file wherever I want.  I realize this would make it possible
> to accidentally put it under revision control, but is that really an
> issue worth trying to solve?

Yes, we have a similar problem with the current *.pro.user files, and we had
dozens of incidences where people put them into SCM or tried to copy them.

Anyway, it's a non-issue for the session, as it's solved properly by having 
the personal session data in the local user settings, and not in the 
"directly visible" file system.
 
> Another possibility would be to formalize the setup a top level
> session directory.  Something like:
> 
> + session/
>    + shadow-builds/
>    + source/
>    + session-file-1
>    + session-file-2

The non-source parts of that structure exist, on Linux it's
 ~/.config/Nokia/qtcreator/

I honestly do not understand why people insist on moving personal session
data into the source directory of some (random, as there is no 1:1 mapping?)
project, "assuming" it would do no harm, and not even having a problem
that would be actually solved by such a move.

> That would make more sense to me than the current way QtCreator
> handles sessions and default shadow build directories.

Shadow builds are a separate issue, and I concur that this issue is not 
solved, as is the problem of project specific editor settings and such,
and generally the layout (or even existence) of the .pro.user files.
It's in the works, though.

Andre'