Am I missing something here? #Seattle VCL

-
Am I missing something here? #Seattle  VCL

I have form2 which inherits  from form1. form1 has font.size = 14. form2 overrides this and sets it to 12.

I create form3 which inherits from form2 (using the File/New/Other/Inheritable Items) and form3 is created with font.size = 15.

why?

Comments

  1. Juan C. CillerueloJanuary 14, 2016 at 11:15 AM

    I've solved this, in FMX, setting manually the font to a decimal number. Try it. Set the font of the form2 to 12.01 by example.

    ReplyDelete
  2. David HeffernanJanuary 15, 2016 at 1:07 AM

    Juan C. Cilleruelo How would that be relevant for a VCL project? And why 12.01? Sounds like voodoo.

    ReplyDelete
  3. Juan C. CillerueloJanuary 15, 2016 at 1:38 AM

    David Heffernan

    I've suggested this solution because in FMX works well.

    First, in FMX the property size of the font admits decimals. I have not time to check this in VCL, sorry.

    Now. In FMX, each platform has a default font size. If in the platform that you designs, you leave the default font size, in the others platforms, when you deploy the program, can see that the font size has been changed by the default size of this other platform. And in many cases is different.

    If the default value of the property is 12, I assign 12.01. This makes that "this is not the default value", and more, in other platforms, it going to be 12.01 too. And in true type fonts, the difference between 12 and 12.01 is... nothing!

    I compile for Windows 8.1 and Windows 10 and Mac OS X, all my developments.

    I like to see all the versions with the same types. ;)

    I wait that this explanation can be understand.

    ReplyDelete
  4. David HeffernanJanuary 15, 2016 at 2:23 AM

    This is voodoo. And FMX voodoo to boot.

    ReplyDelete
  5. Juan C. CillerueloJanuary 15, 2016 at 2:52 AM

    I agree. There are a lot of things in FMX that seems voodoo. (jejeje)

    But surprisingly, it works well!

    ReplyDelete

Post a Comment