Jump to content

TurboMagic

Members
 View Profile  See their activity

  • Content Count

    235

  • Joined

  • Last visited

  • Days Won

    9

Posts posted by TurboMagic

  1. Posted

    I do know that leak reporting normally works, but it doesn't in this specific project. The project is a bigger one with
    a 5-digit number of LOC so creating a minimal demo, as much as I understand why you want it, is not so easy.

     

    Are there any known issues which can interfere with it?

    We already checked and confirmed that there is only one ReportMemoryLeaksOnShutdown := true; line as first line
    in the dpr's main program.

     

    We also tried FastMM491 and included FastMM4 ias first unit in the dpr's uses clause, but it didn't change anything.
    We also had tried V4.97, but that did not compile. There was some data type mismatch somewhere.

  3. Posted

    Hello,

     

    we have a Tokyo based Win32 project where ReportMemoryLeaksOnShutdown := true; as first line in the dpr does not lead to any leaks being reported on shutdown of the program,

    even if we force a leak in FormCLose of the main form (we can prove that the lines are executed there.

     

    In a small test application memory leak reporting works fine.

     

    What can this be?

    In the same project something has gone wrong with FastMM4 anyway. Small rpointer of records (size 12 bytes) do consume over 1K RAM each!

    Any clue what this could be? If extracted into the small test project it doesn't consume too much RAM. Same data type, same loop etc.

     

    Best regards

    TurboMagic

  5. Posted

    On 5/1/2019 at 10:08 AM, Dalija Prasnikar said:

    Android officially does not have splash screen support. Various frameworks only simulate splash screen while they load...  so just use sizes Delphi asks and that should be it,

     

    The best is to use simple logo centered on black background (similar to default FMX splash). It is the least intrusive and will look good on various setups. If your application needs longer initialization, then make main FMX form as light as possible and then implement proper splash inside that can show progress and can be better customized.

    The problem is, that it's not me who decides how the splash screen looks like. The other app is done in a different technology and uses different resolutions, so it's a bit hard for me to design a splash screen which looks similar enough from the logo and icon sizes of these elements on the splash screen. It would be a further argument for unification of development tools. Sigh!

  6. Posted

    Hello,

     

    thanks for the links provided.

    Some questions:

     

    You talk about approved image sizes and when I look at the path mentioned by you I see the resolutions the IDE project settings offer.

    But what does approved mean? Approved by whom? EMBT or Android or...?

    Or asked differently: why does a different development environment use different sizes?

    Who approved those? 😉

    Isn't there some official standard as it is standard to have these ldpi, mdpi, hdpi etc. folders in the apk containing the various resolutions,
    but aren't those resolutions "fixed" somewhere?

  7. Posted

    Hello,

     

    some question regarding Android splash screens. Delphi defines exact pixel sizes for these graphics.

    But where do they come from? Some colleague has written an app (in some web app framework)

    which uses completely different resolutions for those splash screens and if one tries to make similar
    looking one for my app this is quite cumbersome.

     

    These are the resolutions used by the other framework:

     

    200x320

    320x480
    480x800
    720*1280
    960*1600
    1280x1920

     

    TurboMagic

×