Lazarus Release Candidate 1 of 2.2.0

[d7_2_laz]

Would be nice!
Many thanks to you both for attention!
OutputDebugString, as based specifically on an Windows API call, is rather known in the Windows environment.
I like it because it is a handy and easy way to put info to the message window,
without needing to apply (and remove afterwards) additional includes, or to change project options temporarely between the compiles.
Simply code a one-liner, trace your program flow and remove the line afterwards. So it would be nice to see it stay alive and not die, if possible.

[440bx]

Just haven't gotten around yet do add it.

That makes sense.  I was fairly sure you knew about it but, just in case, I thought I'd mention it.

I like it because it is a handy and easy way to put info to the message window,
without needing to apply (and remove afterwards) additional includes, or to change project options temporarely between the compiles.
Simply code a one-liner, trace your program flow and remove the line afterwards. So it would be nice to see it stay alive and not die, if possible.

Just in case you might be interested, for complex parts of a program I code something like this

Code: Pascal  [Select][+][-]

1. if IsDebuggerPresent then
2. begin
3.   { if there is no console, create a console, otherwise use the existing console }
4.  
5.   { format the string message using whatever functions are appropriate }
6.  
7.   writeln(<the formatted string>)
8.  
9.   { possibly trigger an int 3 depending on what has happened or a readln }
10.   { optionally dispose of the console }
11.  
12.   { resume execution }
13. end;

[jamie]

What's wrong with Asserts? They don't work anymore ?

[Martin_fr]

I have tried to install the lazreportpdfexport0.9 package on windows 7 32 bit and it gives me the following error:

lr_e_pdf.pas(539,19) Error: identifier idents no member "SubType"
lr_e_pdf.pas(540,26) Error: identifier idents no member "URI"

I asked around, I was told https://bugs.freepascal.org/view.php?id=37995
(outdate powerpdf version)

[PascalDragon]

What's wrong with Asserts? They don't work anymore ?

If all you want is to generate some output if a debugger is present, but keep the program itself running then an Assert would be the wrong functionality to use.

[d7_2_laz]

Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated? Didn't get it quite fore sure.
(bzw: thanks 440bx for your additinal hint!)

[CM630]

win32richmemoproc.pas from richmemopackage does not compile for me.
Says
win32richmemoproc.pas(335,22) Error: Incompatible types: got "<address of function(PDWord;PByte;LongInt;var LongInt):DWord;StdCall>" expected "<procedure variable type of function(LongWord;PByte;LongInt;var LongInt):DWord;StdCall>" on cbs.pfnCallback := @RTFLoadCallback;

[avra]

Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated?

I have checked it today and it worked. When in Lazarus / Tools / Options / Debugger / EventLog / Messages you check Output checkbox, OutputDebugString('<<<<< It works ! >>>>>') outputs to Debug Output window (I have tested it with a simple button on a form and it's on click event). There are a lot of debug messages so you will have to search for it, but it is there. Your GUI or console application needs to include windows unit and you need to make Output Debug window visible. That's all you need to do on Windows.

For more serious work I do recommend something like MultiLog.

[Martin_fr]

Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated? Didn't get it quite fore sure.
(bzw: thanks 440bx for your additinal hint!)

I think it needs gdb currently.

As for FpDebug, not sure if I get to it in time.

[d7_2_laz]

Thank for your both info!

[skalogryz]

win32richmemoproc.pas from richmemopackage does not compile for me.
Says
win32richmemoproc.pas(335,22) Error: Incompatible types: got "<address of function(PDWord;PByte;LongInt;var LongInt):DWord;StdCall>" expected "<procedure variable type of function(LongWord;PByte;LongInt;var LongInt):DWord;StdCall>" on cbs.pfnCallback := @RTFLoadCallback;

It appears to be FPC 3.2.2 related
And should have been fixed with this pull request
Are you pulling your richmemo from github?

[d7_2_laz]

avra, i don't see those options at the told place   .. even not with the gdb.
Could we exchange a bit some settings?  I'll open an item in the Debugger forum  (but not today).
Thanks!

[Martin_fr]

Only a short questoion: about the "OutputDebugString" / Windows as mentioned earlier,
will it be reanimated? Didn't get it quite fore sure.

Should work with fpdebug (on windows).
Tested with 64 bit, if someone can check 32bit...

Trunk or fixes branch

[avra]

avra, i don't see those options at the told place   .. even not with the gdb.

Be more specific of what you do not see. Output checkbox in "Lazarus / Tools / Options / Debugger / EventLog / Messages" configuration dialogue, Debug Output window, or something else?

[CM630]

win32richmemoproc.pas from richmemopackage does not compile for me.
...

It appears to be FPC 3.2.2 related
And should have been fixed with this pull request
Are you pulling your richmemo from github?

I have downloaded it from sourceforge.
Now I cloned it from github and it works.
Thanks!