[Lazarus] Run parameters

[Kostas Michalopoulos]

The problem of not associating build modes with run modes is that not all
run modes will apply to all build modes. Note that i don't think run modes
should be *part* of build modes, but only an association between build
modes and run modes. Basically, what you say about a default run mode per
build mode, i say to make it a list of what is *not* (from a UI perspective
you'll see them as what is part, but only store what is not so that when
you add a new run mode it is available to all build modes without the user
needing to go at each one and enable it).


On Sat, Feb 11, 2017 at 3:31 PM, Michael Van Canneyt via Lazarus <
lazarus at lists.lazarus-ide.org> wrote:

>
>
> On Sat, 11 Feb 2017, Kostas Michalopoulos wrote:
>
> I think having a list for run modes (i assume you mean the settings you
>> specify in the Run -> Run Parameters dialog box) that you can select from
>> a
>> popup menu near the "play" button and have different run modes apply, like
>> you can select the build mode from the "gear" button, is a good idea.
>> Being
>> able to switch configuration files and working directories from inside
>> Lazarus for some of the tools i work with would be very nice.
>>
>> The only thing i disagree with is to have them per build mode since
>> chances
>> are you'd need them with different build modes (e.g. debug, release,
>> profile, etc would have the same run modes) and even if you could copy
>> them, it would still be an annoyance to make sure all are available.
>>
>> Instead i'd say to have a table with a column per build mode and a row per
>> run mode, have checkboxes for those that will apply and those checkboxes
>> would be enabled by default.
>>
>> Alternatively just use a global list that is the same across all build
>> modes, but then you may have run modes that do not apply in all build
>> modes
>> and have them take up space (e.g. if one of your run modes causes a
>> program
>> to load a 32bit DLL and you are in a build mode that explicitly targets a
>> 64bit OS this run mode wouldn't apply - of course one case wouldn't matter
>> much, but the next thing i imagine after such a feature is available is
>> being able to generate run modes automatically though a script :-P).
>>
>
> If you want a list, I would simply allow to make a list as you suggest,
> and for each build mode you can simply specify which item in the list is
> used as default when pressing run. Being able to specify multiple
> run modes per build mode seems way overkill to me.
>
> I don't want to end up with Eclipse, where you need a Phd in Eclipse to be
> able to do even simple tasks in the IDE...
>
>
> Michael.
> --
> _______________________________________________
> Lazarus mailing list
> Lazarus at lists.lazarus-ide.org
> http://lists.lazarus-ide.org/listinfo/lazarus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lazarus-ide.org/pipermail/lazarus/attachments/20170211/06f2767d/attachment.html>