[Lazarus] TProcess oddity?

[Bart]

Mattias Gärtner schrieb:

>> More topics:
>>
>> The form designer windows should be closed on start of the program - but
>> I couldn't find an according option.
> 
> Do you mean:
> Environment / Options / Environment / Form Editor / Auto create forms when
> opening a unit
> ?

No. When a GUI program is started in the IDE, the designed forms stay on 
the desktop and are overlaid when the windows are created by the 
application. Moving the runtime form reveals the designtime form, what's 
very confusing.


>> Docking should be handled properly in design state (Windows). It's
>> unclear whether it should be possible to dock forms at design time, or
>> whether it should be disabled at all. It seems to me that at design time
>> only the default dock manager can be used, so that docking at design
>> time doesn't make much sense?
> 
> No docking at design time.

Then it should be properly disabled. As a workaround I leave the 
designed mode as dmManual, and turn it into dmAutomatic in FormCreate - 
but that's not a solution to the problem.


>> What about the LazDoc programs? They don't compile at least since 0.9.26 :-(
> 
> What lazdoc program does not compile?

Neither FPDoc nor lazde. Others untested...


>> When I use the built-in FPDoc, how to publish the results?
> 
> Do you mean, you want to see the fpdoc content without the IDE, for example as
> html or chm files?

I want others to see my updates, too.


>> What about integrating lazde, at least a bigger GUI?
> 
> The main purpose of the fpdoc editor in the IDE is for lazy programmers so that
> they at least write a short sentence for each element. It is not meant as a
> real help editor. That's the purpose of lazde.

Then please make it compile, or provide at least a working binary.

>> It's a pain to tab
>> between abstract, inherited and detailed descriptions in FPDoc, in order
>> to find out about missing documentation for an topic.
> 
> Yes, buttons to jump to next/prev undocumented elements are not yet implemented.

That's a minor feature, which I have just implemented in PasDoc. I can 
add such things to fpdoc/lazde, as soon as these compile.

What I want is an instant overview of the amount of documentation for an 
identifier. I'm willing to improve the documentation (so that I get an 
overview myself ;-), but herefore I need somewhat comfortable tools.

> Feel free to create a feature request in the bug tracker.

Done.

>> I'm also missing means to create and link kind of overviews.
> 
> That one too. They are called 'topics' in fpdoc.

Ah, thanks :-)

DoDi