On 26/05/2013 06:48, Felipe Monteiro de Carvalho wrote:
Yes, the code needs to be rewritten. It was written before a system
was created to allow widgetsets to override debugln. It also needs a
variable in the widgetset class to allow the user to choose if he
wants the log or not.
but the code
I get these in my lcldebug.log on Wince:
TWinControl.DoDockClientMsg DockPanel:TPanel
Control=MobileWelcomeForm:TMobileWelcomeForm
DestRect=l=579,t=102,r=819,b=550
TWinControl.DoDockClientMsg DockPanel:TPanel
Control=OpenMapForm:TOpenMapForm DestRect=l=823,t=420,r=1063,b=720
Yes, the code needs to be rewritten. It was written before a system
was created to allow widgetsets to override debugln. It also needs a
variable in the widgetset class to allow the user to choose if he
wants the log or not.
--
Felipe Monteiro de Carvalho
--
Hi, Would you please stop generate a debug file for wince
lclproc.pas line 1695
procedure DebugLn(const s: string);
begin
{$ifdef WinCE}
if DebugNestAtBOL and (s '') then
DbgAppendToFile(ExtractFilePath(ParamStr(0)) + Str_LCL_Debug_File,
DebugNestPrefix+s)
else
Is this about debugln does not log correctly, or about something gets
logged, that you did not want to be logged?
I think the question is what is calling debugln.
- If your code does, then it should log.
- If it is in the IDE (but you wouldn't run that on wince) then that is
correct to.
- If
On 24/05/2013 19:42, Zaher Dirkey wrote:
On Fri, May 24, 2013 at 9:17 PM, Martin laza...@mfriebe.de
mailto:laza...@mfriebe.de wrote:
I think the question is what is calling debugln.
- If your code does, then it should log.
- If it is in the IDE (but you wouldn't run that on
