[Lazarus] Congrats on the new project options screen

[Juha Manninen]

On Sun, Aug 4, 2013 at 4:30 PM, Ludo Brands <ludo.brands at free.fr> wrote:
> Comments:
> - there is a horizontal scroll bar but several strings are simply cut off

Resizing the options window should help. (?)

> - can't specify multiple -Oo optimizations.
> - -Oo options disappear when clicking on "All Options ..." again.
> Independent if you leave the [No] in the option or not

If multiple -Oos are needed then we must have a different GUI for them.


> - no support for spaces in the -o, -l options or any other option taking
> a path or filename. Adding quotes doesn't change this behavior.

Right. I will look at that.


> - FreeBSD is missing from the targets

A bug in FPC. The options are parsed directly from "fpc -h".
This is a nasty situation because the all-options GUI now overwrites
the hand-written custom options.


> - you can check mutually exclusive settings such as all the -M options

This is also nasty. The idea is to offer options parsed from "fpc -h"
without analyzing their meaning. Important options still have their
dedicated GUIs. I think (also) -M must be left out from this
all-options GUI.


> - for one reason or another, vertical scrolling with the scroll bar is
> very jumpy. As if the cpu is running at 100%. This is not the case
> though, "only" 2 cores of an i7 at 40%.

Not here. Your Kubuntu has some config issues. The ScrollBars have
smooth scrolling enabled and it works well here, using both GTK2 and
QT.


> - -Cf options are not split up, you can only select
> -CfSSE64,SSE3,SSSE3,SSE41,SSE42,AVX

I improved the parsed. This is also an inconsistency if FPC. All
categories in "fpc -i" output from FPC 2.6.2 are separated by newline.
FPC 2.7.1 changed FPU instruction sets to a comma separated list.

Dimitry (skalogryz) wanted to have external config files for options
for every FPC version, and even for other compilers. We had a
discussion in dev mailing list. I don't know if he will make code for
it.
It would be easier to parse but it needs more maintenance. Ideal would
be to have machine readable output from FPC directly, instead of the
inconsistent help output.

Regards,
Juha