[Lazarus] Tools/Run Parameters storage in .lps/session file instead of lpi?

[Martin]

On 26/02/2012 15:56, Mattias Gaertner wrote:
> On Sun, 26 Feb 2012 16:17:48 +0100
> Reinier Olislagers<reinierolislagers at gmail.com>  wrote:
>
>> Hi list,
>>
>> Developing fpcup together using a mercurial repo with Ludo Brands, which
>> is always a pleasure.
>>
>> Less of a pleasure is that we frequently have conflicts in fpcup.lpi
>>
>> One of the changes that we saw in the commits:
>> -<CommandLineParams Value="--verbose"/>
>> +<CommandLineParams Value="--verbose --help"/>
>>
>> which got me wonder.
>>
>> Wouldn't it make more sense to store the Tools/Run Parameters in the
>> .lps/session file instead of the lpi file?
>> Each developer may have their own aspect of the application they're
>> testing and can therefore have different needs.
> True.
>
>
>> Would writing a patch be worthwhile? A quick search on mantis on "run
>> parameters" gave no results...
> Yes.
> Keep in mind:
> - Many developers use both the released IDE and the trunk IDE. So
>    if possible try to keep backward compatibility. Simply moving a value
>    from lpi to lps breaks this.
> - Often it is needed to have various sets of run/debug parameters.
>    Often these are not the same as "build modes", so they should be a
>    separate set. Maybe they can be called "run modes".
> - All settings in the run parameters dialog should go into that.
+1

I really often need to toggle the "Host Application", and that does not 
even have a dropdown


> - the build modes solves the backward issue, by saving the first build
>    mode always at the old place of the lpi. For every other build
>    mode the user can choose where to store it - the lpi or lps.
>
+1