[Lazarus] Lazreport, again.

[Jesus Reyes]

--- El dom 17-ago-08, Michael Van Canneyt <michael at freepascal.org> escribió:

> De:: Michael Van Canneyt <michael at freepascal.org>
> Asunto: [Lazarus] Lazreport, again.
> A: "Lazarus mailing list" <lazarus at lazarus.freepascal.org>
> Fecha: domingo, 17 agosto, 2008, 6:54 am
> hi,
> 
> I keep getting the following errors in Lazarus when trying
> to design a report:
> 
> Gdk-CRITICAL **: file gdkwindow.c: line 727
> (gdk_window_unref): assertion `private->ref_count >
> 0' failed.
> TCustomForm.SetActiveControl frDesignerForm:TfrDesignerForm
> AWinControl=ValueEdit:TEdit
> GetParentForm(AWinControl)=frDesignerForm:TfrDesignerForm
> csLoading=False AWinControl.CanFocus=False
> IsControlVisible=True Enabled=True
> TApplication.HandleException Cannot focus a disabled or
> invisible window
>   Stack trace:
>   $00000000006F4476 line 1278 of include/customform.inc
>   $00000000006F1802 line 108 of include/customform.inc
>   $0000000000832941 line 4913 of include/wincontrol.inc
>   $0000000000A01973 line 1802 of objectinspector.pp
>   $0000000000A01F5A line 1932 of objectinspector.pp
>   $0000000000840044 line 3202 of include/control.inc
>   $00000000006DB279
>   $000000000083C33E line 1583 of include/control.inc
>   $0000000000831F90 line 4715 of include/wincontrol.inc
>   $00000000009264F0 line 3543 of gtkproc.inc
>   $0000000000932719 line 1094 of gtkcallback.inc
>   $000000000093289F line 1172 of gtkcallback.inc
> 
> Lazarus from today, x86_64, linux, GTK 1.
> 
> Steps to reproduce:
> - Install lazreport package
> - Drop tfrreport on form
> - Select 'Design report' from context menu
> - Drop band on report.
> - Move the fastreport object inspector around...
> -> Above error.
> 
> A second way of getting this is simply trying to expand the
> 'Font' editor in the fastreport
> object inspector.
> 
> I've been playing about with it for a couple of hours,
> and start wondering if anyone has
> ever been able to make a working report with it, it is
> extremely unstable... ?

The problem above was introduced in latest patch of LazReport, IMO it works much better now but it doesn't mean that everything it's working all fine, and the true is that some times while fixing something another one get bad side effects, lack of time to test on all widgetsets which doesn't work exactly the same on every single detail makes difficult to track down all flaws. Also, I don't agree that it's "extremely unstable" but I do agree that it doesn't work all good in all widgetsets, yet.

For the moment this one should fixed in r16090.

> 
> Michael.

Jesus Reyes A.

__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.yahoo.com.mx/