Re: [GRASS-dev] Added suppress_required field to flags

2010-11-25 Thread Glynn Clements
Martin Landa wrote: > > However, this feature cannot be used until the GUI's own requirement > > checking has been adapted to understand it. Currently, if an option > > marked as ->required is omitted but a flag marked as > > ->suppress_required is given, the command itself won't complain about >

Re: [GRASS-dev] Added suppress_required field to flags

2010-11-25 Thread Martin Landa
Hi, 2010/11/25 Glynn Clements : > However, this feature cannot be used until the GUI's own requirement > checking has been adapted to understand it. Currently, if an option > marked as ->required is omitted but a flag marked as > ->suppress_required is given, the command itself won't complain abo

Re: [GRASS-dev] Added suppress_required field to flags

2010-11-25 Thread Hamish
Glynn wrote: > "struct Flag" now has a boolean ->suppress_required > field. If this field is set on a flag, and that flag is given > on the command line, the parser won't check whether ->required > options were provided. see also https://trac.osgeo.org/grass/ticket/886 that would help avoid som

[GRASS-dev] Added suppress_required field to flags

2010-11-25 Thread Glynn Clements
"struct Flag" now has a boolean ->suppress_required field. If this field is set on a flag, and that flag is given on the command line, the parser won't check whether ->required options were provided. This will allow options which are normally required to be marked as required even if there are sp