Makeskel expects another(?) semicolon after win\wininc\func.inc:
function GetRandomRgn(aHDC: HDC; aHRGN: HRGN; iNum: WINT): WINT;
stdcall; external 'gdi32';
function ...
Perhaps it cannot parse the "external" directive?
FPDoc seems to suffer from the same problem, it creates an all-empty
des
Felipe Monteiro de Carvalho schrieb:
Yes, in the case of the rectangle drawing I think it was a typo by who
implemented the current rectangle in fcl-image, I have done various
similar typos in my coding and they don't mean I really wanted to
redefine rectangle.
But the TCanvas line is trully co
Marco van de Voort schrieb:
That's a known issue. IIRC a workaround was to compile fpdoc without
optimization.
Sorry, that didn't help :-(
So what was your commandline to build the checkout ?
Argh, I did updates regularly, but forgot to rebuild the compiler etc. :-(
But rebuilding only rem
On Thu, Dec 8, 2011 at 11:49 AM, Hans-Peter Diettrich
wrote:
> I'd suggest that you use the TCanvas conventions, before you run into well
> known pitfalls.
>
> E.g. an empty rectangle should be (x,y, x,y), while a single pixel should be
> (x,y, x+1,y+1). The Width is Right-Left, not Right-Left+1.
michael.vancann...@wisa.be schrieb:
Currently the following steps are required to build the project file
and the docs:
1. make -n > mydocs.bat
2. edit mydocs.bat to make fpdoc create an project file
3. mydocs.bat
4. edit the mydocs.xml project as required
5. fpdoc mydocs.xml
2+3 could be omit
In our previous episode, Hans-Peter Diettrich said:
> >> But when I tried to build the LCL, fpdoc crashes badly in
> >> THTMLWriter.AppendProcType (SIGSEGV). I tried to catch this error by
> >> try-except, but then Windows kills fpdoc. Running from the commandline
> >> at least reveals the Eleme
Marco van de Voort schrieb:
But when I tried to build the LCL, fpdoc crashes badly in
THTMLWriter.AppendProcType (SIGSEGV). I tried to catch this error by
try-except, but then Windows kills fpdoc. Running from the commandline
at least reveals the Element as "FontEnumProc".
I'll have to resear
On Thu, 8 Dec 2011, Hans-Peter Diettrich wrote:
michael.vancann...@wisa.be schrieb:
Does there exist a chance (trick) to use the input files of a different
installation, without copying the description files?
If you use the make command to generate the docs, simply pass the
FPCSRCDIR comma
michael.vancann...@wisa.be schrieb:
Yes, but changing this will break existing code ?
Such code can be considered broken, deserves an fix anyhow.
Yes, it cannot do both at the same time, unless we add a property
PaintLikeTCanvas or something like that.
Hm. I would reverse the property. "Us
Marco van de Voort schrieb:
In our previous episode, Sven Barth said:
The -v option should become more verbose, just for hunting such bugs.
And the messages should go to stdout instead of stderr, at least on
Windows (with poor redirection capabilities).
StdErr redirection works in Windows the s
michael.vancann...@wisa.be schrieb:
Does there exist a chance (trick) to use the input files of a different
installation, without copying the description files?
If you use the make command to generate the docs, simply pass the
FPCSRCDIR command line parameter.
eg: make rtl.chk fcl.chk FP
In our previous episode, Sven Barth said:
> > The -v option should become more verbose, just for hunting such bugs.
> > And the messages should go to stdout instead of stderr, at least on
> > Windows (with poor redirection capabilities).
>
> StdErr redirection works in Windows the same as on Unix
On Thu, 8 Dec 2011, Felipe Monteiro de Carvalho wrote:
On Thu, Dec 8, 2011 at 9:33 AM, wrote:
Yes, but changing this will break existing code ?
Yes, it cannot do both at the same time, unless we add a property
PaintLikeTCanvas or something like that.
Hm.
I would reverse the property. "
Am 08.12.2011 02:59, schrieb Hans-Peter Diettrich:
Michael Van Canneyt schrieb:
Wait, did you try this on FPC trunk sources ? That won't work.
2.6.0 sources should be OK.
I could build RTL and FCL docs from 2.4.2 without major problems (the
trunk Makefile was not fully compatible with the old
On Thu, Dec 8, 2011 at 9:33 AM, wrote:
> Yes, but changing this will break existing code ?
Yes, it cannot do both at the same time, unless we add a property
PaintLikeTCanvas or something like that.
--
Felipe Monteiro de Carvalho
___
fpc-devel maillis
On Thu, 8 Dec 2011, Felipe Monteiro de Carvalho wrote:
Some more changes I'd like to propose. It seams that Rectangle is not
TCanvas compatible:
procedure TFPPixelCanvas.DoRectangle (const Bounds:TRect);
A rectangle over (0, 0, 10, 10) should not include the pixels line
with x=10 and y=10 bu
Some more changes I'd like to propose. It seams that Rectangle is not
TCanvas compatible:
procedure TFPPixelCanvas.DoRectangle (const Bounds:TRect);
A rectangle over (0, 0, 10, 10) should not include the pixels line
with x=10 and y=10 but instead go only to x=9 and y=9, it is
considered that the
On Thu, 8 Dec 2011, Graeme Geldenhuys wrote:
On 7 December 2011 23:09, Hans-Peter Diettrich wrote:
Does there exist a chance (trick) to use the input files of a different
installation, without copying the description files?
If you use the make command to generate the docs, simply pass the
18 matches
Mail list logo
