Jump to content

Uwe Raabe

Members
 View Profile  See their activity

  • Content Count

    2538

  • Joined

  • Last visited

  • Days Won

    145

Posts posted by Uwe Raabe

  5. Posted

    If I understand this paragraph correctly

    Quote

    Customers who have installed RAD Studio 12 using the ISO can continue to use that version, add platforms to it via the ISO, and use GetIt to add additional packages to the installation.

    Customers who have installed RAD Studio 12 using the online installation process won’t have the ability to add new platforms and core features to the product via the Manage Features dialog. In order to do this, they will need to uninstall and then reinstall using the new inline release.

    you still need to install from the ISO or wait for the inline release.

    • Thanks 1

  12. Posted

    It boils down to the fact that 'THIS' just is not the upper case of 'This' on every locale. In case this is a requirement of the application, then ToUpper is not the right choice. Unfortunately ToUpperInvariant may not be either, although it will probably work for pure English text strings.

     

    For most locales upper case for ASCII characters is what one would expect, but that doesn't hold true for Turkish.

  18. Posted

    3 hours ago, PeterPanettone said:

    Is that normal?

    Looks like a bit much. It depends on the number of design time packages. Anyway, it should not have changed unless you installed a bunch of new ones.

     

    There already exists a feature request to move that into a thread.

    • Thanks 1

  25. Posted

    56 minutes ago, PeterPanettone said:

    This faulty behavior occurs only if MMX is loaded AND with the "MainProgramWindowManager" unit! (If both conditions are NOT met, clicking the SAVE button turns the SAVE-ALL icon grey: Checked and re-checked just now).

    That is probably caused by the IDE or whatever catching the failing assertion during save of that unit. While MMX logs such an assertion it should nevertheless popup.

     

    1 hour ago, PeterPanettone said:

    This points to the same error from the previous MMX error message dialog (EAssertionFailed in CustomPascalExplorer.pas), thus proving that MMX prevents the project from being compiled or built.

    I have uploaded a new beta catching this assertion and writing it to CodeSite. So if you reproducibly get that exception now, you should get a CodeSite message with the new beta - unless the underlying object instance is no longer valid, which would move the spot to a completely different source location.

     

    What puzzles me is that this assertion failure nor any other exception is not logged to CodeSite. After all the MMX beta hooks into AssertErrorProc as well as Application.OnException. Can you disable the JCL exception handler as well as any other ones interfering with MMX here - at least for the time needed to investigate this?

×