Bug Xailer 2.5 ?

[ricardo.pinto]

Hi,
In Xailer 2.4.4, when create an GroupBox and set Font:Bold, then inside
create TEdit and DateEdit, both with property lParentFont=F, only the cText
of GroupBox is bold.
But now, I've upgraded to Xailer 2.5 and when i do those same steps, the
result aint the same...It gives the idea that TEdit and DateEdit "ignore"
the property lParentFont=F...because they still bold.
The only way that i found to solve this its going to property font of
TEdit/DateEdit, open the dialog and without doing nothing click "Ok"....Then
when you run again the project, this is solved.
Any idea how to solve this without going to all objects in project and do
this step?
Thanks,
Ricardo Pinto

[ignacio]

ricardo.pinto escribió el mié, 07 diciembre 2011 11:11Hi,
In Xailer 2.4.4, when create an GroupBox and set Font:Bold, then inside
create TEdit and DateEdit, both with property lParentFont=F, only the cText
of GroupBox is bold.
But now, I've upgraded to Xailer 2.5 and when i do those same steps, the
result aint the same...It gives the idea that TEdit and DateEdit "ignore"
the property lParentFont=F...because they still bold.
The only way that i found to solve this its going to property font of
TEdit/DateEdit, open the dialog and without doing nothing click "Ok"....Then
when you run again the project, this is solved.
Any idea how to solve this without going to all objects in project and do
this step?
Thanks,
Ricardo Pinto
Here is working fine. See image attached.
Regards,



Attached files

[ricardo.pinto]

But the goal its TEdit and DateEdit don't be bold.
in the image attached its how it looks in 2.4.4. But in 2.5 all the TEdit
remain bold and the property lParentFont=F.
Thanks!
"Ignacio Ortiz de Zúñiga" escreveu na mensagem
news:4edf458f$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
ricardo.pinto escribiíƒÂ³ el miíƒÂ©, 07 diciembre 2011 11:11
> Hi,
>
> In Xailer 2.4.4, when create an GroupBox and set
> Font:Bold, then inside create TEdit and DateEdit, both with property
> lParentFont=F, only the cText of GroupBox is bold.
>
> But now, I've upgraded to Xailer 2.5 and when i do those
> same steps, the result aint the same...It gives the idea that TEdit and
> DateEdit "ignore" the property lParentFont=F...because they still bold.
>
> The only way that i found to solve this its going to
> property font of TEdit/DateEdit, open the dialog and without doing
> nothing click "Ok"....Then when you run again the project, this is solved.
>
> Any idea how to solve this without going to all objects
> in project and do this step?
>
> Thanks,
> Ricardo Pinto
Here is working fine. See image attached.
Regards,
--
Ignacio Ortiz de ZíƒÂºíƒÂ±iga
[Equipo de Xailer/Xailer team]
http://www.xailer.com
http://www.xailer.info
--

Attached files

[jlalin]

Ricardo,
I did some test and it works quite fine here.
Can you make a little test to reproduce the error and send it here?
Saludos,
José Lalí­n

[ricardo.pinto]

Hi José,
I send in attach one example that was created in xailer 2.4.4. But when open
in 2.5 you'll see that the Tedit it's bold.
Thanks!
"José Lalí­n" escreveu na mensagem news:4edfbdbc$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
Ricardo,
I did some test and it works quite fine here.
Can you make a little test to reproduce the error and send it here?
Saludos,
José Lalí­n
--

Attached files Xailer2_4_4.zip (40.1 KB)Â

[jfgimenez]

Ricardo,
> I send in attach one example that was created in xailer 2.4.4. But
> when open
> in 2.5 you'll see that the Tedit it's bold.
Thanks for the sample. I've been reviewing it, and the problem is that
the TEdit control has an undefined font. That is, if you open the .xfm
file, you'll see that the TEdit control has lParentFont := .F., but
there is no font assigned to it, so it's undefined.
There was a bug in previous versions of Xailer, exactly in that case,
when lParentFont := .F. and the current font is the same as the form's
one. In this case, Xailer didn't save the font assignment to the
control. Now, Xailer 2.5 does. Sorry for any inconvenience.
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

[ricardo.pinto]

Hi Jose,
So what you're saying that's necessary go to all this cases and change
manually the font?
i still dont understand...If i create a new project in 2.5, the Tedit dont
assume the parentfont=F.
Sorry for anything...
Thanks!
"Jose F. Gimenez" escreveu na mensagem news:4eef3560$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
Ricardo,
> I send in attach one example that was created in xailer 2.4.4. But when
> open
> in 2.5 you'll see that the Tedit it's bold.
Thanks for the sample. I've been reviewing it, and the problem is that
the TEdit control has an undefined font. That is, if you open the .xfm
file, you'll see that the TEdit control has lParentFont := .F., but
there is no font assigned to it, so it's undefined.
There was a bug in previous versions of Xailer, exactly in that case,
when lParentFont := .F. and the current font is the same as the form's
one. In this case, Xailer didn't save the font assignment to the
control. Now, Xailer 2.5 does. Sorry for any inconvenience.
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

[jfgimenez]

Ricardo,
> So what you're saying that's necessary go to all this cases and
> change manually the font?
>
> i still dont understand...If i create a new project in 2.5, the Tedit
> dont assume the parentfont=F.
The difference between Xailer <=2.4 and 2.5 is that both saves the .xfm
in different ways in that specific case. That is, when a container
control has a different font than the form, and a child control has
again the same font than the form.
F.e.: a form has "MS Sans Serif, 8, normal", a groupbox has "MS Sans
Serif, 8, bold" and a label into the groupbox has the same font as the
form "MS Sans Serif, 8, normal". In this case, Xailer <=2.4 generates
the code for the label by setting lParentFont := .F., but fails to
detect that the font is different than its parent (due to a incorrect
comparision to the form's font), so, it doesn't saves the code to create
the font. ITOH, Xailer 2.5 does it correctly, saving both properties
lParentFont and oFont.
However, we've just made a change to handle this case, and now, when a
control has lParentFont := .F. and hasn't a font assigned, the form's
font is used. So, in your sample, the tedit will be shown in normal font
(not bold).
We'll publish the update ASAP.
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info

[ricardo.pinto]

Thanks for all the help Jose.
Regards,
Ricardo Pinto
"Jose F. Gimenez" escreveu na mensagem news:4ef1bd58$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
The difference between Xailer <=2.4 and 2.5 is that both saves the .xfm
in different ways in that specific case. That is, when a container
control has a different font than the form, and a child control has
again the same font than the form.
F.e.: a form has "MS Sans Serif, 8, normal", a groupbox has "MS Sans
Serif, 8, bold" and a label into the groupbox has the same font as the
form "MS Sans Serif, 8, normal". In this case, Xailer <=2.4 generates
the code for the label by setting lParentFont := .F., but fails to
detect that the font is different than its parent (due to a incorrect
comparision to the form's font), so, it doesn't saves the code to create
the font. ITOH, Xailer 2.5 does it correctly, saving both properties
lParentFont and oFont.
However, we've just made a change to handle this case, and now, when a
control has lParentFont := .F. and hasn't a font assigned, the form's
font is used. So, in your sample, the tedit will be shown in normal font
(not bold).
We'll publish the update ASAP.
Regards,
Jose F. Gimenez
http://www.xailer.com
http://www.xailer.info