Have been using XE2 for Windows FMX projects. Stuck to its GDI+ mode from the very beginning because of issues with Firemonkey's Direct2D support.

-
Have been using XE2 for Windows FMX projects. Stuck to its GDI+ mode from the very beginning because of issues with Firemonkey's Direct2D support.

I was wondering what has changed between XE2 and Berlin, wrt FMX GDI+ speed and improvements in Direct2D support. Are there any overall changes in speed? (only wrt Windows)

Anyone who has been busy with Windows FMX (2D) projects who can enlighten me about what to expect when switching to Berlin?

(I've perused the QP to find issues, but that turned out to be a bad idea if you're out to find good news)

Thanks for sharing your experiences.

Comments

  1. Christen Blom-DahlJuly 19, 2018 at 7:49 AM

    Firemonkey has changed a lot since XE2. Yo could check the new Community version and see the changes yourself.

    ReplyDelete
  2. Dominique WillemsJuly 19, 2018 at 8:13 AM

    That's what I'm planning. There are a lot of changes, I'm sure. Just curious about people's experiences with it.

    ReplyDelete
  3. Douglas RuddJuly 19, 2018 at 10:56 AM

    The latest FMX is light years ahead of XE2. Less bugs. Less workarounds. I used to have to fiddle with graphic settings to get something that worked. Now the graphics just work out of the box.

    ReplyDelete
  4. Dominique WillemsJuly 19, 2018 at 2:47 PM

    Douglas Rudd Have you experienced any issues with Direct2D?

    ReplyDelete
  5. Douglas RuddJuly 19, 2018 at 4:41 PM

    Dominique Willems In Tokyo, as far as I know it defaults to Direct2D and I haven't noticed anything wrong in Windows 10.

    ReplyDelete
  6. Dominique WillemsJuly 20, 2018 at 2:12 AM

    Douglas Rudd Excellent news. Looking forward to checking it out.

    ReplyDelete
  7. Dominique WillemsAugust 28, 2018 at 8:47 AM

    Douglas Rudd It does default to Direct2D, but does it default to using the GPU? I thought it was the OS that decided whether hardware is used or not, but apparently there is a GlobalUseGPUCanvas boolean to be set when targeting Windows. Documentation is not all too clear about its advantages, or whether there is any speed to be gained.

    ReplyDelete
  8. Dominique WillemsAugust 28, 2018 at 9:00 AM

    Douglas Rudd Interesting. Besides it just discarding all of my BindingNames, it has decided to draw all controls' TCanvas operations with Form offsets (not the relative ones inside the objects). It's a huge mess. Transitioning from XE2 is turning out to be a gigantic nightmare.

    ReplyDelete
  9. Douglas RuddAugust 28, 2018 at 1:37 PM

    Dominique Willems The binding names stuff has probably changed since XE2.
    Its not my fault you were using an ancient Delphi with an ancient computer with an 80 character screen.

    ReplyDelete
  10. Dominique WillemsAugust 28, 2018 at 1:53 PM

    Douglas Rudd LOL! This TRS-80 has 64 characters, and nobody will ever need more than that.

    ReplyDelete

Post a Comment