That should do it for you. Now that you have \RBuilder\Source in your library path you are building your applications with the ReportBuilder source. Now you can set stops in our source and step through it to possibly debug any problems. There should be no need to recompile the ReportBuilder packages.
Nope. I still can debug report builder source code. If I put a breakpoint on line I wish to break on, it turns into a little redcircle with a X through. I do believe that designates the break point is invalid.
Report builder does not turn off debug some where in the source code do they?
When I do a build all with integrated debugger turn on, I do not see the pp*.* files being compiled with the rest of my files. I must be missing something else. Sorry for the inconvenience.
Be sure you \Rbuilder\Lib is no longer in your path. When a break point has an x through it, this just means the code was never executed. As a test place a report and a button on a form and in the button's onClick event call ppReport1.Print;
Then place a break point in the constructor of the TppPreview class located in the ppPreview.pas file. We know this code will be executed when the button is clicked. Now when you run your app, it should break after you click the button.
For debuging purposes, you should be able to turn the "Build with runtime packages" off and debug with your original source. If this option will not work for you. I did a quick search in Google Groups (http://www.google.com/groups) for Delphi runtime package debug, and it returned numerous articles on the subject.
Comments
You can point you library path to the \RBuilder\Source\... to debug the
ReportBuilder source.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
C:\Program Files\Borland\Delphi6\RBuilder\Source
Yupper. That's in my library path. Do you have to compile the RB.DPK's with
the compilers options turned on?
Tim
That should do it for you. Now that you have \RBuilder\Source in your
library path you are building your applications with the ReportBuilder
source. Now you can set stops in our source and step through it to possibly
debug any problems. There should be no need to recompile the ReportBuilder
packages.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Nope. I still can debug report builder source code. If I put a breakpoint on
line I wish to break on, it turns into a little redcircle with a X through.
I do believe that designates the break point is invalid.
Report builder does not turn off debug some where in the source code do
they?
Regards,
Tim
When I do a build all with integrated debugger turn on, I do not see the
pp*.* files being compiled with the rest of my files. I must be missing
something else. Sorry for the inconvenience.
Regards,
Tim
Be sure you \Rbuilder\Lib is no longer in your path. When a break point
has an x through it, this just means the code was never executed. As a test
place a report and a button on a form and in the button's onClick event call
ppReport1.Print;
Then place a break point in the constructor of the TppPreview class located
in the ppPreview.pas file. We know this code will be executed when the
button is clicked. Now when you run your app, it should break after you
click the button.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
path.
Thanks Nico!
You can debug ReportBuilder source with "Build with runtime packages" turn
on!
For debuging purposes, you should be able to turn the "Build with runtime
packages" off and debug with your original source. If this option will not
work for you. I did a quick search in Google Groups
(http://www.google.com/groups) for Delphi runtime package debug, and it
returned numerous articles on the subject.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com