{"id":13571,"date":"2026-06-24T15:31:35","date_gmt":"2026-06-24T13:31:35","guid":{"rendered":"https:\/\/maenken.systems\/download-area\/"},"modified":"2026-11-12T11:00:30","modified_gmt":"2026-11-12T10:00:30","slug":"download-area","status":"publish","type":"page","link":"https:\/\/maenken.systems\/en\/download-area\/","title":{"rendered":"Download Area"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-page\" data-elementor-id=\"13571\" class=\"elementor elementor-13571 elementor-12969\" data-elementor-post-type=\"page\">\n\t\t\t\t<div class=\"elementor-element elementor-element-475aebb e-con-full elementor-hidden-mobile e-flex e-con e-parent\" data-id=\"475aebb\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t<div class=\"elementor-element elementor-element-4c2a514 e-flex e-con-boxed e-con e-child\" data-id=\"4c2a514\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t<div class=\"elementor-element elementor-element-ca8faa3 e-con-full e-flex e-con e-child\" data-id=\"ca8faa3\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-140ead7 elementor-widget elementor-widget-elementskit-heading\" data-id=\"140ead7\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"elementskit-heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"ekit-wid-con\" ><div class=\"ekit-heading elementskit-section-title-wraper text_left   ekit_heading_tablet-   ekit_heading_mobile-\"><h2 class=\"ekit-heading--title elementskit-section-title \">Maenken Systems  <span>Components<\/span><\/h2><h3 class=\"ekit-heading--subtitle elementskit-section-subtitle  \">\n\t\t\t\t\t\tDownload Center\n\t\t\t\t\t<\/h3><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-63e2dc8 e-con-full e-flex e-con e-child\" data-id=\"63e2dc8\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-0b04d60 elementor-widget elementor-widget-spacer\" data-id=\"0b04d60\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"spacer.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"elementor-spacer\">\n\t\t\t<div class=\"elementor-spacer-inner\"><\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-f535814 e-con-full elementor-hidden-widescreen elementor-hidden-desktop elementor-hidden-tablet e-flex e-con e-parent\" data-id=\"f535814\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t<div class=\"elementor-element elementor-element-a278b1a e-con-full e-flex e-con e-child\" data-id=\"a278b1a\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-c468d65 elementor-widget elementor-widget-heading\" data-id=\"c468d65\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">MSys Component<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-3d6d583 elementor-widget elementor-widget-elementskit-fancy-animated-text\" data-id=\"3d6d583\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"elementskit-fancy-animated-text.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"ekit-wid-con\" >            <h3 class=\"ekit-fancy-text letters rotate-3\" data-id=\"3d6d583\" data-animation-settings=\"{&quot;animationStyle&quot;:&quot;animated&quot;,&quot;animationDelay&quot;:3000,&quot;loadingBar&quot;:3800,&quot;lettersDelay&quot;:50,&quot;typeLettersDelay&quot;:150,&quot;duration&quot;:500,&quot;revealDuration&quot;:600,&quot;revealAnimationDelay&quot;:1500}\">\n                \t\t\t\t<span class=\"ekit-fancy-text-lists \">\n\t\t\t\t\t\t\t\t\t\t<b class=\"ekit-fancy-text elementor-repeater-item-22e0158 is-visible\">Delphi Tools<\/b>\n\t\t\t\t\t\t\t\t\t\t<b class=\"ekit-fancy-text elementor-repeater-item-bf83cf4 \">Plug-In&#039;s<\/b>\n\t\t\t\t\t\t\t\t\t\t<b class=\"ekit-fancy-text elementor-repeater-item-5bd96e1 \">Addon&#039;s<\/b>\n\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t            <\/h3>\n        <\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-cff1be6 elementor-widget__width-initial elementor-widget elementor-widget-text-editor\" data-id=\"cff1be6\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Download Center<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<main class=\"elementor-element elementor-element-5bb5488 e-con-full e-flex e-con e-parent\" data-id=\"5bb5488\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t<div class=\"elementor-element elementor-element-8e72684 elementor-hidden-mobile e-con-full elementor-hidden-tablet e-flex e-con e-child\" data-id=\"8e72684\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-6a052b2 elementor-widget elementor-widget-spacer\" data-id=\"6a052b2\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"spacer.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"elementor-spacer\">\n\t\t\t<div class=\"elementor-spacer-inner\"><\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-bd2377a e-con-full e-flex e-con e-child\" data-id=\"bd2377a\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-c39adf5 elementor-widget elementor-widget-heading\" data-id=\"c39adf5\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h1 class=\"elementor-heading-title elementor-size-default\">MSys Download Center<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-bd03c33 elementor-widget elementor-widget-heading\" data-id=\"bd03c33\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">MSys Tools zum Download<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-6aa3a52 e-con-full e-flex e-con e-child\" data-id=\"6aa3a52\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-51f2d6f elementor-widget elementor-widget-text-editor\" data-id=\"51f2d6f\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>In this section, you will find software components provided by us available for download. Download the applications, extensions and tools you need quickly and easily, and benefit from our high-performance solutions.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/main>\n\t\t<div class=\"elementor-element elementor-element-81a9a07 e-flex e-con-boxed e-con e-parent\" data-id=\"81a9a07\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-element elementor-element-9b5f1e9 elementor-widget elementor-widget-elementskit-heading\" data-id=\"9b5f1e9\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"elementskit-heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"ekit-wid-con\" ><div class=\"ekit-heading elementskit-section-title-wraper text_center   ekit_heading_tablet-   ekit_heading_mobile-\"><h3 class=\"elementskit-section-subtitle  \">\n\t\t\t\t\t\tMaenken System powered Plug-Ins\n\t\t\t\t\t<\/h3><h2 class=\"ekit-heading--title elementskit-section-title text_fill\">MSys <span>Downloads<\/span><\/h2><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<main class=\"elementor-element elementor-element-7141042 e-flex e-con-boxed e-con e-parent\" data-id=\"7141042\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;shape_divider_top&quot;:&quot;opacity-tilt&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t\t<div class=\"e-con-inner\">\n\t\t\t\t<div class=\"elementor-shape elementor-shape-top\" aria-hidden=\"true\" data-negative=\"false\">\n\t\t\t<svg xmlns=\"http:\/\/www.w3.org\/2000\/svg\" viewBox=\"0 0 2600 131.1\" preserveAspectRatio=\"none\">\n\t<path class=\"elementor-shape-fill\" d=\"M0 0L2600 0 2600 69.1 0 0z\"\/>\n\t<path class=\"elementor-shape-fill\" style=\"opacity:0.5\" d=\"M0 0L2600 0 2600 69.1 0 69.1z\"\/>\n\t<path class=\"elementor-shape-fill\" style=\"opacity:0.25\" d=\"M2600 0L0 0 0 130.1 2600 69.1z\"\/>\n<\/svg>\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-8524525 elementor-widget elementor-widget-elementskit-heading\" data-id=\"8524525\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"elementskit-heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"ekit-wid-con\" ><div class=\"ekit-heading elementskit-section-title-wraper text_center   ekit_heading_tablet-   ekit_heading_mobile-\"><h3 class=\"elementskit-section-subtitle  \">\n\t\t\t\t\t\tMSys Download Center\n\t\t\t\t\t<\/h3><h2 class=\"ekit-heading--title elementskit-section-title text_fill\">Developer  <span>Tools<\/span><\/h2><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-26bbcdb e-con-full e-grid e-con e-child\" data-id=\"26bbcdb\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;background_motion_fx_motion_fx_scrolling&quot;:&quot;yes&quot;,&quot;background_motion_fx_opacity_effect&quot;:&quot;yes&quot;,&quot;background_motion_fx_opacity_direction&quot;:&quot;in-out&quot;,&quot;background_motion_fx_opacity_level&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:8.2,&quot;sizes&quot;:[]},&quot;background_motion_fx_opacity_range&quot;:{&quot;unit&quot;:&quot;%&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:{&quot;start&quot;:35,&quot;end&quot;:100}},&quot;background_motion_fx_scale_effect&quot;:&quot;yes&quot;,&quot;background_motion_fx_scale_direction&quot;:&quot;in-out-in&quot;,&quot;background_motion_fx_scale_speed&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:10,&quot;sizes&quot;:[]},&quot;background_motion_fx_scale_range&quot;:{&quot;unit&quot;:&quot;%&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:{&quot;start&quot;:32,&quot;end&quot;:100}},&quot;background_motion_fx_devices&quot;:[&quot;widescreen&quot;,&quot;desktop&quot;,&quot;tablet&quot;,&quot;mobile&quot;],&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-8718c51 elementor-widget elementor-widget-elementskit-heading\" data-id=\"8718c51\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"elementskit-heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"ekit-wid-con\" ><div class=\"ekit-heading elementskit-section-title-wraper text_center   ekit_heading_tablet-   ekit_heading_mobile-\"><h3 class=\"elementskit-section-subtitle  \">\n\t\t\t\t\t\tPlug-In Suite for Delphi\n\t\t\t\t\t<\/h3><h2 class=\"ekit-heading--title elementskit-section-title text_fill\">MSys Tool Suite for <span>Delphi RAD<\/span><\/h2><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-7b4a683 e-con-full e-flex e-con e-child\" data-id=\"7b4a683\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;gradient&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-5912dd7 elementor-widget elementor-widget-text-editor\" data-id=\"5912dd7\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Delphi 13.2<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-f64269e e-con-full e-flex e-con e-child\" data-id=\"f64269e\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t<div class=\"elementor-element elementor-element-e4cc4b0 e-con-full e-flex e-con e-child\" data-id=\"e4cc4b0\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-f3539df elementor-widget elementor-widget-msysdl_history\" data-id=\"f3539df\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_history.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"msysdl-history\" data-msysdl-history><button type=\"button\" class=\"msysdl-history__open\" aria-haspopup=\"dialog\">Release notes<\/button><div class=\"msysdl-history__modal\" role=\"dialog\" aria-modal=\"true\" aria-labelledby=\"msysdl-hist-title-1\" hidden><div class=\"msysdl-history__backdrop\" data-msysdl-close><\/div><div class=\"msysdl-history__dialog\" role=\"document\" tabindex=\"-1\"><button type=\"button\" class=\"msysdl-history__close\" data-msysdl-close aria-label=\"Close\">&times;<\/button><h2 class=\"msysdl-history__title\" id=\"msysdl-hist-title-1\">Version history<\/h2><ul class=\"msysdl-history__list\"><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.9.13.539<\/span><span class=\"msysdl-history__date\">26. October 2026 14:05<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version setzt den Code-Review der Suite fort: In allen Werkzeugen sind weitere Fehler behoben, die er zutage gef\u00f6rdert hat. Neu ist ein Plugin f\u00fcr Claude Code, das der MSYS Delphi MCP Server beim Einrichten eines Projekts mitbringt. Alle Werkzeuge der Suite tragen einheitlich die Hauptversion 1.9.<\/p>\n<h2 id=\"msysdl-cl-1-inhalt\" class=\"MD_h2\">Inhalt<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Project ToDos, mit Kanban-Board<\/li>\n<li class=\"MD_li\">MSYS Delphi MCP Server<\/li>\n<li class=\"MD_li\">SBOM, mit den Kommandozeilenwerkzeugen SBomGen und GenSBOMReport<\/li>\n<li class=\"MD_li\">AutoReload<\/li>\n<li class=\"MD_li\">CodeSigner<\/li>\n<li class=\"MD_li\">SmartSetup<\/li>\n<li class=\"MD_li\">Buildmanager<\/li>\n<\/ul>\n<p class=\"MD_p\">Die Plugins lassen sich bei der Installation einzeln abw\u00e4hlen. Das Setup installiert die Suite f\u00fcr die 32- und die 64-Bit-IDE.<\/p>\n<h2 id=\"msysdl-cl-1-neuerungen\" class=\"MD_h2\">Neuerungen<\/h2>\n<h3 id=\"msysdl-cl-1-stabilit\u00e4t-und-fehlerbehebungen\" class=\"MD_h3\">Stabilit\u00e4t und Fehlerbehebungen<\/h3>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Andockbare Fenster und Editor-Ansichten der Plugins melden sich beim Entladen vollst\u00e4ndig ab. Ein Zugriff der IDE auf ein bereits entladenes Plugin ist damit ausgeschlossen.<\/li>\n<li class=\"MD_li\">Hilfetexte der Plugins f\u00fchren nicht mehr zu einem Absturz, wenn das Erscheinungsbild der IDE noch nicht bereitsteht.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SBOM<\/strong><ul class=\"MD_ul\">\n<li class=\"MD_li\">SBomGen meldet einen Fehler bei der Erzeugung mit einem positiven Exit-Code; <code class=\"MD_code\">if errorlevel 1<\/code> in einem Build-Skript erkennt ihn jetzt.<\/li>\n<li class=\"MD_li\">Der PDF-Bericht druckt den Zeitstempel der SBOM, und ein langer Kopfteil bricht sauber auf die n\u00e4chste Seite um.<\/li>\n<li class=\"MD_li\">Das Ergebnis einer SBOM-Pr\u00fcfung wird nicht mehr stillschweigend gek\u00fcrzt.<\/li>\n<li class=\"MD_li\">Fehler beim Lesen einer MAP-Datei nennen im Protokoll Datei und Ursache; gro\u00dfe MAP-Dateien werden schneller ausgewertet.<\/li>\n<\/ul>\n<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">CodeSigner:<\/strong> Scheitert nur der Zeitstempeldienst, bleibt die Datei unsigniert, statt eine Signatur ohne Zeitstempel zu tragen. Die Pr\u00fcfung nach dem Signieren schlie\u00dft den Zeitstempel ein und nennt bei einem Abbruch den Grund.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project ToDos:<\/strong> Eine Kanban-Datei mit unerwarteten Eintr\u00e4gen l\u00e4sst das Board nicht mehr ohne Spalten zur\u00fcck, und ein Fehler im Board rei\u00dft das Plugin nicht mehr mit. \u00c4nderungen an den Notizen einer Aufgabe werden \u00fcberall erkannt.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SmartSetup:<\/strong> Der Hilfe-Ballon zeigt immer die Angaben des Produkts, \u00fcber dem er steht. Schl\u00e4gt die Abfrage der Zugangsdaten fehl, zeigt das Fenster keine ungefilterte Ausgabe des Kommandozeilenwerkzeugs mehr.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Buildmanager:<\/strong> Versionsnummern \u00fcber 65535 und doppelte Versionsangaben in Projekt- und Gruppendateien werden gemeldet statt \u00fcbernommen.<\/li>\n<\/ul>\n<h3 id=\"msysdl-cl-1-msys-delphi-mcp-server\" class=\"MD_h3\">MSYS Delphi MCP Server<\/h3>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEU:<\/strong> Claude-Code-Plugin \u201edelphi-ide-mcp\". <em class=\"MD_em\">Projekt einrichten<\/em> legt es neben die <code class=\"MD_code\">.mcp.json<\/code> des Arbeitsbereichs. Es bringt die Skills des Servers in jede Claude-Code-Sitzung dieses Ordners und l\u00e4sst den Server pr\u00fcfen, bevor Claude Code eine Delphi-Quelle an der IDE vorbei schreibt oder einen Compiler aus der Kommandozeile startet. Claude Code l\u00e4dt das Plugin erst, wenn Sie dem Ordner dort einmal vertraut haben.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">designer_add_component<\/code> l\u00e4sst die aktive Seite eines PageControls unver\u00e4ndert, wenn die neue Komponente auf eine Registerseite kommt.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">db_sql<\/code> lehnt im Lesemodus auch schreibende Anweisungen hinter <code class=\"MD_code\">WITH<\/code> und <code class=\"MD_code\">SELECT \u2026 INTO OUTFILE<\/code> ab.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">project_add_file<\/code> und <code class=\"MD_code\">project_remove_file<\/code> erhalten Kommentare zwischen den <code class=\"MD_code\">{$R}<\/code>-Direktiven der Projektdatei.<\/li>\n<li class=\"MD_li\">Das Lesen des Meldungsfensters kann die IDE nicht mehr einfrieren.<\/li>\n<li class=\"MD_li\">Die Skills des Servers werden auch gefunden, wenn die Umgebungsvariable <code class=\"MD_code\">PROGRAMDATA<\/code> fehlt.<\/li>\n<li class=\"MD_li\">Dazu mehrere Korrekturen an der Absicherung paralleler Zugriffe.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-1-hinweise-zur-installation\" class=\"MD_h2\">Hinweise zur Installation<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Schlie\u00dfen Sie RAD Studio vor der Installation; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Das Setup braucht ein 64-Bit-Windows und Administratorrechte.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.8.12.537<\/span><span class=\"msysdl-history__date\">16. October 2026 14:29<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version ist ein Stabilit\u00e4ts- und Qualit\u00e4ts-Release. Am deutlichsten merken Sie das beim Schlie\u00dfen von RAD Studio: Die IDE st\u00fcrzt mit geladenen Plugins nicht mehr ab. Die erzeugten Software-St\u00fccklisten (SBOM) folgen jetzt dem Standard CycloneDX 1.7. Alle Werkzeuge der Suite tragen einheitlich die Hauptversion <strong class=\"MD_strong\">1.8<\/strong>.<\/p>\n<h2 id=\"msysdl-cl-2-1-stabilit\u00e4t-und-fehlerbehebungen\" class=\"MD_h2\">1. Stabilit\u00e4t und Fehlerbehebungen<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Beim Schlie\u00dfen von RAD Studio mit geladenen MSYS-Plugins kam es zu einem Absturz. Das ist behoben.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">AutoReload:<\/strong> Eine angeforderte Neuladung wirkt jetzt zuverl\u00e4ssig.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SmartSetup:<\/strong> Fehler bleiben auf das Produktfenster beschr\u00e4nkt und rei\u00dfen die IDE nicht mehr mit; dazu weitere Korrekturen im Produktfenster.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SBOM:<\/strong> mehrere Korrekturen im Editor und beim Einlesen aus Git \u2014 unter anderem wird ein auf den aktuellen Stand gesetzter Git-Tag jetzt \u00fcbernommen.<\/li>\n<li class=\"MD_li\">Dazu zahlreiche kleinere Korrekturen in Host und Plugins, die der Code-Review zutage gef\u00f6rdert hat.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-2-2-sbom--st\u00fccklisten-nach-cyclonedx-17\" class=\"MD_h2\">2. SBOM \u2014 St\u00fccklisten nach CycloneDX 1.7<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die erzeugten SBOMs folgen in allen Ausgabewegen dem Standard CycloneDX 1.7 und werden streng dagegen gepr\u00fcft.<\/li>\n<li class=\"MD_li\">Vollst\u00e4ndigere Lizenzangaben in den erzeugten St\u00fccklisten.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-2-3-msys-delphi-mcp-server--verbesserungen\" class=\"MD_h2\">3. MSYS Delphi MCP Server \u2014 Verbesserungen<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEU:<\/strong> <code class=\"MD_code\">project_add_config<\/code> und <code class=\"MD_code\">project_remove_config<\/code> legen Build-Konfigurationen eines Projekts an und entfernen sie.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEU:<\/strong> <code class=\"MD_code\">designer_clear_event<\/code> entfernt die Zuordnung eines Ereignisses im Formular-Designer.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">editor_close_file<\/code> kann die Datei vor dem Schlie\u00dfen speichern.<\/li>\n<li class=\"MD_li\">Das Ausgabeverzeichnis f\u00fcr BPL und DCP eines Projekts l\u00e4sst sich lesen und setzen; ebenso die Optionen des Ressourcen-Compilers.<\/li>\n<li class=\"MD_li\">Compiler-Meldungen kommen jetzt verl\u00e4sslich aus dem Datenmodell der IDE.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project ToDos:<\/strong> Die \u00c4nderungspr\u00fcfung ber\u00fccksichtigt auch die Beschreibung und die Notizen einer Aufgabe.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-2-4-setup\" class=\"MD_h2\">4. Setup<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der MSys CodeSign Buildhost wird nicht mehr mit der Suite ausgeliefert. Signiert wird \u00fcber den MSys CodeSign Server.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-2-5-hinweise-zum-upgrade\" class=\"MD_h2\">5. Hinweise zum Upgrade<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Schlie\u00dfen Sie RAD Studio vor der Installation<\/strong>; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Haben Sie mit Version 1.7 den MSys CodeSign Buildhost \u00fcber das Setup installiert, bleibt er als eigenes Produkt bestehen. Dieses Setup liefert ihn nicht mehr mit; das Signieren l\u00e4uft unver\u00e4ndert \u00fcber den MSys CodeSign Server.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.7.12.531<\/span><span class=\"msysdl-history__date\">12. October 2026 11:08<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">This version brings a new tool for anyone who builds a project for several platforms and configurations: the <strong class=\"MD_strong\">Build Manager<\/strong>. The <strong class=\"MD_strong\">MSYS Delphi MCP Server<\/strong> can operate it as well and has become considerably more reliable with long builds and changes to project files. All tools in the suite now share the major version <strong class=\"MD_strong\">1.7<\/strong>.<\/p>\n<h2 id=\"msysdl-cl-3-1-new-msys-build-manager--build-profiles-for-projects-and-groups\" class=\"MD_h2\">1. NEW: MSYS Build Manager \u2014 build profiles for projects and groups<\/h2>\n<p class=\"MD_p\">If you build a project for several platforms and configurations, you now define this once as a profile and start it with a single click.<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">A <strong class=\"MD_strong\">project profile<\/strong> selects from platform \u00d7 configuration, for example Win32 and Win64, each in Release.<\/li>\n<li class=\"MD_li\">A <strong class=\"MD_strong\">group profile<\/strong> combines the project profiles of a project group and builds them in the group's order.<\/li>\n<li class=\"MD_li\">Clean, Compile and Build are started from a dockable window. After the run, the previously active platform and configuration are restored.<\/li>\n<li class=\"MD_li\">A run can be cancelled; for each step you see errors, warnings and hints.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Version numbers<\/strong> can be set per project or for the whole group. The Build Manager writes them into the project before each build, so all platforms of a run carry the same number; if desired, it increments the build number automatically.<\/li>\n<li class=\"MD_li\">The profiles are stored in the <code class=\"MD_code\">.dproj<\/code> or <code class=\"MD_code\">.groupproj<\/code> file and go into version control together with the project.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-3-2-msys-delphi-mcp-server--improvements\" class=\"MD_h2\">2. MSYS Delphi MCP Server \u2014 improvements<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW:<\/strong> Build profiles can be read, created, changed and started via the server (<code class=\"MD_code\">buildprofile_list<\/code>, <code class=\"MD_code\">_get<\/code>, <code class=\"MD_code\">_set<\/code>, <code class=\"MD_code\">_rename<\/code>, <code class=\"MD_code\">_remove<\/code>, <code class=\"MD_code\">_run<\/code>, <code class=\"MD_code\">_status<\/code>, <code class=\"MD_code\">_cancel<\/code>). The server status (<code class=\"MD_code\">server_status<\/code>) reports whether the Build Manager is loaded and whether profiles have been set up.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW:<\/strong> <code class=\"MD_code\">codesigner_get_config<\/code> and <code class=\"MD_code\">codesigner_set_config<\/code> read and set a project's signing settings. The tool <code class=\"MD_code\">code_sign_file<\/code> is now called <code class=\"MD_code\">codesigner_sign_file<\/code>.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Long builds:<\/strong> <code class=\"MD_code\">project_compile<\/code> responds after 240 seconds at the latest. If a build takes longer, it keeps running; the response says so, and the result appears in the suite's message window. Calls that need the IDE in the meantime receive a \"busy\" response including the running tool, instead of running into a seemingly hanging dialog.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project files:<\/strong> <code class=\"MD_code\">project_add_file<\/code> reports an IDE prompt immediately instead of waiting. <code class=\"MD_code\">project_rename_file<\/code> reports what the IDE actually did and updates the uses clause of all affected projects. Comments and the IDE's form creation code in the project file are preserved when adding, removing and renaming.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Form Designer:<\/strong> <code class=\"MD_code\">designer_delete_component<\/code> also deletes menu items. <code class=\"MD_code\">designer_get_components<\/code> shows menu items, actions and fields under their parent element and no longer lists internal helper objects. <code class=\"MD_code\">designer_set_event<\/code> also works with inherited forms.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project ToDos:<\/strong> Write access can be protected against intermediate changes. If someone else has changed a task in the meantime, nothing is overwritten.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">project_get_build_log<\/code> returns the end of the log, where the errors are. <code class=\"MD_code\">editor_save_all<\/code> and <code class=\"MD_code\">ide_get_open_modules<\/code> also detect projects with changed options as unsaved.<\/li>\n<li class=\"MD_li\">The bundled skills for AI assistants have been restructured: concise entry pages, with the details in separate files.<\/li>\n<li class=\"MD_li\">A memory leak in several tools has been fixed.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-3-3-setup\" class=\"MD_h2\">3. Setup<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">The Build Manager is included in the full setup and can be deselected individually in the component selection.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW:<\/strong> For the CodeSigner, the setup can also install the <strong class=\"MD_strong\">MSys CodeSign Buildhost<\/strong> \u2014 the connection to the MSys CodeSign Server (<code class=\"MD_code\">RemoteSigner.dll<\/code> for <code class=\"MD_code\">signtool \/dlib<\/code>, plus <code class=\"MD_code\">CodeSignJob.exe<\/code> and <code class=\"MD_code\">CodeSignConfigCLI.exe<\/code>). It is a separate product with its own entry under \"Apps &amp; Features\" and remains installed when the suite is uninstalled.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-3-4-also-new-since-the-last-release-1312526\" class=\"MD_h2\">4. Also new since the last release 1.3.12.526<\/h2>\n<p class=\"MD_p\">Version 1.5.12.531 added:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">32-bit and 64-bit IDE:<\/strong> The setup installs the tools for both IDEs of Delphi 13; each finds its own build, and both carry the same number.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW: MSYS SmartSetup<\/strong> \u2014 the TMS Smart Setup products in the IDE: a list with filters, a tile on the Welcome Screen, updating and installing directly from the IDE. Requires an existing installation of TMS Smart Setup (<code class=\"MD_code\">tms.exe<\/code>).<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">MCP Server:<\/strong> Calls with an unknown parameter are rejected; <code class=\"MD_code\">project_compile<\/code> can build a specific platform and configuration on request; <code class=\"MD_code\">project_set_platforms<\/code> toggles target platforms; <code class=\"MD_code\">text_search<\/code> understands regular expressions; line endings are always CRLF.<\/li>\n<li class=\"MD_li\">Project ToDos, SBOM Generator and the consistently English user interface with German translation \u2014 details in the setup's \"What's New\" file.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-3-5-upgrade-notes\" class=\"MD_h2\">5. Upgrade notes<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Close RAD Studio before installing<\/strong>; the setup checks for this.<\/li>\n<li class=\"MD_li\">An existing installation is overwritten; your settings are retained.<\/li>\n<li class=\"MD_li\">If you address the MCP server from scripts or your own instructions: <code class=\"MD_code\">code_sign_file<\/code> is now called <code class=\"MD_code\">codesigner_sign_file<\/code>.<\/li>\n<li class=\"MD_li\">If you don't need the MSys CodeSign Buildhost, deselect it in the component selection under the CodeSigner.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.5.12.531<\/span><span class=\"msysdl-history__date\">23. September 2026 10:49<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version l\u00e4uft zum ersten Mal auch in der 64-Bit-IDE von Delphi 13. Dazu kommt ein neues Werkzeug f\u00fcr TMS Smart Setup, und f\u00fcr einzelne Werkzeuge gibt es jetzt eigene, kleinere Setups.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: 32- und 64-Bit-IDE<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Delphi 13 gibt es als 32- und als 64-Bit-IDE. Das Setup installiert die Werkzeuge jetzt f\u00fcr beide: Jede IDE findet ihre eigene Fassung, und Sie k\u00f6nnen frei zwischen ihnen wechseln. Beide Fassungen tragen dieselbe Versionsnummer.<\/p>\n<p class=\"MD_p\">Alle Werkzeuge der Suite tragen ab dieser Version einheitlich die Hauptversion 1.5.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">NEU: MSYS SmartSetup \u2014 TMS-Produkte im Blick<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Wer Komponenten von TMS \u00fcber TMS Smart Setup bezieht, sieht jetzt in der IDE, welche Produkte es gibt, welche installiert sind und wo eine neuere Fassung bereitliegt.<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Eine gegliederte Liste mit Filtern (installiert, Update verf\u00fcgbar, Name, Server) zeigt Name, installierte und verf\u00fcgbare Version, Status, Lizenz und Server jedes Produkts.<\/li>\n<li class=\"MD_li\">Eine Kachel auf dem Welcome-Screen nennt die Zahl der Produkte, der installierten und der verf\u00fcgbaren Updates.<\/li>\n<li class=\"MD_li\">Aktualisieren und Installieren laufen direkt aus der IDE; die Ausgabe erscheint live im Meldungsfenster.<\/li>\n<\/ul>\n<p class=\"MD_p\">Voraussetzung ist eine vorhandene Installation von TMS Smart Setup (tms.exe); das Plugin bringt sie nicht mit.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">NEU: Einzelsetups<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Neben dem Gesamtsetup gibt es eigene Setups f\u00fcr den SBOM Generator, den CodeSigner und SmartSetup. Sie sind Teil desselben Produkts: Wer sp\u00e4ter das Gesamtsetup installiert, aktualisiert einfach, und eine Deinstallation entfernt alles gemeinsam.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">MSYS Delphi MCP Server \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Aufrufe mit einem unbekannten Parameter werden jetzt abgelehnt, statt den Parameter stillschweigend zu \u00fcbergehen. Ein Tippfehler im Parameternamen f\u00e4llt damit sofort auf.<\/li>\n<li class=\"MD_li\">NEU: project_compile baut auf Wunsch eine bestimmte Plattform und Konfiguration und stellt danach die vorherige wieder ein.<\/li>\n<li class=\"MD_li\">NEU: project<em class=\"MD_em\">set<\/em>platforms schaltet Zielplattformen eines Projekts ein und aus.<\/li>\n<li class=\"MD_li\">NEU: text_search versteht regul\u00e4re Ausdr\u00fccke und nimmt auch eine einzelne Datei als Suchort.<\/li>\n<li class=\"MD_li\">Zeilenenden sind immer CRLF: Bearbeitet ein Werkzeug eine Datei mit LF-Zeilenenden, wird sie durchgehend auf CRLF gebracht.<\/li>\n<li class=\"MD_li\">Zahlreiche Meldungen sind genauer geworden \u2014 etwa wenn ein gesuchter Text nur innerhalb einer Zeile vorkommt oder ein Projekt nicht aufger\u00e4umt werden kann, weil die IDE seine DLL geladen hat.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Weitere Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Project ToDos: Der Abh\u00e4ngigkeits-Streifen wird gr\u00fcn, sobald alle Blocker erledigt sind; Statusfilter und Beziehungen werden strenger gepr\u00fcft.<\/li>\n<li class=\"MD_li\">SBOM Generator: Speichern im SBOM-Editor funktioniert auch nach einem Dateiwechsel zuverl\u00e4ssig; System-DLLs werden passend zur Plattform aufgel\u00f6st, JSON-Dateien ohne BOM geschrieben.<\/li>\n<li class=\"MD_li\">Die Oberfl\u00e4che der Suite ist durchgehend englisch, mit deutscher \u00dcbersetzung.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.3.12.526<\/span><span class=\"msysdl-history__date\">16. September 2026 12:03<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version bringt ein neues Werkzeug mit: den CodeSigner, der Ihre fertigen Programme signiert, ohne dass Sie daran denken m\u00fcssen. Der zweite Schwerpunkt liegt beim SBOM Generator, der auf CycloneDX 1.7 umgestellt wurde und jetzt das BSI-Profil nach TR-03183-2 erzeugen und pr\u00fcfen kann.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: MSYS CodeSigner \u2014 signierte Auslieferung ohne Handgriff<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Unsignierte Software hat es unter Windows schwer: SmartScreen warnt, die Benutzerkontensteuerung meldet einen \u201eunbekannten Herausgeber\", und mancher Virenscanner schaut genauer hin. Das neue Plugin nimmt Ihnen den Schritt ab, der das verhindert.<\/p>\n<p class=\"MD_p\">Der CodeSigner signiert das Ergebnis eines Builds unmittelbar nachdem die IDE es erzeugt hat \u2014 mit Zeitstempel und anschlie\u00dfender Pr\u00fcfung. Signiert wird ausschlie\u00dflich, was Sie daf\u00fcr angemeldet haben:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Einmal pro Rechner hinterlegen Sie unter Tools &gt; Optionen &gt; MSys &gt; CodeSigner, womit signiert wird. Drei Wege stehen zur Wahl: Hardware-Token\/HSM, Zertifikatsdatei oder Azure Trusted Signing.<\/li>\n<li class=\"MD_li\">Pro Projekt entscheiden Sie unter MSys &gt; Code-Signierung f\u00fcr dieses Projekt\u2026, ob und in welchen Build-Konfigurationen signiert wird. Die Angabe wandert in die .dproj und gilt f\u00fcr jeden, der das Projekt baut.<\/li>\n<li class=\"MD_li\">Nach jedem Compile pr\u00fcft das Plugin vier Dinge: War der Build erfolgreich? Ist das Projekt angemeldet? Steht die gebaute Konfiguration auf der Liste? F\u00e4llt eines davon durch, passiert nichts.<\/li>\n<\/ul>\n<p class=\"MD_p\">Einzelne Dateien signieren Sie \u00fcber MSys &gt; Datei signieren\u2026 \u2014 auch solche, die nicht aus dem aktuellen Projekt stammen. Der Dialog sagt Ihnen vorab, ob dieser Rechner \u00fcberhaupt signieren kann.<\/p>\n<p class=\"MD_p\">Voraussetzung ist ein Code-Signing-Zertifikat und signtool.exe aus dem Windows SDK; beides bringen Sie mit, das Plugin benutzt, was auf Ihrem Rechner liegt. Ein ausf\u00fchrliches Handbuch finden Sie im Wiki des Projekts.<\/p>\n<p class=\"MD_p\">Der Azure-Zweig ist vollst\u00e4ndig eingebaut, aber mangels Konto noch nicht mit einem echten Dienst erprobt; die Options-Seite weist ihn deshalb als \u201e(vorbereitet)\" aus.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">MSYS SBOM Generator \u2014 CycloneDX 1.7 und das BSI-Profil<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der Generator erzeugt jetzt CycloneDX 1.7 statt 1.6. Das Schema wurde vollst\u00e4ndig ausgewertet und die Ausgabe lokal dagegen gepr\u00fcft.<\/li>\n<li class=\"MD_li\">NEU: Das Profil nach BSI TR-03183-2 l\u00e4sst sich einschalten. Es erg\u00e4nzt je Komponentenart die vom BSI geforderten Eigenschaften; die Werte sind im SBOM-Editor einstellbar.<\/li>\n<li class=\"MD_li\">NEU: Ein Validator pr\u00fcft eine SBOM gegen den CycloneDX-Kern und gegen die BSI-Anforderungen. Jeder Befund tr\u00e4gt eine Regel-Kennung, sodass nachvollziehbar ist, woran er h\u00e4ngt. Auch als Verb der Kommandozeilen-Werkzeuge verf\u00fcgbar \u2014 damit l\u00e4sst sich eine SBOM in der Build-Kette pr\u00fcfen.<\/li>\n<li class=\"MD_li\">Neben SHA-256 wird jetzt auch SHA-512 berechnet, in einem Lesedurchlauf.<\/li>\n<li class=\"MD_li\">Externe Module lassen sich als solche kennzeichnen: Wird ein Modul mitgeliefert oder auf dem Zielsystem vorausgesetzt? Liegt f\u00fcr ein externes Modul eine eigene SBOM vor, kann sie wahlweise referenziert statt eingebettet werden.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Delphi MCP Server \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">NEU: Das Werkzeug code<em class=\"MD_em\">sign<\/em>file l\u00e4sst eine beliebige Datei \u00fcber den CodeSigner signieren. Die Server-Auskunft (server_status) meldet zus\u00e4tzlich, ob der Signer geladen ist und ob dieser Rechner derzeit signieren kann.<\/li>\n<li class=\"MD_li\">Der Formular-Designer ist weiter bedienbar geworden: Seiten, Collections und Men\u00fc-Eintr\u00e4ge lassen sich jetzt ebenfalls anlegen und \u00e4ndern.<\/li>\n<li class=\"MD_li\">L\u00e4uft ein Werkzeug-Aufruf in eine Exception der Anwendung, h\u00e4lt der Debugger nicht mehr den ganzen Ablauf an \u2014 er setzt fort, wo das bisher eine R\u00fcckfrage erzwang.<\/li>\n<li class=\"MD_li\">Dialoge werden vollst\u00e4ndiger gemeldet: Der Fragetext fensterloser VCL-Steuerelemente kommt jetzt mit.<\/li>\n<li class=\"MD_li\">Der Server startet standardm\u00e4\u00dfig mit dem Plugin. Wer das nicht m\u00f6chte, schaltet es in den Optionen ab.<\/li>\n<li class=\"MD_li\">Zum Server gibt es ein ausf\u00fchrliches Benutzerhandbuch im Wiki des Projekts.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">NEU: Der Status \u201eTBD (zu besprechen)\u201c. Er h\u00e4lt fest, dass eine Aufgabe auf eine Entscheidung von Ihnen wartet \u2014 die h\u00e4ufigste Art, wie ein Vorgang liegen bleibt, ohne dass es auff\u00e4llt. Anders als \u201eZur\u00fcckgestellt\u201c blendet ihn kein Filter aus: Eine Frage, die auf Antwort wartet, soll sichtbar bleiben. Setzen k\u00f6nnen Sie ihn im Bearbeiten-Dialog, \u00fcber das Kontextmen\u00fc der Aufgabenliste oder indem Sie die Karte auf dem Board in die neue Spalte TBD ziehen. Bestehende Boards bekommen diese Spalte beim n\u00e4chsten \u00d6ffnen von selbst dazu. Auch der KI-Assistent am MCP-Server kennt ihn: Steht eine Entscheidung an, die nur Sie treffen k\u00f6nnen, legt er die Aufgabe dort ab und fragt nach, statt zu raten.<\/li>\n<li class=\"MD_li\">Beziehungen zwischen Aufgaben werden beim Speichern gegen den Bestand gepr\u00fcft. Eine Kennung, die es nicht gibt, wird abgelehnt statt stillschweigend \u00fcbernommen.<\/li>\n<li class=\"MD_li\">Der Bearbeiten-Dialog ist breiter geworden, damit die deutschen Beschriftungen vollst\u00e4ndig hineinpassen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Einrichtung: der MCP-Server meldet sich bei Kai an<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Das Setup tr\u00e4gt den MSYS-MCP-Server auf Wunsch in Kai ein, den KI-Assistenten von RAD Studio. Damit stehen die Werkzeuge des Servers dort ohne weitere Handgriffe zur Verf\u00fcgung.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Schlie\u00dfen Sie RAD Studio vor der Installation; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Der CodeSigner ist in der Komponentenauswahl des Setups abw\u00e4hlbar. Ohne eingerichtetes Zertifikat tut er nichts \u2014 er meldet sich erst, wenn Sie ein Projekt f\u00fcr die Signierung anmelden.<\/li>\n<li class=\"MD_li\">Bestehende SBOMs bleiben lesbar. Neu erzeugte SBOMs tragen die Version 1.7; wer sie in einem Werkzeug weiterverarbeitet, das nur 1.6 versteht, pr\u00fcft das bitte vorab.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.2.12.520<\/span><span class=\"msysdl-history__date\">26. August 2026 10:51<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version dreht sich um die Bedienung: Die gesamte Suite spricht jetzt die Sprache Ihrer IDE \u2014 auf einer deutschen RAD Studio-Installation also Deutsch, sonst Englisch. Und jedes Eingabefeld, dessen Wirkung nicht auf den ersten Blick klar ist, erkl\u00e4rt sich selbst: Der Mauszeiger gen\u00fcgt, und es erscheint ein formatierter Hilfetext.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: Die Oberfl\u00e4che folgt der Sprache Ihrer IDE<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Men\u00fcs, Dialoge, Options-Seiten, Fenstertitel und Meldungen der Suite liegen jetzt zweisprachig vor. Betroffen ist alles, was Sie sehen:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">das MSys-Men\u00fc und der Info-Dialog der Suite,<\/li>\n<li class=\"MD_li\">die Options-Seiten unter Tools &gt; Optionen &gt; MSys,<\/li>\n<li class=\"MD_li\">die andockbaren Fenster samt ihrer Titel (\"Projekt-Todos\", \"MCP-Server\", \"SBOM-Projekteditor\", \"Virtuelle SBOMs\", \u2026),<\/li>\n<li class=\"MD_li\">die Dialoge der einzelnen Plugins,<\/li>\n<li class=\"MD_li\">das Kanban-Board der Project ToDos, das bisher als eigenst\u00e4ndiges Fenster durchgehend englisch war.<\/li>\n<\/ul>\n<p class=\"MD_p\">Ausgew\u00e4hlt wird beim Start des jeweiligen Plugins anhand der IDE-Sprache. Ein Sprachwechsel in RAD Studio wirkt sich deshalb erst nach einem Neustart der IDE aus. Fehlt zu einem Text eine \u00dcbersetzung, erscheint er auf Englisch \u2014 ohne Fehlermeldung und ohne L\u00fccke in der Oberfl\u00e4che.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">NEU: Hilfetexte, die erkl\u00e4ren statt zu benennen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Wo bisher ein kurzer Tooltip den Feldnamen wiederholte, steht jetzt ein formatierter Hilfetext: mit \u00dcberschriften, Hervorhebungen, Listen und Tabellen. Er beschreibt nicht nur, was ein Feld ist, sondern was es bewirkt \u2014 einschlie\u00dflich der Nebenwirkungen, die man sonst erst nach dem Speichern bemerkt.<\/p>\n<p class=\"MD_p\">Zu finden an den Options-Seiten aller Plugins sowie an den Dialogen, die etwas Erkl\u00e4rungsbed\u00fcrftiges tun: dem SBOM-Editor und seinen Eingabemasken, der Server-Karte und dem Verbindungs-Editor des MCP-Servers, dem Bearbeiten- und Auswahl-Dialog der Project ToDos und dem Kanban-Board.<\/p>\n<p class=\"MD_p\">Das Popup bleibt stehen, solange der Mauszeiger auf dem Feld steht \u2014 diese Texte sind zum Lesen gedacht, nicht zum \u00dcberfliegen.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Delphi MCP Server \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die Server-Auskunft (server_status) f\u00fchrt jetzt die Suite selbst auf: die Host-Komponente und jedes geladene Plugin mit Name, Version, Hersteller und Beschreibung. Damit ist im KI-Werkzeug unmittelbar sichtbar, welcher Stand tats\u00e4chlich l\u00e4uft.<\/li>\n<li class=\"MD_li\">Formular-Designer: Neue Komponenten landen zuverl\u00e4ssig unter dem angegebenen \u00fcbergeordneten Element, und die Komponentenliste bildet die tats\u00e4chliche Verschachtelung ab statt einer flachen Aufz\u00e4hlung.<\/li>\n<li class=\"MD_li\">Das Speichern mehrerer ge\u00e4nderter Dateien bricht nicht mehr beim ersten Fehler ab, sondern behandelt jede Datei einzeln und meldet je Datei, was geschehen ist.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Das Kanban-Board ist vollst\u00e4ndig \u00fcbersetzt, samt seiner Gruppierungsliste, und hat die neuen Hilfetexte erhalten.<\/li>\n<li class=\"MD_li\">Die manuelle Sortierung erzeugt wieder gleichm\u00e4\u00dfig verteilte Sortierschl\u00fcssel; bisher wuchsen sie beim Einf\u00fcgen unn\u00f6tig in die L\u00e4nge.<\/li>\n<li class=\"MD_li\">Verwaltungsdateien des Boards (z. B. _kanban.json) werden beim Einlesen der Aufgaben \u00fcbergangen und tauchen nicht mehr als vermeintliches Todo auf.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">SBOM Generator \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der Editor merkt sich zuverl\u00e4ssig, welche Datei er gerade bearbeitet. Bisher konnte es nach einem Wechsel zwischen ge\u00f6ffneten Modulen vorkommen, dass beim Speichern der Inhalt in das zuvor bearbeitete Modul zur\u00fcckgeschrieben wurde.<\/li>\n<li class=\"MD_li\">Die Fenster \"Virtuelle SBOMs\" und \"Externe Module\" sind \u00fcbersetzt, einschlie\u00dflich der Spalten\u00fcberschriften.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Schlie\u00dfen Sie RAD Studio vor der Installation; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Die Sprache der Oberfl\u00e4che richtet sich nach der IDE. Wenn Sie die Sprache von RAD Studio umstellen, starten Sie die IDE danach neu.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.2.12.499<\/span><span class=\"msysdl-history__date\">12. August 2026 10:52<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Das zentrale Thema dieser Version ist die Aufnahme des Plugins \"MSYS Delphi MCP Server\" in die Suite: RAD Studio wird damit f\u00fcr KI-Werkzeuge wie Claude Code bedienbar. Daneben b\u00fcndelt die Suite ihre Einstellungen jetzt zentral in den IDE-Optionen und meldet sich beim IDE-Start auf Splashscreen und Info-Dialog von RAD Studio an.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: MSYS Delphi MCP Server \u2014 KI-Werkzeuge bedienen die IDE<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Das neue Plugin betreibt einen MCP-Server (Model Context Protocol) direkt im IDE-Prozess. KI-Assistenten wie Claude Code verbinden sich damit und arbeiten in der laufenden IDE: Quelltexte und Formulare lesen und \u00e4ndern, Projekte kompilieren, Anwendungen starten, debuggen und bedienen \u2014 unter Ihrer Aufsicht, in Ihrer ge\u00f6ffneten IDE.<\/p>\n<p class=\"MD_p\">Der Werkzeugumfang in Stichpunkten:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Quelltext-Editor und Formular-Designer: Dateien \u00f6ffnen, lesen, \u00e4ndern und speichern; Komponenten anlegen, Eigenschaften und Ereignisse setzen.<\/li>\n<li class=\"MD_li\">Projekte: kompilieren, bereinigen, Build-Konfiguration wechseln, Projektoptionen (u. a. Suchpfade) lesen und schreiben; Meldungen und Build-Log abrufen.<\/li>\n<li class=\"MD_li\">Debugger: Anwendung starten (auch mit Startparametern), anhalten und fortsetzen, Haltepunkte verwalten, Einzelschritte, Threads und Aufrufliste einsehen, Ausdr\u00fccke auswerten und Werte \u00e4ndern.<\/li>\n<li class=\"MD_li\">Laufende Anwendung: Oberfl\u00e4che abfragen und bedienen (Klicks, Eingaben) \u2014 f\u00fcr Tests der eigenen Anwendung direkt aus dem KI-Werkzeug heraus.<\/li>\n<li class=\"MD_li\">Datenbanken: Verbindungen verwalten, SQL ausf\u00fchren und Schemata analysieren (\u00fcber FireDAC, Datenbank-Engine-neutral).<\/li>\n<li class=\"MD_li\">Project ToDos: Aufgaben lesen, anlegen und pflegen; \u00c4nderungen an den Aufgaben werden dem KI-Werkzeug aktiv gemeldet.<\/li>\n<\/ul>\n<p class=\"MD_p\">Sicherheit und Alltag: Gleichzeitige Zugriffe auf die IDE werden serialisiert; bei offenen modalen Dialogen verweigern die Werkzeuge den Zugriff kontrolliert, statt die IDE zu blockieren. Die Einstellungen des Servers finden Sie unter Tools &gt; Optionen.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">Suite &amp; IDE-Integration<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Einstellungen an einem Ort: Alle Plugins der Suite konfigurieren Sie jetzt zentral unter Tools &gt; Optionen in einer eigenen MSYS-Sektion \u2014 die bisherigen einzelnen Einstellungsdialoge entfallen.<\/li>\n<li class=\"MD_li\">Die Suite meldet sich beim IDE-Start an: mit eigenem Eintrag auf dem Splashscreen und im Info-Dialog von RAD Studio.<\/li>\n<li class=\"MD_li\">Neuer suite-interner Ereignis-Bus: Die Plugins informieren sich gegenseitig \u00fcber \u00c4nderungen \u2014 z. B. erf\u00e4hrt der MCP-Server sofort von ge\u00e4nderten Aufgaben der Project ToDos.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Spaltenbreiten und Sortierung der Aufgaben\u00fcbersicht werden mit dem IDE-Desktop gespeichert und wiederhergestellt.<\/li>\n<li class=\"MD_li\">Interne Dateien (z. B. gespeicherte Kanban-Einstellungen) erscheinen nicht mehr f\u00e4lschlich als Aufgaben.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">SBOM Generator \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die Konfiguration ist in die IDE-Optionen umgezogen: vier Seiten unter Tools &gt; Optionen ersetzen den bisherigen eigenen Einstellungsdialog.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Setup &amp; Deinstallation<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Wird die Installation \u00fcber die Benutzerkontensteuerung mit einem anderen Administratorkonto erhoben, landen die Registrierung der Suite und die Kachel der Startseite jetzt trotzdem zuverl\u00e4ssig im Profil des angemeldeten Benutzers \u2014 und die Deinstallation r\u00e4umt exakt dort wieder auf.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die Installation kann direkt \u00fcber eine bestehende Version erfolgen; eine Deinstallation ist nicht n\u00f6tig.<\/li>\n<li class=\"MD_li\">Die Delphi-IDE muss w\u00e4hrend der Installation geschlossen sein; das Setup pr\u00fcft dies automatisch.<\/li>\n<li class=\"MD_li\">Einstellungen: Die Plugin-Konfiguration finden Sie k\u00fcnftig unter Tools &gt; Optionen (siehe Abschnitt 2).<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.2.12.493<\/span><span class=\"msysdl-history__date\">29. July 2026 10:52<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version baut die Suite in allen Bereichen aus: ein neues Plugin (MSYS AutoReload), sp\u00fcrbare Komfort- und Stabilit\u00e4tsverbesserungen in der IDE sowie umfangreiche Erweiterungen des SBOM Generators samt vollst\u00e4ndigem Benutzerhandbuch. Die Produktversion entspricht ab dieser Version der Dateiversion der zentralen MSYS-Bibliothek.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: MSYS AutoReload \u2014 externe Datei\u00e4nderungen ohne Nachfrage<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Das neue Plugin \u00fcberwacht die in der IDE ge\u00f6ffneten Dateien (einschlie\u00dflich Begleitdateien wie JSON oder Markdown) und l\u00e4dt sie automatisch neu, wenn sie au\u00dferhalb der IDE ge\u00e4ndert wurden \u2014 etwa durch Werkzeuge, Skripte oder die Versionsverwaltung. Der Dialog \"Datei wurde au\u00dferhalb des Editors ge\u00e4ndert\" entf\u00e4llt f\u00fcr unver\u00e4nderte Editor-Inhalte komplett.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">Suite &amp; IDE-Integration<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Willkommensseite: Eine eigene MSYS-Kachel auf der RAD-Studio-Startseite zeigt die installierten Plugins der Suite auf einen Blick.<\/li>\n<li class=\"MD_li\">Meldungsfenster: Alle Meldungen der Suite erscheinen jetzt in einer eigenen Gruppe \"MSys\" \u2014 farbig nach Meldungsart (Info, Warnung, Fehler) und an das helle wie dunkle IDE-Theme angepasst.<\/li>\n<li class=\"MD_li\">About-Dialog: \u00fcberarbeitet, mit animiertem 3D-Logo und direktem Kontakt-Link; die Versions- und Herstellerangaben der Plugins werden zuverl\u00e4ssig aus den geladenen Modulen ermittelt.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Erweiterungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der Bearbeitungsdialog zeigt die Aufgaben-ID an und erlaubt das direkte Bl\u00e4ttern von Aufgabe zu Aufgabe, ohne den Dialog zu verlassen.<\/li>\n<li class=\"MD_li\">Zuverl\u00e4ssigere Aktualisierung der Aufgaben\u00fcbersicht bei schnellen \u00c4nderungen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">SBOM Generator \u2014 Erweiterungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Vollst\u00e4ndiges Benutzerhandbuch: Der Funktionsumfang des Plugins ist jetzt durchg\u00e4ngig dokumentiert (Installation, Einstellungen, Editor, virtuelle SBOMs, externe Module, Fehlersuche); die CLI-Anleitung wurde \u00fcberarbeitet.<\/li>\n<li class=\"MD_li\">Bibliotheks- und Package-Projekte vervollst\u00e4ndigt: Die Projekt\u00fcbersicht (\"Project Info\") zeigt jetzt auch die Builds von DLL- und BPL-Projekten; in der SBOM erhalten sie den korrekten CycloneDX-Komponententyp \"library\".<\/li>\n<li class=\"MD_li\">PDF-Report: Nach dem Erstellen \u00fcber den \u2014 jetzt deutlich sichtbaren \u2014 PDF-Button \u00f6ffnet sich der Report automatisch im Standard-PDF-Viewer. Ein Fehler, der beim Erzeugen des Reports zum Absturz f\u00fchren konnte, wurde behoben.<\/li>\n<li class=\"MD_li\">Zuverl\u00e4ssigkeit im Alltag: Beim Kompilieren mit ge\u00f6ffneter SBOM-Datei erscheint keine \"Datei wurde ge\u00e4ndert\"-Nachfrage mehr; die Liste der virtuellen SBOMs aktualisiert sich selbstst\u00e4ndig; neu erstellte Projekte erzeugen keine wiederkehrenden Statusmeldungen mehr; Meldungen erscheinen ohne doppelte Kennzeichnung.<\/li>\n<li class=\"MD_li\">Kommandozeilen-Tools f\u00fcr CI\/CD: Die Tools SBomGen und GenSBOMReport verwenden jetzt benannte Parameter in der Form -name=wert (z. B. SBomGen -project=MyApp.dproj -platform=Win32 -config=Release). Neu sind die Parameter -extmodules= und -vsbom=, mit denen die Verzeichnisse f\u00fcr externe Module und virtuelle SBOMs pro Lauf \u00fcberschrieben werden k\u00f6nnen \u2014 die Daten k\u00f6nnen damit direkt aus dem Repository kommen, ohne das Benutzerprofil des Build-Agenten vorzubereiten. Hinweis: Die bisherige positionsbasierte Aufrufform wird nicht mehr unterst\u00fctzt; bestehende Build-Skripte m\u00fcssen einmalig angepasst werden.<\/li>\n<li class=\"MD_li\">Der grafische SBOM-Editor folgt jetzt vollst\u00e4ndig dem dunklen IDE-Theme.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Stabilit\u00e4t<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Ein Fehler beim Schlie\u00dfen der IDE mit geladenen Plugins (Zugriffsverletzung beim Herunterfahren) wurde behoben.<\/li>\n<li class=\"MD_li\">Die Logging-Infrastruktur der Suite wurde konsolidiert und ist durchg\u00e4ngig thread-sicher.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die MSYS Delphi Tools k\u00f6nnen direkt \u00fcber eine bestehende Installation der Version 1.0.0 installiert werden; eine Deinstallation ist nicht n\u00f6tig.<\/li>\n<li class=\"MD_li\">Die Delphi-IDE muss w\u00e4hrend der Installation geschlossen sein; das Setup pr\u00fcft dies automatisch.<\/li>\n<li class=\"MD_li\">CI\/CD: Aufrufe der Kommandozeilen-Tools auf die neue -name=wert-Syntax umstellen (siehe Abschnitt 4).<\/li>\n<li class=\"MD_li\">Ausblick: Das Plugin \"MSYS Delphi MCP Server\" (Anbindung von KI-Werkzeugen an die IDE \u00fcber das Model Context Protocol) wurde weiter ausgebaut und bleibt Bestandteil einer kommenden Version.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.0.0.0<\/span><span class=\"msysdl-history__date\">24. June 2026 10:53<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version l\u00f6st den bisher einzeln ausgelieferten \"MSYS SBOM Generator 0.2.0 Beta\" ab. Aus dem einzelnen Plugin ist die Produktfamilie \"MSYS Delphi Tools\" geworden: eine modulare Sammlung von Erweiterungen f\u00fcr Embarcadero RAD Studio 13 (Delphi 13), die \u00fcber einen gemeinsamen Installer ausgeliefert wird.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">Neue Produktstruktur \u2014 eine Suite, ein Installer<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Ein zentrales Setup installiert alle Werkzeuge in einem Durchgang. Im Komponenten-Dialog w\u00e4hlen Sie aus, welche Plugins Sie nutzen m\u00f6chten \u2014 jedes Plugin ist einzeln an- und abw\u00e4hlbar.<\/li>\n<li class=\"MD_li\">Alle Plugins ordnen sich unter dem neuen gemeinsamen Hauptmen\u00fc \"MSys\" der IDE ein. Ein Men\u00fcpunkt, alle Werkzeuge.<\/li>\n<li class=\"MD_li\">Der Dialog \"About MSys\u2026\" zeigt auf einen Blick die installierte Version aller geladenen Plugins einschlie\u00dflich Hersteller-Angaben.<\/li>\n<li class=\"MD_li\">Die Plugin-Verwaltung \u00fcbernimmt das Paket selbst: In der IDE wird nur noch eine einzige Bibliothek registriert; die Plugins werden automatisch erkannt und geladen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">NEU: MSYS Project ToDos \u2014 Aufgabenverwaltung im Projekt<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Mit \"Project ToDos\" erh\u00e4lt die IDE eine vollst\u00e4ndige, projektbezogene Aufgabenverwaltung. Aufgaben werden im Projektordner gespeichert und wandern damit gemeinsam mit dem Quellcode durch Ihre Versionsverwaltung \u2014 ideal f\u00fcr Teams.<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Andockbare Aufgaben\u00fcbersicht (MSys \u2192 Project Todos): alle Aufgaben des ge\u00f6ffneten Projekts mit Status, Priorit\u00e4t, Kategorie und Verantwortlichem; sortier- und filterbar. \u00c4nderungen am Projekt oder an den Aufgabendateien werden automatisch erkannt.<\/li>\n<li class=\"MD_li\">Komfortabler Bearbeitungsdialog: Jede Aufgabe besteht aus einem kompakten Eintrag und einer ausf\u00fchrlichen Notiz im Markdown-Format \u2014 Platz f\u00fcr Spezifikationen, Akzeptanzkriterien und Checklisten.<\/li>\n<li class=\"MD_li\">Kanban-Board (MSys \u2192 Project Todos Kanban): Aufgaben als Karten in Spalten, per Drag &amp; Drop verschiebbar. Die Gruppierung ist umschaltbar nach Status, Kategorie oder Priorit\u00e4t; Spaltenfarben und ausgeblendete Spalten werden je Projekt gespeichert. Filter blenden erledigte und verworfene Aufgaben wahlweise aus.<\/li>\n<li class=\"MD_li\">Beziehungen zwischen Aufgaben: \"blockiert von\", \"bezieht sich auf\" und \"Duplikat von\". Blockierte Aufgaben werden in Liste und Board markiert; ein Tooltip zeigt, welche Aufgaben blockieren und welche blockiert werden.<\/li>\n<li class=\"MD_li\">Freie Reihenfolge: Aufgaben lassen sich per Drag &amp; Drop, Tastatur (Alt + Pfeiltasten) oder Kontextmen\u00fc manuell sortieren \u2014 die Reihenfolge bleibt dauerhaft erhalten.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">SBOM Generator \u2014 Erweiterungen seit Version 0.2.0 Beta<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">CycloneDX 1.6: Erzeugte SBOM-Dateien folgen jetzt der CycloneDX-Spezifikation in Version 1.6 (bisher 1.5).<\/li>\n<li class=\"MD_li\">Komponenten-Editor: Der Reiter \"Components\" des grafischen SBOM-Editors ist nun vollst\u00e4ndig editierbar. Komponenten k\u00f6nnen manuell angelegt, bearbeitet und gel\u00f6scht werden.<\/li>\n<li class=\"MD_li\">Import von Hersteller-SBOMs: Liefert ein Drittanbieter eine eigene SBOM-Datei (*.cdx.json) mit, l\u00e4sst sie sich direkt in die SBOM des eigenen Projekts \u00fcbernehmen \u2014 einschlie\u00dflich Unterkomponenten und Abh\u00e4ngigkeitsgraph. Ebenso k\u00f6nnen Komponenten aus den eigenen virtuellen SBOMs \u00fcbernommen werden.<\/li>\n<li class=\"MD_li\">Externe Module: Neue Verwaltung f\u00fcr Fremdmodule, die nicht aus dem Delphi-Build stammen (z. B. mitgelieferte Dritt-DLLs). Ein Scanner erkennt solche Module automatisch; ein eigener Editor und eine andockbare \u00dcbersicht erlauben die Pflege der Paketinformationen, die anschlie\u00dfend in die erzeugte SBOM einflie\u00dfen. Die Zuordnung wird je Projekt gespeichert.<\/li>\n<li class=\"MD_li\">DLL- und BPL-Projekte: Die Erkennung des Ausgabetyps wurde \u00fcberarbeitet \u2014 SBOMs werden jetzt auch f\u00fcr Bibliotheks- und Package-Projekte korrekt erzeugt, nicht nur f\u00fcr Anwendungen.<\/li>\n<li class=\"MD_li\">Stabilit\u00e4t: Verbesserungen beim Laden und Entladen des Plugins sowie diverse Fehlerbehebungen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Wenn der bisherige \"MSYS SBOM Generator 0.2.0 Beta\" installiert ist, deinstallieren Sie diesen bitte vor der Installation der MSYS Delphi Tools \u00fcber \"Apps &amp; Features\".<\/li>\n<li class=\"MD_li\">Die Delphi-IDE muss w\u00e4hrend der Installation geschlossen sein; das Setup pr\u00fcft dies automatisch.<\/li>\n<li class=\"MD_li\">Ausblick: Das Plugin \"MSYS Delphi MCP Server\" (Anbindung von KI-Werkzeugen an die IDE \u00fcber das Model Context Protocol) ist in Vorbereitung und wird Bestandteil einer kommenden Version sein.<\/li>\n<\/ul>\n<\/div><\/div><\/li><\/ul><\/div><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-8574589 e-con-full e-flex e-con e-child\" data-id=\"8574589\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-951f2c4 elementor-widget elementor-widget-msysdl_info\" data-id=\"951f2c4\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--version\"><span class=\"msysdl-info__label\">Version: <\/span><span class=\"msysdl-info__value\">1.9.13.539<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-7d0e419 e-con-full e-flex e-con e-child\" data-id=\"7d0e419\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-c709f74 elementor-widget elementor-widget-msysdl_info\" data-id=\"c709f74\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--release_date\"><span class=\"msysdl-info__label\">Release: <\/span><span class=\"msysdl-info__value\">26. October 2026 14:05<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-f2f2489 e-con-full e-flex e-con e-child\" data-id=\"f2f2489\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-9e5b9c6 elementor-widget elementor-widget-msysdl_button\" data-id=\"9e5b9c6\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-dl\"><a class=\"msysdl-dl__btn\" href=\"https:\/\/maenken.systems\/msysdl\/15305\/latest\/\" rel=\"nofollow\">Download<\/a><span class=\"msysdl-dl__meta\"><\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-dded4af e-con-full e-flex e-con e-child\" data-id=\"dded4af\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;gradient&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-c719a13 elementor-widget elementor-widget-text-editor\" data-id=\"c719a13\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Delphi 13<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-5bf70b5 e-con-full e-flex e-con e-child\" data-id=\"5bf70b5\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t<div class=\"elementor-element elementor-element-b5d785e e-con-full e-flex e-con e-child\" data-id=\"b5d785e\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-0b8383e elementor-widget elementor-widget-msysdl_history\" data-id=\"0b8383e\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_history.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"msysdl-history\" data-msysdl-history><button type=\"button\" class=\"msysdl-history__open\" aria-haspopup=\"dialog\">Release notes<\/button><div class=\"msysdl-history__modal\" role=\"dialog\" aria-modal=\"true\" aria-labelledby=\"msysdl-hist-title-2\" hidden><div class=\"msysdl-history__backdrop\" data-msysdl-close><\/div><div class=\"msysdl-history__dialog\" role=\"document\" tabindex=\"-1\"><button type=\"button\" class=\"msysdl-history__close\" data-msysdl-close aria-label=\"Close\">&times;<\/button><h2 class=\"msysdl-history__title\" id=\"msysdl-hist-title-2\">Version history<\/h2><ul class=\"msysdl-history__list\"><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.9.13.539<\/span><span class=\"msysdl-history__date\">26. October 2026 13:59<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version setzt den Code-Review der Suite fort: In allen Werkzeugen sind weitere Fehler behoben, die er zutage gef\u00f6rdert hat. Neu ist ein Plugin f\u00fcr Claude Code, das der MSYS Delphi MCP Server beim Einrichten eines Projekts mitbringt. Alle Werkzeuge der Suite tragen einheitlich die Hauptversion 1.9.<\/p>\n<h2 id=\"msysdl-cl-10-inhalt\" class=\"MD_h2\">Inhalt<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Project ToDos, mit Kanban-Board<\/li>\n<li class=\"MD_li\">MSYS Delphi MCP Server<\/li>\n<li class=\"MD_li\">SBOM, mit den Kommandozeilenwerkzeugen SBomGen und GenSBOMReport<\/li>\n<li class=\"MD_li\">AutoReload<\/li>\n<li class=\"MD_li\">CodeSigner<\/li>\n<li class=\"MD_li\">SmartSetup<\/li>\n<li class=\"MD_li\">Buildmanager<\/li>\n<\/ul>\n<p class=\"MD_p\">Die Plugins lassen sich bei der Installation einzeln abw\u00e4hlen. Das Setup installiert die Suite f\u00fcr die 32- und die 64-Bit-IDE.<\/p>\n<h2 id=\"msysdl-cl-10-neuerungen\" class=\"MD_h2\">Neuerungen<\/h2>\n<h3 id=\"msysdl-cl-10-stabilit\u00e4t-und-fehlerbehebungen\" class=\"MD_h3\">Stabilit\u00e4t und Fehlerbehebungen<\/h3>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Andockbare Fenster und Editor-Ansichten der Plugins melden sich beim Entladen vollst\u00e4ndig ab. Ein Zugriff der IDE auf ein bereits entladenes Plugin ist damit ausgeschlossen.<\/li>\n<li class=\"MD_li\">Hilfetexte der Plugins f\u00fchren nicht mehr zu einem Absturz, wenn das Erscheinungsbild der IDE noch nicht bereitsteht.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SBOM<\/strong><ul class=\"MD_ul\">\n<li class=\"MD_li\">SBomGen meldet einen Fehler bei der Erzeugung mit einem positiven Exit-Code; <code class=\"MD_code\">if errorlevel 1<\/code> in einem Build-Skript erkennt ihn jetzt.<\/li>\n<li class=\"MD_li\">Der PDF-Bericht druckt den Zeitstempel der SBOM, und ein langer Kopfteil bricht sauber auf die n\u00e4chste Seite um.<\/li>\n<li class=\"MD_li\">Das Ergebnis einer SBOM-Pr\u00fcfung wird nicht mehr stillschweigend gek\u00fcrzt.<\/li>\n<li class=\"MD_li\">Fehler beim Lesen einer MAP-Datei nennen im Protokoll Datei und Ursache; gro\u00dfe MAP-Dateien werden schneller ausgewertet.<\/li>\n<\/ul>\n<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">CodeSigner:<\/strong> Scheitert nur der Zeitstempeldienst, bleibt die Datei unsigniert, statt eine Signatur ohne Zeitstempel zu tragen. Die Pr\u00fcfung nach dem Signieren schlie\u00dft den Zeitstempel ein und nennt bei einem Abbruch den Grund.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project ToDos:<\/strong> Eine Kanban-Datei mit unerwarteten Eintr\u00e4gen l\u00e4sst das Board nicht mehr ohne Spalten zur\u00fcck, und ein Fehler im Board rei\u00dft das Plugin nicht mehr mit. \u00c4nderungen an den Notizen einer Aufgabe werden \u00fcberall erkannt.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SmartSetup:<\/strong> Der Hilfe-Ballon zeigt immer die Angaben des Produkts, \u00fcber dem er steht. Schl\u00e4gt die Abfrage der Zugangsdaten fehl, zeigt das Fenster keine ungefilterte Ausgabe des Kommandozeilenwerkzeugs mehr.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Buildmanager:<\/strong> Versionsnummern \u00fcber 65535 und doppelte Versionsangaben in Projekt- und Gruppendateien werden gemeldet statt \u00fcbernommen.<\/li>\n<\/ul>\n<h3 id=\"msysdl-cl-10-msys-delphi-mcp-server\" class=\"MD_h3\">MSYS Delphi MCP Server<\/h3>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEU:<\/strong> Claude-Code-Plugin \u201edelphi-ide-mcp\". <em class=\"MD_em\">Projekt einrichten<\/em> legt es neben die <code class=\"MD_code\">.mcp.json<\/code> des Arbeitsbereichs. Es bringt die Skills des Servers in jede Claude-Code-Sitzung dieses Ordners und l\u00e4sst den Server pr\u00fcfen, bevor Claude Code eine Delphi-Quelle an der IDE vorbei schreibt oder einen Compiler aus der Kommandozeile startet. Claude Code l\u00e4dt das Plugin erst, wenn Sie dem Ordner dort einmal vertraut haben.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">designer_add_component<\/code> l\u00e4sst die aktive Seite eines PageControls unver\u00e4ndert, wenn die neue Komponente auf eine Registerseite kommt.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">db_sql<\/code> lehnt im Lesemodus auch schreibende Anweisungen hinter <code class=\"MD_code\">WITH<\/code> und <code class=\"MD_code\">SELECT \u2026 INTO OUTFILE<\/code> ab.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">project_add_file<\/code> und <code class=\"MD_code\">project_remove_file<\/code> erhalten Kommentare zwischen den <code class=\"MD_code\">{$R}<\/code>-Direktiven der Projektdatei.<\/li>\n<li class=\"MD_li\">Das Lesen des Meldungsfensters kann die IDE nicht mehr einfrieren.<\/li>\n<li class=\"MD_li\">Die Skills des Servers werden auch gefunden, wenn die Umgebungsvariable <code class=\"MD_code\">PROGRAMDATA<\/code> fehlt.<\/li>\n<li class=\"MD_li\">Dazu mehrere Korrekturen an der Absicherung paralleler Zugriffe.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-10-hinweise-zur-installation\" class=\"MD_h2\">Hinweise zur Installation<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Schlie\u00dfen Sie RAD Studio vor der Installation; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Das Setup braucht ein 64-Bit-Windows und Administratorrechte.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.8.12.537<\/span><span class=\"msysdl-history__date\">16. October 2026 14:29<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version ist ein Stabilit\u00e4ts- und Qualit\u00e4ts-Release. Am deutlichsten merken Sie das beim Schlie\u00dfen von RAD Studio: Die IDE st\u00fcrzt mit geladenen Plugins nicht mehr ab. Die erzeugten Software-St\u00fccklisten (SBOM) folgen jetzt dem Standard CycloneDX 1.7. Alle Werkzeuge der Suite tragen einheitlich die Hauptversion <strong class=\"MD_strong\">1.8<\/strong>.<\/p>\n<h2 id=\"msysdl-cl-11-1-stabilit\u00e4t-und-fehlerbehebungen\" class=\"MD_h2\">1. Stabilit\u00e4t und Fehlerbehebungen<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Beim Schlie\u00dfen von RAD Studio mit geladenen MSYS-Plugins kam es zu einem Absturz. Das ist behoben.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">AutoReload:<\/strong> Eine angeforderte Neuladung wirkt jetzt zuverl\u00e4ssig.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SmartSetup:<\/strong> Fehler bleiben auf das Produktfenster beschr\u00e4nkt und rei\u00dfen die IDE nicht mehr mit; dazu weitere Korrekturen im Produktfenster.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">SBOM:<\/strong> mehrere Korrekturen im Editor und beim Einlesen aus Git \u2014 unter anderem wird ein auf den aktuellen Stand gesetzter Git-Tag jetzt \u00fcbernommen.<\/li>\n<li class=\"MD_li\">Dazu zahlreiche kleinere Korrekturen in Host und Plugins, die der Code-Review zutage gef\u00f6rdert hat.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-11-2-sbom--st\u00fccklisten-nach-cyclonedx-17\" class=\"MD_h2\">2. SBOM \u2014 St\u00fccklisten nach CycloneDX 1.7<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die erzeugten SBOMs folgen in allen Ausgabewegen dem Standard CycloneDX 1.7 und werden streng dagegen gepr\u00fcft.<\/li>\n<li class=\"MD_li\">Vollst\u00e4ndigere Lizenzangaben in den erzeugten St\u00fccklisten.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-11-3-msys-delphi-mcp-server--verbesserungen\" class=\"MD_h2\">3. MSYS Delphi MCP Server \u2014 Verbesserungen<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEU:<\/strong> <code class=\"MD_code\">project_add_config<\/code> und <code class=\"MD_code\">project_remove_config<\/code> legen Build-Konfigurationen eines Projekts an und entfernen sie.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEU:<\/strong> <code class=\"MD_code\">designer_clear_event<\/code> entfernt die Zuordnung eines Ereignisses im Formular-Designer.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">editor_close_file<\/code> kann die Datei vor dem Schlie\u00dfen speichern.<\/li>\n<li class=\"MD_li\">Das Ausgabeverzeichnis f\u00fcr BPL und DCP eines Projekts l\u00e4sst sich lesen und setzen; ebenso die Optionen des Ressourcen-Compilers.<\/li>\n<li class=\"MD_li\">Compiler-Meldungen kommen jetzt verl\u00e4sslich aus dem Datenmodell der IDE.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project ToDos:<\/strong> Die \u00c4nderungspr\u00fcfung ber\u00fccksichtigt auch die Beschreibung und die Notizen einer Aufgabe.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-11-4-setup\" class=\"MD_h2\">4. Setup<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der MSys CodeSign Buildhost wird nicht mehr mit der Suite ausgeliefert. Signiert wird \u00fcber den MSys CodeSign Server.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-11-5-hinweise-zum-upgrade\" class=\"MD_h2\">5. Hinweise zum Upgrade<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Schlie\u00dfen Sie RAD Studio vor der Installation<\/strong>; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Haben Sie mit Version 1.7 den MSys CodeSign Buildhost \u00fcber das Setup installiert, bleibt er als eigenes Produkt bestehen. Dieses Setup liefert ihn nicht mehr mit; das Signieren l\u00e4uft unver\u00e4ndert \u00fcber den MSys CodeSign Server.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.7.12.531<\/span><span class=\"msysdl-history__date\">12. October 2026 10:54<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">This version brings a new tool for anyone who builds a project for several platforms and configurations: the <strong class=\"MD_strong\">Build Manager<\/strong>. The <strong class=\"MD_strong\">MSYS Delphi MCP Server<\/strong> can operate it as well and has become considerably more reliable with long builds and changes to project files. All tools in the suite now share the major version <strong class=\"MD_strong\">1.7<\/strong>.<\/p>\n<h2 id=\"msysdl-cl-12-1-new-msys-build-manager--build-profiles-for-projects-and-groups\" class=\"MD_h2\">1. NEW: MSYS Build Manager \u2014 build profiles for projects and groups<\/h2>\n<p class=\"MD_p\">If you build a project for several platforms and configurations, you now define this once as a profile and start it with a single click.<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">A <strong class=\"MD_strong\">project profile<\/strong> selects from platform \u00d7 configuration, for example Win32 and Win64, each in Release.<\/li>\n<li class=\"MD_li\">A <strong class=\"MD_strong\">group profile<\/strong> combines the project profiles of a project group and builds them in the group's order.<\/li>\n<li class=\"MD_li\">Clean, Compile and Build are started from a dockable window. After the run, the previously active platform and configuration are restored.<\/li>\n<li class=\"MD_li\">A run can be cancelled; for each step you see errors, warnings and hints.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Version numbers<\/strong> can be set per project or for the whole group. The Build Manager writes them into the project before each build, so all platforms of a run carry the same number; if desired, it increments the build number automatically.<\/li>\n<li class=\"MD_li\">The profiles are stored in the <code class=\"MD_code\">.dproj<\/code> or <code class=\"MD_code\">.groupproj<\/code> file and go into version control together with the project.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-12-2-msys-delphi-mcp-server--improvements\" class=\"MD_h2\">2. MSYS Delphi MCP Server \u2014 improvements<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW:<\/strong> Build profiles can be read, created, changed and started via the server (<code class=\"MD_code\">buildprofile_list<\/code>, <code class=\"MD_code\">_get<\/code>, <code class=\"MD_code\">_set<\/code>, <code class=\"MD_code\">_rename<\/code>, <code class=\"MD_code\">_remove<\/code>, <code class=\"MD_code\">_run<\/code>, <code class=\"MD_code\">_status<\/code>, <code class=\"MD_code\">_cancel<\/code>). The server status (<code class=\"MD_code\">server_status<\/code>) reports whether the Build Manager is loaded and whether profiles have been set up.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW:<\/strong> <code class=\"MD_code\">codesigner_get_config<\/code> and <code class=\"MD_code\">codesigner_set_config<\/code> read and set a project's signing settings. The tool <code class=\"MD_code\">code_sign_file<\/code> is now called <code class=\"MD_code\">codesigner_sign_file<\/code>.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Long builds:<\/strong> <code class=\"MD_code\">project_compile<\/code> responds after 240 seconds at the latest. If a build takes longer, it keeps running; the response says so, and the result appears in the suite's message window. Calls that need the IDE in the meantime receive a \"busy\" response including the running tool, instead of running into a seemingly hanging dialog.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project files:<\/strong> <code class=\"MD_code\">project_add_file<\/code> reports an IDE prompt immediately instead of waiting. <code class=\"MD_code\">project_rename_file<\/code> reports what the IDE actually did and updates the uses clause of all affected projects. Comments and the IDE's form creation code in the project file are preserved when adding, removing and renaming.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Form Designer:<\/strong> <code class=\"MD_code\">designer_delete_component<\/code> also deletes menu items. <code class=\"MD_code\">designer_get_components<\/code> shows menu items, actions and fields under their parent element and no longer lists internal helper objects. <code class=\"MD_code\">designer_set_event<\/code> also works with inherited forms.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Project ToDos:<\/strong> Write access can be protected against intermediate changes. If someone else has changed a task in the meantime, nothing is overwritten.<\/li>\n<li class=\"MD_li\"><code class=\"MD_code\">project_get_build_log<\/code> returns the end of the log, where the errors are. <code class=\"MD_code\">editor_save_all<\/code> and <code class=\"MD_code\">ide_get_open_modules<\/code> also detect projects with changed options as unsaved.<\/li>\n<li class=\"MD_li\">The bundled skills for AI assistants have been restructured: concise entry pages, with the details in separate files.<\/li>\n<li class=\"MD_li\">A memory leak in several tools has been fixed.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-12-3-setup\" class=\"MD_h2\">3. Setup<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">The Build Manager is included in the full setup and can be deselected individually in the component selection.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW:<\/strong> For the CodeSigner, the setup can also install the <strong class=\"MD_strong\">MSys CodeSign Buildhost<\/strong> \u2014 the connection to the MSys CodeSign Server (<code class=\"MD_code\">RemoteSigner.dll<\/code> for <code class=\"MD_code\">signtool \/dlib<\/code>, plus <code class=\"MD_code\">CodeSignJob.exe<\/code> and <code class=\"MD_code\">CodeSignConfigCLI.exe<\/code>). It is a separate product with its own entry under \"Apps &amp; Features\" and remains installed when the suite is uninstalled.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-12-4-also-new-since-the-last-release-1312526\" class=\"MD_h2\">4. Also new since the last release 1.3.12.526<\/h2>\n<p class=\"MD_p\">Version 1.5.12.531 added:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">32-bit and 64-bit IDE:<\/strong> The setup installs the tools for both IDEs of Delphi 13; each finds its own build, and both carry the same number.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">NEW: MSYS SmartSetup<\/strong> \u2014 the TMS Smart Setup products in the IDE: a list with filters, a tile on the Welcome Screen, updating and installing directly from the IDE. Requires an existing installation of TMS Smart Setup (<code class=\"MD_code\">tms.exe<\/code>).<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">MCP Server:<\/strong> Calls with an unknown parameter are rejected; <code class=\"MD_code\">project_compile<\/code> can build a specific platform and configuration on request; <code class=\"MD_code\">project_set_platforms<\/code> toggles target platforms; <code class=\"MD_code\">text_search<\/code> understands regular expressions; line endings are always CRLF.<\/li>\n<li class=\"MD_li\">Project ToDos, SBOM Generator and the consistently English user interface with German translation \u2014 details in the setup's \"What's New\" file.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-12-5-upgrade-notes\" class=\"MD_h2\">5. Upgrade notes<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Close RAD Studio before installing<\/strong>; the setup checks for this.<\/li>\n<li class=\"MD_li\">An existing installation is overwritten; your settings are retained.<\/li>\n<li class=\"MD_li\">If you address the MCP server from scripts or your own instructions: <code class=\"MD_code\">code_sign_file<\/code> is now called <code class=\"MD_code\">codesigner_sign_file<\/code>.<\/li>\n<li class=\"MD_li\">If you don't need the MSys CodeSign Buildhost, deselect it in the component selection under the CodeSigner.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.5.12.531<\/span><span class=\"msysdl-history__date\">23. September 2026 10:55<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version l\u00e4uft zum ersten Mal auch in der 64-Bit-IDE von Delphi 13. Dazu kommt ein neues Werkzeug f\u00fcr TMS Smart Setup, und f\u00fcr einzelne Werkzeuge gibt es jetzt eigene, kleinere Setups.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: 32- und 64-Bit-IDE<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Delphi 13 gibt es als 32- und als 64-Bit-IDE. Das Setup installiert die Werkzeuge jetzt f\u00fcr beide: Jede IDE findet ihre eigene Fassung, und Sie k\u00f6nnen frei zwischen ihnen wechseln. Beide Fassungen tragen dieselbe Versionsnummer.<\/p>\n<p class=\"MD_p\">Alle Werkzeuge der Suite tragen ab dieser Version einheitlich die Hauptversion 1.5.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">NEU: MSYS SmartSetup \u2014 TMS-Produkte im Blick<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Wer Komponenten von TMS \u00fcber TMS Smart Setup bezieht, sieht jetzt in der IDE, welche Produkte es gibt, welche installiert sind und wo eine neuere Fassung bereitliegt.<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Eine gegliederte Liste mit Filtern (installiert, Update verf\u00fcgbar, Name, Server) zeigt Name, installierte und verf\u00fcgbare Version, Status, Lizenz und Server jedes Produkts.<\/li>\n<li class=\"MD_li\">Eine Kachel auf dem Welcome-Screen nennt die Zahl der Produkte, der installierten und der verf\u00fcgbaren Updates.<\/li>\n<li class=\"MD_li\">Aktualisieren und Installieren laufen direkt aus der IDE; die Ausgabe erscheint live im Meldungsfenster.<\/li>\n<\/ul>\n<p class=\"MD_p\">Voraussetzung ist eine vorhandene Installation von TMS Smart Setup (tms.exe); das Plugin bringt sie nicht mit.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">NEU: Einzelsetups<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Neben dem Gesamtsetup gibt es eigene Setups f\u00fcr den SBOM Generator, den CodeSigner und SmartSetup. Sie sind Teil desselben Produkts: Wer sp\u00e4ter das Gesamtsetup installiert, aktualisiert einfach, und eine Deinstallation entfernt alles gemeinsam.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">MSYS Delphi MCP Server \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Aufrufe mit einem unbekannten Parameter werden jetzt abgelehnt, statt den Parameter stillschweigend zu \u00fcbergehen. Ein Tippfehler im Parameternamen f\u00e4llt damit sofort auf.<\/li>\n<li class=\"MD_li\">NEU: project_compile baut auf Wunsch eine bestimmte Plattform und Konfiguration und stellt danach die vorherige wieder ein.<\/li>\n<li class=\"MD_li\">NEU: project<em class=\"MD_em\">set<\/em>platforms schaltet Zielplattformen eines Projekts ein und aus.<\/li>\n<li class=\"MD_li\">NEU: text_search versteht regul\u00e4re Ausdr\u00fccke und nimmt auch eine einzelne Datei als Suchort.<\/li>\n<li class=\"MD_li\">Zeilenenden sind immer CRLF: Bearbeitet ein Werkzeug eine Datei mit LF-Zeilenenden, wird sie durchgehend auf CRLF gebracht.<\/li>\n<li class=\"MD_li\">Zahlreiche Meldungen sind genauer geworden \u2014 etwa wenn ein gesuchter Text nur innerhalb einer Zeile vorkommt oder ein Projekt nicht aufger\u00e4umt werden kann, weil die IDE seine DLL geladen hat.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Weitere Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Project ToDos: Der Abh\u00e4ngigkeits-Streifen wird gr\u00fcn, sobald alle Blocker erledigt sind; Statusfilter und Beziehungen werden strenger gepr\u00fcft.<\/li>\n<li class=\"MD_li\">SBOM Generator: Speichern im SBOM-Editor funktioniert auch nach einem Dateiwechsel zuverl\u00e4ssig; System-DLLs werden passend zur Plattform aufgel\u00f6st, JSON-Dateien ohne BOM geschrieben.<\/li>\n<li class=\"MD_li\">Die Oberfl\u00e4che der Suite ist durchgehend englisch, mit deutscher \u00dcbersetzung.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.3.12.526<\/span><span class=\"msysdl-history__date\">16. September 2026 12:04<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version bringt ein neues Werkzeug mit: den CodeSigner, der Ihre fertigen Programme signiert, ohne dass Sie daran denken m\u00fcssen. Der zweite Schwerpunkt liegt beim SBOM Generator, der auf CycloneDX 1.7 umgestellt wurde und jetzt das BSI-Profil nach TR-03183-2 erzeugen und pr\u00fcfen kann.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: MSYS CodeSigner \u2014 signierte Auslieferung ohne Handgriff<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Unsignierte Software hat es unter Windows schwer: SmartScreen warnt, die Benutzerkontensteuerung meldet einen \u201eunbekannten Herausgeber\", und mancher Virenscanner schaut genauer hin. Das neue Plugin nimmt Ihnen den Schritt ab, der das verhindert.<\/p>\n<p class=\"MD_p\">Der CodeSigner signiert das Ergebnis eines Builds unmittelbar nachdem die IDE es erzeugt hat \u2014 mit Zeitstempel und anschlie\u00dfender Pr\u00fcfung. Signiert wird ausschlie\u00dflich, was Sie daf\u00fcr angemeldet haben:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Einmal pro Rechner hinterlegen Sie unter Tools &gt; Optionen &gt; MSys &gt; CodeSigner, womit signiert wird. Drei Wege stehen zur Wahl: Hardware-Token\/HSM, Zertifikatsdatei oder Azure Trusted Signing.<\/li>\n<li class=\"MD_li\">Pro Projekt entscheiden Sie unter MSys &gt; Code-Signierung f\u00fcr dieses Projekt\u2026, ob und in welchen Build-Konfigurationen signiert wird. Die Angabe wandert in die .dproj und gilt f\u00fcr jeden, der das Projekt baut.<\/li>\n<li class=\"MD_li\">Nach jedem Compile pr\u00fcft das Plugin vier Dinge: War der Build erfolgreich? Ist das Projekt angemeldet? Steht die gebaute Konfiguration auf der Liste? F\u00e4llt eines davon durch, passiert nichts.<\/li>\n<\/ul>\n<p class=\"MD_p\">Einzelne Dateien signieren Sie \u00fcber MSys &gt; Datei signieren\u2026 \u2014 auch solche, die nicht aus dem aktuellen Projekt stammen. Der Dialog sagt Ihnen vorab, ob dieser Rechner \u00fcberhaupt signieren kann.<\/p>\n<p class=\"MD_p\">Voraussetzung ist ein Code-Signing-Zertifikat und signtool.exe aus dem Windows SDK; beides bringen Sie mit, das Plugin benutzt, was auf Ihrem Rechner liegt. Ein ausf\u00fchrliches Handbuch finden Sie im Wiki des Projekts.<\/p>\n<p class=\"MD_p\">Der Azure-Zweig ist vollst\u00e4ndig eingebaut, aber mangels Konto noch nicht mit einem echten Dienst erprobt; die Options-Seite weist ihn deshalb als \u201e(vorbereitet)\" aus.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">MSYS SBOM Generator \u2014 CycloneDX 1.7 und das BSI-Profil<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der Generator erzeugt jetzt CycloneDX 1.7 statt 1.6. Das Schema wurde vollst\u00e4ndig ausgewertet und die Ausgabe lokal dagegen gepr\u00fcft.<\/li>\n<li class=\"MD_li\">NEU: Das Profil nach BSI TR-03183-2 l\u00e4sst sich einschalten. Es erg\u00e4nzt je Komponentenart die vom BSI geforderten Eigenschaften; die Werte sind im SBOM-Editor einstellbar.<\/li>\n<li class=\"MD_li\">NEU: Ein Validator pr\u00fcft eine SBOM gegen den CycloneDX-Kern und gegen die BSI-Anforderungen. Jeder Befund tr\u00e4gt eine Regel-Kennung, sodass nachvollziehbar ist, woran er h\u00e4ngt. Auch als Verb der Kommandozeilen-Werkzeuge verf\u00fcgbar \u2014 damit l\u00e4sst sich eine SBOM in der Build-Kette pr\u00fcfen.<\/li>\n<li class=\"MD_li\">Neben SHA-256 wird jetzt auch SHA-512 berechnet, in einem Lesedurchlauf.<\/li>\n<li class=\"MD_li\">Externe Module lassen sich als solche kennzeichnen: Wird ein Modul mitgeliefert oder auf dem Zielsystem vorausgesetzt? Liegt f\u00fcr ein externes Modul eine eigene SBOM vor, kann sie wahlweise referenziert statt eingebettet werden.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Delphi MCP Server \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">NEU: Das Werkzeug code<em class=\"MD_em\">sign<\/em>file l\u00e4sst eine beliebige Datei \u00fcber den CodeSigner signieren. Die Server-Auskunft (server_status) meldet zus\u00e4tzlich, ob der Signer geladen ist und ob dieser Rechner derzeit signieren kann.<\/li>\n<li class=\"MD_li\">Der Formular-Designer ist weiter bedienbar geworden: Seiten, Collections und Men\u00fc-Eintr\u00e4ge lassen sich jetzt ebenfalls anlegen und \u00e4ndern.<\/li>\n<li class=\"MD_li\">L\u00e4uft ein Werkzeug-Aufruf in eine Exception der Anwendung, h\u00e4lt der Debugger nicht mehr den ganzen Ablauf an \u2014 er setzt fort, wo das bisher eine R\u00fcckfrage erzwang.<\/li>\n<li class=\"MD_li\">Dialoge werden vollst\u00e4ndiger gemeldet: Der Fragetext fensterloser VCL-Steuerelemente kommt jetzt mit.<\/li>\n<li class=\"MD_li\">Der Server startet standardm\u00e4\u00dfig mit dem Plugin. Wer das nicht m\u00f6chte, schaltet es in den Optionen ab.<\/li>\n<li class=\"MD_li\">Zum Server gibt es ein ausf\u00fchrliches Benutzerhandbuch im Wiki des Projekts.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">NEU: Der Status \u201eTBD (zu besprechen)\u201c. Er h\u00e4lt fest, dass eine Aufgabe auf eine Entscheidung von Ihnen wartet \u2014 die h\u00e4ufigste Art, wie ein Vorgang liegen bleibt, ohne dass es auff\u00e4llt. Anders als \u201eZur\u00fcckgestellt\u201c blendet ihn kein Filter aus: Eine Frage, die auf Antwort wartet, soll sichtbar bleiben. Setzen k\u00f6nnen Sie ihn im Bearbeiten-Dialog, \u00fcber das Kontextmen\u00fc der Aufgabenliste oder indem Sie die Karte auf dem Board in die neue Spalte TBD ziehen. Bestehende Boards bekommen diese Spalte beim n\u00e4chsten \u00d6ffnen von selbst dazu. Auch der KI-Assistent am MCP-Server kennt ihn: Steht eine Entscheidung an, die nur Sie treffen k\u00f6nnen, legt er die Aufgabe dort ab und fragt nach, statt zu raten.<\/li>\n<li class=\"MD_li\">Beziehungen zwischen Aufgaben werden beim Speichern gegen den Bestand gepr\u00fcft. Eine Kennung, die es nicht gibt, wird abgelehnt statt stillschweigend \u00fcbernommen.<\/li>\n<li class=\"MD_li\">Der Bearbeiten-Dialog ist breiter geworden, damit die deutschen Beschriftungen vollst\u00e4ndig hineinpassen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Einrichtung: der MCP-Server meldet sich bei Kai an<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Das Setup tr\u00e4gt den MSYS-MCP-Server auf Wunsch in Kai ein, den KI-Assistenten von RAD Studio. Damit stehen die Werkzeuge des Servers dort ohne weitere Handgriffe zur Verf\u00fcgung.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Schlie\u00dfen Sie RAD Studio vor der Installation; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Der CodeSigner ist in der Komponentenauswahl des Setups abw\u00e4hlbar. Ohne eingerichtetes Zertifikat tut er nichts \u2014 er meldet sich erst, wenn Sie ein Projekt f\u00fcr die Signierung anmelden.<\/li>\n<li class=\"MD_li\">Bestehende SBOMs bleiben lesbar. Neu erzeugte SBOMs tragen die Version 1.7; wer sie in einem Werkzeug weiterverarbeitet, das nur 1.6 versteht, pr\u00fcft das bitte vorab.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.2.12.520<\/span><span class=\"msysdl-history__date\">26. August 2026 10:56<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version dreht sich um die Bedienung: Die gesamte Suite spricht jetzt die Sprache Ihrer IDE \u2014 auf einer deutschen RAD Studio-Installation also Deutsch, sonst Englisch. Und jedes Eingabefeld, dessen Wirkung nicht auf den ersten Blick klar ist, erkl\u00e4rt sich selbst: Der Mauszeiger gen\u00fcgt, und es erscheint ein formatierter Hilfetext.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: Die Oberfl\u00e4che folgt der Sprache Ihrer IDE<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Men\u00fcs, Dialoge, Options-Seiten, Fenstertitel und Meldungen der Suite liegen jetzt zweisprachig vor. Betroffen ist alles, was Sie sehen:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">das MSys-Men\u00fc und der Info-Dialog der Suite,<\/li>\n<li class=\"MD_li\">die Options-Seiten unter Tools &gt; Optionen &gt; MSys,<\/li>\n<li class=\"MD_li\">die andockbaren Fenster samt ihrer Titel (\"Projekt-Todos\", \"MCP-Server\", \"SBOM-Projekteditor\", \"Virtuelle SBOMs\", \u2026),<\/li>\n<li class=\"MD_li\">die Dialoge der einzelnen Plugins,<\/li>\n<li class=\"MD_li\">das Kanban-Board der Project ToDos, das bisher als eigenst\u00e4ndiges Fenster durchgehend englisch war.<\/li>\n<\/ul>\n<p class=\"MD_p\">Ausgew\u00e4hlt wird beim Start des jeweiligen Plugins anhand der IDE-Sprache. Ein Sprachwechsel in RAD Studio wirkt sich deshalb erst nach einem Neustart der IDE aus. Fehlt zu einem Text eine \u00dcbersetzung, erscheint er auf Englisch \u2014 ohne Fehlermeldung und ohne L\u00fccke in der Oberfl\u00e4che.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">NEU: Hilfetexte, die erkl\u00e4ren statt zu benennen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Wo bisher ein kurzer Tooltip den Feldnamen wiederholte, steht jetzt ein formatierter Hilfetext: mit \u00dcberschriften, Hervorhebungen, Listen und Tabellen. Er beschreibt nicht nur, was ein Feld ist, sondern was es bewirkt \u2014 einschlie\u00dflich der Nebenwirkungen, die man sonst erst nach dem Speichern bemerkt.<\/p>\n<p class=\"MD_p\">Zu finden an den Options-Seiten aller Plugins sowie an den Dialogen, die etwas Erkl\u00e4rungsbed\u00fcrftiges tun: dem SBOM-Editor und seinen Eingabemasken, der Server-Karte und dem Verbindungs-Editor des MCP-Servers, dem Bearbeiten- und Auswahl-Dialog der Project ToDos und dem Kanban-Board.<\/p>\n<p class=\"MD_p\">Das Popup bleibt stehen, solange der Mauszeiger auf dem Feld steht \u2014 diese Texte sind zum Lesen gedacht, nicht zum \u00dcberfliegen.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Delphi MCP Server \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die Server-Auskunft (server_status) f\u00fchrt jetzt die Suite selbst auf: die Host-Komponente und jedes geladene Plugin mit Name, Version, Hersteller und Beschreibung. Damit ist im KI-Werkzeug unmittelbar sichtbar, welcher Stand tats\u00e4chlich l\u00e4uft.<\/li>\n<li class=\"MD_li\">Formular-Designer: Neue Komponenten landen zuverl\u00e4ssig unter dem angegebenen \u00fcbergeordneten Element, und die Komponentenliste bildet die tats\u00e4chliche Verschachtelung ab statt einer flachen Aufz\u00e4hlung.<\/li>\n<li class=\"MD_li\">Das Speichern mehrerer ge\u00e4nderter Dateien bricht nicht mehr beim ersten Fehler ab, sondern behandelt jede Datei einzeln und meldet je Datei, was geschehen ist.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Das Kanban-Board ist vollst\u00e4ndig \u00fcbersetzt, samt seiner Gruppierungsliste, und hat die neuen Hilfetexte erhalten.<\/li>\n<li class=\"MD_li\">Die manuelle Sortierung erzeugt wieder gleichm\u00e4\u00dfig verteilte Sortierschl\u00fcssel; bisher wuchsen sie beim Einf\u00fcgen unn\u00f6tig in die L\u00e4nge.<\/li>\n<li class=\"MD_li\">Verwaltungsdateien des Boards (z. B. _kanban.json) werden beim Einlesen der Aufgaben \u00fcbergangen und tauchen nicht mehr als vermeintliches Todo auf.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">SBOM Generator \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der Editor merkt sich zuverl\u00e4ssig, welche Datei er gerade bearbeitet. Bisher konnte es nach einem Wechsel zwischen ge\u00f6ffneten Modulen vorkommen, dass beim Speichern der Inhalt in das zuvor bearbeitete Modul zur\u00fcckgeschrieben wurde.<\/li>\n<li class=\"MD_li\">Die Fenster \"Virtuelle SBOMs\" und \"Externe Module\" sind \u00fcbersetzt, einschlie\u00dflich der Spalten\u00fcberschriften.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Schlie\u00dfen Sie RAD Studio vor der Installation; das Setup pr\u00fcft dies.<\/li>\n<li class=\"MD_li\">Eine vorhandene Installation wird \u00fcberschrieben; Ihre Einstellungen bleiben erhalten.<\/li>\n<li class=\"MD_li\">Die Sprache der Oberfl\u00e4che richtet sich nach der IDE. Wenn Sie die Sprache von RAD Studio umstellen, starten Sie die IDE danach neu.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.2.12.499<\/span><span class=\"msysdl-history__date\">12. August 2026 10:57<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Das zentrale Thema dieser Version ist die Aufnahme des Plugins \"MSYS Delphi MCP Server\" in die Suite: RAD Studio wird damit f\u00fcr KI-Werkzeuge wie Claude Code bedienbar. Daneben b\u00fcndelt die Suite ihre Einstellungen jetzt zentral in den IDE-Optionen und meldet sich beim IDE-Start auf Splashscreen und Info-Dialog von RAD Studio an.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: MSYS Delphi MCP Server \u2014 KI-Werkzeuge bedienen die IDE<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Das neue Plugin betreibt einen MCP-Server (Model Context Protocol) direkt im IDE-Prozess. KI-Assistenten wie Claude Code verbinden sich damit und arbeiten in der laufenden IDE: Quelltexte und Formulare lesen und \u00e4ndern, Projekte kompilieren, Anwendungen starten, debuggen und bedienen \u2014 unter Ihrer Aufsicht, in Ihrer ge\u00f6ffneten IDE.<\/p>\n<p class=\"MD_p\">Der Werkzeugumfang in Stichpunkten:<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Quelltext-Editor und Formular-Designer: Dateien \u00f6ffnen, lesen, \u00e4ndern und speichern; Komponenten anlegen, Eigenschaften und Ereignisse setzen.<\/li>\n<li class=\"MD_li\">Projekte: kompilieren, bereinigen, Build-Konfiguration wechseln, Projektoptionen (u. a. Suchpfade) lesen und schreiben; Meldungen und Build-Log abrufen.<\/li>\n<li class=\"MD_li\">Debugger: Anwendung starten (auch mit Startparametern), anhalten und fortsetzen, Haltepunkte verwalten, Einzelschritte, Threads und Aufrufliste einsehen, Ausdr\u00fccke auswerten und Werte \u00e4ndern.<\/li>\n<li class=\"MD_li\">Laufende Anwendung: Oberfl\u00e4che abfragen und bedienen (Klicks, Eingaben) \u2014 f\u00fcr Tests der eigenen Anwendung direkt aus dem KI-Werkzeug heraus.<\/li>\n<li class=\"MD_li\">Datenbanken: Verbindungen verwalten, SQL ausf\u00fchren und Schemata analysieren (\u00fcber FireDAC, Datenbank-Engine-neutral).<\/li>\n<li class=\"MD_li\">Project ToDos: Aufgaben lesen, anlegen und pflegen; \u00c4nderungen an den Aufgaben werden dem KI-Werkzeug aktiv gemeldet.<\/li>\n<\/ul>\n<p class=\"MD_p\">Sicherheit und Alltag: Gleichzeitige Zugriffe auf die IDE werden serialisiert; bei offenen modalen Dialogen verweigern die Werkzeuge den Zugriff kontrolliert, statt die IDE zu blockieren. Die Einstellungen des Servers finden Sie unter Tools &gt; Optionen.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">Suite &amp; IDE-Integration<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Einstellungen an einem Ort: Alle Plugins der Suite konfigurieren Sie jetzt zentral unter Tools &gt; Optionen in einer eigenen MSYS-Sektion \u2014 die bisherigen einzelnen Einstellungsdialoge entfallen.<\/li>\n<li class=\"MD_li\">Die Suite meldet sich beim IDE-Start an: mit eigenem Eintrag auf dem Splashscreen und im Info-Dialog von RAD Studio.<\/li>\n<li class=\"MD_li\">Neuer suite-interner Ereignis-Bus: Die Plugins informieren sich gegenseitig \u00fcber \u00c4nderungen \u2014 z. B. erf\u00e4hrt der MCP-Server sofort von ge\u00e4nderten Aufgaben der Project ToDos.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Spaltenbreiten und Sortierung der Aufgaben\u00fcbersicht werden mit dem IDE-Desktop gespeichert und wiederhergestellt.<\/li>\n<li class=\"MD_li\">Interne Dateien (z. B. gespeicherte Kanban-Einstellungen) erscheinen nicht mehr f\u00e4lschlich als Aufgaben.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">SBOM Generator \u2014 Verbesserungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die Konfiguration ist in die IDE-Optionen umgezogen: vier Seiten unter Tools &gt; Optionen ersetzen den bisherigen eigenen Einstellungsdialog.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Setup &amp; Deinstallation<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Wird die Installation \u00fcber die Benutzerkontensteuerung mit einem anderen Administratorkonto erhoben, landen die Registrierung der Suite und die Kachel der Startseite jetzt trotzdem zuverl\u00e4ssig im Profil des angemeldeten Benutzers \u2014 und die Deinstallation r\u00e4umt exakt dort wieder auf.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die Installation kann direkt \u00fcber eine bestehende Version erfolgen; eine Deinstallation ist nicht n\u00f6tig.<\/li>\n<li class=\"MD_li\">Die Delphi-IDE muss w\u00e4hrend der Installation geschlossen sein; das Setup pr\u00fcft dies automatisch.<\/li>\n<li class=\"MD_li\">Einstellungen: Die Plugin-Konfiguration finden Sie k\u00fcnftig unter Tools &gt; Optionen (siehe Abschnitt 2).<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.2.12.493<\/span><span class=\"msysdl-history__date\">29. July 2026 10:57<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version baut die Suite in allen Bereichen aus: ein neues Plugin (MSYS AutoReload), sp\u00fcrbare Komfort- und Stabilit\u00e4tsverbesserungen in der IDE sowie umfangreiche Erweiterungen des SBOM Generators samt vollst\u00e4ndigem Benutzerhandbuch. Die Produktversion entspricht ab dieser Version der Dateiversion der zentralen MSYS-Bibliothek.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">NEU: MSYS AutoReload \u2014 externe Datei\u00e4nderungen ohne Nachfrage<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Das neue Plugin \u00fcberwacht die in der IDE ge\u00f6ffneten Dateien (einschlie\u00dflich Begleitdateien wie JSON oder Markdown) und l\u00e4dt sie automatisch neu, wenn sie au\u00dferhalb der IDE ge\u00e4ndert wurden \u2014 etwa durch Werkzeuge, Skripte oder die Versionsverwaltung. Der Dialog \"Datei wurde au\u00dferhalb des Editors ge\u00e4ndert\" entf\u00e4llt f\u00fcr unver\u00e4nderte Editor-Inhalte komplett.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">Suite &amp; IDE-Integration<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Willkommensseite: Eine eigene MSYS-Kachel auf der RAD-Studio-Startseite zeigt die installierten Plugins der Suite auf einen Blick.<\/li>\n<li class=\"MD_li\">Meldungsfenster: Alle Meldungen der Suite erscheinen jetzt in einer eigenen Gruppe \"MSys\" \u2014 farbig nach Meldungsart (Info, Warnung, Fehler) und an das helle wie dunkle IDE-Theme angepasst.<\/li>\n<li class=\"MD_li\">About-Dialog: \u00fcberarbeitet, mit animiertem 3D-Logo und direktem Kontakt-Link; die Versions- und Herstellerangaben der Plugins werden zuverl\u00e4ssig aus den geladenen Modulen ermittelt.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">MSYS Project ToDos \u2014 Erweiterungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Der Bearbeitungsdialog zeigt die Aufgaben-ID an und erlaubt das direkte Bl\u00e4ttern von Aufgabe zu Aufgabe, ohne den Dialog zu verlassen.<\/li>\n<li class=\"MD_li\">Zuverl\u00e4ssigere Aktualisierung der Aufgaben\u00fcbersicht bei schnellen \u00c4nderungen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">SBOM Generator \u2014 Erweiterungen<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Vollst\u00e4ndiges Benutzerhandbuch: Der Funktionsumfang des Plugins ist jetzt durchg\u00e4ngig dokumentiert (Installation, Einstellungen, Editor, virtuelle SBOMs, externe Module, Fehlersuche); die CLI-Anleitung wurde \u00fcberarbeitet.<\/li>\n<li class=\"MD_li\">Bibliotheks- und Package-Projekte vervollst\u00e4ndigt: Die Projekt\u00fcbersicht (\"Project Info\") zeigt jetzt auch die Builds von DLL- und BPL-Projekten; in der SBOM erhalten sie den korrekten CycloneDX-Komponententyp \"library\".<\/li>\n<li class=\"MD_li\">PDF-Report: Nach dem Erstellen \u00fcber den \u2014 jetzt deutlich sichtbaren \u2014 PDF-Button \u00f6ffnet sich der Report automatisch im Standard-PDF-Viewer. Ein Fehler, der beim Erzeugen des Reports zum Absturz f\u00fchren konnte, wurde behoben.<\/li>\n<li class=\"MD_li\">Zuverl\u00e4ssigkeit im Alltag: Beim Kompilieren mit ge\u00f6ffneter SBOM-Datei erscheint keine \"Datei wurde ge\u00e4ndert\"-Nachfrage mehr; die Liste der virtuellen SBOMs aktualisiert sich selbstst\u00e4ndig; neu erstellte Projekte erzeugen keine wiederkehrenden Statusmeldungen mehr; Meldungen erscheinen ohne doppelte Kennzeichnung.<\/li>\n<li class=\"MD_li\">Kommandozeilen-Tools f\u00fcr CI\/CD: Die Tools SBomGen und GenSBOMReport verwenden jetzt benannte Parameter in der Form -name=wert (z. B. SBomGen -project=MyApp.dproj -platform=Win32 -config=Release). Neu sind die Parameter -extmodules= und -vsbom=, mit denen die Verzeichnisse f\u00fcr externe Module und virtuelle SBOMs pro Lauf \u00fcberschrieben werden k\u00f6nnen \u2014 die Daten k\u00f6nnen damit direkt aus dem Repository kommen, ohne das Benutzerprofil des Build-Agenten vorzubereiten. Hinweis: Die bisherige positionsbasierte Aufrufform wird nicht mehr unterst\u00fctzt; bestehende Build-Skripte m\u00fcssen einmalig angepasst werden.<\/li>\n<li class=\"MD_li\">Der grafische SBOM-Editor folgt jetzt vollst\u00e4ndig dem dunklen IDE-Theme.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"5\">\n<li class=\"MD_li\">Stabilit\u00e4t<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Ein Fehler beim Schlie\u00dfen der IDE mit geladenen Plugins (Zugriffsverletzung beim Herunterfahren) wurde behoben.<\/li>\n<li class=\"MD_li\">Die Logging-Infrastruktur der Suite wurde konsolidiert und ist durchg\u00e4ngig thread-sicher.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"6\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Die MSYS Delphi Tools k\u00f6nnen direkt \u00fcber eine bestehende Installation der Version 1.0.0 installiert werden; eine Deinstallation ist nicht n\u00f6tig.<\/li>\n<li class=\"MD_li\">Die Delphi-IDE muss w\u00e4hrend der Installation geschlossen sein; das Setup pr\u00fcft dies automatisch.<\/li>\n<li class=\"MD_li\">CI\/CD: Aufrufe der Kommandozeilen-Tools auf die neue -name=wert-Syntax umstellen (siehe Abschnitt 4).<\/li>\n<li class=\"MD_li\">Ausblick: Das Plugin \"MSYS Delphi MCP Server\" (Anbindung von KI-Werkzeugen an die IDE \u00fcber das Model Context Protocol) wurde weiter ausgebaut und bleibt Bestandteil einer kommenden Version.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.0.0.0<\/span><span class=\"msysdl-history__date\">24. June 2026 10:57<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Diese Version l\u00f6st den bisher einzeln ausgelieferten \"MSYS SBOM Generator 0.2.0 Beta\" ab. Aus dem einzelnen Plugin ist die Produktfamilie \"MSYS Delphi Tools\" geworden: eine modulare Sammlung von Erweiterungen f\u00fcr Embarcadero RAD Studio 13 (Delphi 13), die \u00fcber einen gemeinsamen Installer ausgeliefert wird.<\/p>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\">\n<li class=\"MD_li\">Neue Produktstruktur \u2014 eine Suite, ein Installer<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Ein zentrales Setup installiert alle Werkzeuge in einem Durchgang. Im Komponenten-Dialog w\u00e4hlen Sie aus, welche Plugins Sie nutzen m\u00f6chten \u2014 jedes Plugin ist einzeln an- und abw\u00e4hlbar.<\/li>\n<li class=\"MD_li\">Alle Plugins ordnen sich unter dem neuen gemeinsamen Hauptmen\u00fc \"MSys\" der IDE ein. Ein Men\u00fcpunkt, alle Werkzeuge.<\/li>\n<li class=\"MD_li\">Der Dialog \"About MSys\u2026\" zeigt auf einen Blick die installierte Version aller geladenen Plugins einschlie\u00dflich Hersteller-Angaben.<\/li>\n<li class=\"MD_li\">Die Plugin-Verwaltung \u00fcbernimmt das Paket selbst: In der IDE wird nur noch eine einzige Bibliothek registriert; die Plugins werden automatisch erkannt und geladen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"2\">\n<li class=\"MD_li\">NEU: MSYS Project ToDos \u2014 Aufgabenverwaltung im Projekt<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<p class=\"MD_p\">Mit \"Project ToDos\" erh\u00e4lt die IDE eine vollst\u00e4ndige, projektbezogene Aufgabenverwaltung. Aufgaben werden im Projektordner gespeichert und wandern damit gemeinsam mit dem Quellcode durch Ihre Versionsverwaltung \u2014 ideal f\u00fcr Teams.<\/p>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Andockbare Aufgaben\u00fcbersicht (MSys \u2192 Project Todos): alle Aufgaben des ge\u00f6ffneten Projekts mit Status, Priorit\u00e4t, Kategorie und Verantwortlichem; sortier- und filterbar. \u00c4nderungen am Projekt oder an den Aufgabendateien werden automatisch erkannt.<\/li>\n<li class=\"MD_li\">Komfortabler Bearbeitungsdialog: Jede Aufgabe besteht aus einem kompakten Eintrag und einer ausf\u00fchrlichen Notiz im Markdown-Format \u2014 Platz f\u00fcr Spezifikationen, Akzeptanzkriterien und Checklisten.<\/li>\n<li class=\"MD_li\">Kanban-Board (MSys \u2192 Project Todos Kanban): Aufgaben als Karten in Spalten, per Drag &amp; Drop verschiebbar. Die Gruppierung ist umschaltbar nach Status, Kategorie oder Priorit\u00e4t; Spaltenfarben und ausgeblendete Spalten werden je Projekt gespeichert. Filter blenden erledigte und verworfene Aufgaben wahlweise aus.<\/li>\n<li class=\"MD_li\">Beziehungen zwischen Aufgaben: \"blockiert von\", \"bezieht sich auf\" und \"Duplikat von\". Blockierte Aufgaben werden in Liste und Board markiert; ein Tooltip zeigt, welche Aufgaben blockieren und welche blockiert werden.<\/li>\n<li class=\"MD_li\">Freie Reihenfolge: Aufgaben lassen sich per Drag &amp; Drop, Tastatur (Alt + Pfeiltasten) oder Kontextmen\u00fc manuell sortieren \u2014 die Reihenfolge bleibt dauerhaft erhalten.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"3\">\n<li class=\"MD_li\">SBOM Generator \u2014 Erweiterungen seit Version 0.2.0 Beta<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">CycloneDX 1.6: Erzeugte SBOM-Dateien folgen jetzt der CycloneDX-Spezifikation in Version 1.6 (bisher 1.5).<\/li>\n<li class=\"MD_li\">Komponenten-Editor: Der Reiter \"Components\" des grafischen SBOM-Editors ist nun vollst\u00e4ndig editierbar. Komponenten k\u00f6nnen manuell angelegt, bearbeitet und gel\u00f6scht werden.<\/li>\n<li class=\"MD_li\">Import von Hersteller-SBOMs: Liefert ein Drittanbieter eine eigene SBOM-Datei (*.cdx.json) mit, l\u00e4sst sie sich direkt in die SBOM des eigenen Projekts \u00fcbernehmen \u2014 einschlie\u00dflich Unterkomponenten und Abh\u00e4ngigkeitsgraph. Ebenso k\u00f6nnen Komponenten aus den eigenen virtuellen SBOMs \u00fcbernommen werden.<\/li>\n<li class=\"MD_li\">Externe Module: Neue Verwaltung f\u00fcr Fremdmodule, die nicht aus dem Delphi-Build stammen (z. B. mitgelieferte Dritt-DLLs). Ein Scanner erkennt solche Module automatisch; ein eigener Editor und eine andockbare \u00dcbersicht erlauben die Pflege der Paketinformationen, die anschlie\u00dfend in die erzeugte SBOM einflie\u00dfen. Die Zuordnung wird je Projekt gespeichert.<\/li>\n<li class=\"MD_li\">DLL- und BPL-Projekte: Die Erkennung des Ausgabetyps wurde \u00fcberarbeitet \u2014 SBOMs werden jetzt auch f\u00fcr Bibliotheks- und Package-Projekte korrekt erzeugt, nicht nur f\u00fcr Anwendungen.<\/li>\n<li class=\"MD_li\">Stabilit\u00e4t: Verbesserungen beim Laden und Entladen des Plugins sowie diverse Fehlerbehebungen.<\/li>\n<\/ul>\n<hr class=\"MD_hr\">\n<ol class=\"MD_ol\" start=\"4\">\n<li class=\"MD_li\">Hinweise zum Upgrade<\/li>\n<\/ol>\n<hr class=\"MD_hr\">\n<ul class=\"MD_ul\">\n<li class=\"MD_li\">Wenn der bisherige \"MSYS SBOM Generator 0.2.0 Beta\" installiert ist, deinstallieren Sie diesen bitte vor der Installation der MSYS Delphi Tools \u00fcber \"Apps &amp; Features\".<\/li>\n<li class=\"MD_li\">Die Delphi-IDE muss w\u00e4hrend der Installation geschlossen sein; das Setup pr\u00fcft dies automatisch.<\/li>\n<li class=\"MD_li\">Ausblick: Das Plugin \"MSYS Delphi MCP Server\" (Anbindung von KI-Werkzeugen an die IDE \u00fcber das Model Context Protocol) ist in Vorbereitung und wird Bestandteil einer kommenden Version sein.<\/li>\n<\/ul>\n<\/div><\/div><\/li><\/ul><\/div><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-622046c e-con-full e-flex e-con e-child\" data-id=\"622046c\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-5fef733 elementor-widget elementor-widget-msysdl_info\" data-id=\"5fef733\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--version\"><span class=\"msysdl-info__label\">Version: <\/span><span class=\"msysdl-info__value\">1.9.13.539<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-5799766 e-con-full e-flex e-con e-child\" data-id=\"5799766\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-8e1ec3c elementor-widget elementor-widget-msysdl_info\" data-id=\"8e1ec3c\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--release_date\"><span class=\"msysdl-info__label\">Release: <\/span><span class=\"msysdl-info__value\">26. October 2026 13:59<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-00c7639 e-con-full e-flex e-con e-child\" data-id=\"00c7639\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-8688dcf elementor-widget elementor-widget-msysdl_button\" data-id=\"8688dcf\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-dl\"><a class=\"msysdl-dl__btn\" href=\"https:\/\/maenken.systems\/msysdl\/15306\/latest\/\" rel=\"nofollow\">Download<\/a><span class=\"msysdl-dl__meta\"><\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-b284f2a e-con-full e-grid e-con e-child\" data-id=\"b284f2a\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;background_motion_fx_motion_fx_scrolling&quot;:&quot;yes&quot;,&quot;background_motion_fx_opacity_effect&quot;:&quot;yes&quot;,&quot;background_motion_fx_opacity_direction&quot;:&quot;in-out&quot;,&quot;background_motion_fx_opacity_range&quot;:{&quot;unit&quot;:&quot;%&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:{&quot;start&quot;:14,&quot;end&quot;:100}},&quot;background_motion_fx_scale_effect&quot;:&quot;yes&quot;,&quot;background_motion_fx_scale_direction&quot;:&quot;in-out-in&quot;,&quot;background_motion_fx_scale_speed&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:10,&quot;sizes&quot;:[]},&quot;background_motion_fx_opacity_level&quot;:{&quot;unit&quot;:&quot;px&quot;,&quot;size&quot;:10,&quot;sizes&quot;:[]},&quot;background_motion_fx_scale_range&quot;:{&quot;unit&quot;:&quot;%&quot;,&quot;size&quot;:&quot;&quot;,&quot;sizes&quot;:{&quot;start&quot;:20,&quot;end&quot;:80}},&quot;background_motion_fx_devices&quot;:[&quot;widescreen&quot;,&quot;desktop&quot;,&quot;tablet&quot;,&quot;mobile&quot;],&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-b7069d2 elementor-widget elementor-widget-elementskit-heading\" data-id=\"b7069d2\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"elementskit-heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"ekit-wid-con\" ><div class=\"ekit-heading elementskit-section-title-wraper text_center   ekit_heading_tablet-   ekit_heading_mobile-\"><h3 class=\"elementskit-section-subtitle  \">\n\t\t\t\t\t\tPlug-In Suite for Delphi\n\t\t\t\t\t<\/h3><h2 class=\"ekit-heading--title elementskit-section-title text_fill\">Code Formatter for <span>Delphi RAD<\/span><\/h2><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-3e8f98b e-con-full e-flex e-con e-child\" data-id=\"3e8f98b\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;gradient&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-f296849 elementor-widget elementor-widget-text-editor\" data-id=\"f296849\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Delphi 13.2<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-7822a56 e-con-full e-flex e-con e-child\" data-id=\"7822a56\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t<div class=\"elementor-element elementor-element-c95a4b4 e-con-full e-flex e-con e-child\" data-id=\"c95a4b4\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-e8365c7 elementor-widget elementor-widget-msysdl_history\" data-id=\"e8365c7\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_history.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"msysdl-history\" data-msysdl-history><button type=\"button\" class=\"msysdl-history__open\" aria-haspopup=\"dialog\">Release notes<\/button><div class=\"msysdl-history__modal\" role=\"dialog\" aria-modal=\"true\" aria-labelledby=\"msysdl-hist-title-3\" hidden><div class=\"msysdl-history__backdrop\" data-msysdl-close><\/div><div class=\"msysdl-history__dialog\" role=\"document\" tabindex=\"-1\"><button type=\"button\" class=\"msysdl-history__close\" data-msysdl-close aria-label=\"Close\">&times;<\/button><h2 class=\"msysdl-history__title\" id=\"msysdl-hist-title-3\">Version history<\/h2><ul class=\"msysdl-history__list\"><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.4.30.176<\/span><span class=\"msysdl-history__date\">26. October 2026 11:12<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-19-fixed\" class=\"MD_h2\">Fixed<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Generic parameter lists keep their tight spacing when an unconstrained parameter comes before a <code class=\"MD_code\">;<\/code>.<\/strong> A declaration such as <code class=\"MD_code\">function RegisterDecorator: TRegistration;<\/code> came out as <code class=\"MD_code\">RegisterDecorator &lt; TService; TDecorator: TService &gt; :<\/code>, spaced like two comparisons. Lists in which every group before the <code class=\"MD_code\">;<\/code> carried a constraint were already fine.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Continuation lines aligned at the opening bracket land under the first argument again<\/strong> when the brackets are padded inside. With <code class=\"MD_code\">delphi_align_at_open_bracket<\/code> and a space inside the brackets, wrapped arguments ended one column to the left of the first one, because the space behind the bracket was not counted.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">The English setup speaks English throughout.<\/strong> Three messages \u2014 the IDE is still running, no Delphi installation was found, and the option to start Delphi on the last page \u2014 appeared in German in the English setup as well.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-19-new\" class=\"MD_h2\">New<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Padding inside brackets per side.<\/strong> <code class=\"MD_code\">delphi_space_inside_parens<\/code> and <code class=\"MD_code\">delphi_space_inside_brackets<\/code> now take <code class=\"MD_code\">none<\/code>, <code class=\"MD_code\">open<\/code>, <code class=\"MD_code\">close<\/code> or <code class=\"MD_code\">both<\/code> instead of only on and off, so the space can go behind the opening bracket only, before the closing one only, or on both sides. <code class=\"MD_code\">true<\/code> and <code class=\"MD_code\">false<\/code> stay valid and mean <code class=\"MD_code\">both<\/code> and <code class=\"MD_code\">none<\/code>. In the options dialog a drop-down list per bracket kind replaces the check box. The setting applies to every pair, also to one spread over several lines.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Colons of declarations in one column.<\/strong> The new option <code class=\"MD_code\">delphi_align_declaration_colons<\/code> (off by default) lines up the colons of consecutive <code class=\"MD_code\">var<\/code>, <code class=\"MD_code\">const<\/code> and field declarations, with a space in front of each \u2014 the <code class=\"MD_code\">Name : Type<\/code> style, which so far could only be preserved, not produced. Parameter lists follow when parameter types are aligned as well; the colons of properties, case labels and function results stay where they are. In the options dialog the option sits with the other alignment cases.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.3.27.146<\/span><span class=\"msysdl-history__date\">16. October 2026 14:25<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-20-fixed\" class=\"MD_h2\">Fixed<\/h2>\n<p class=\"MD_p\">Unattended installs run through. With \/SILENT or \/VERYSILENT the installer still showed its closing message and waited for a click. Silent runs now show no dialog at all and write the outcome to the setup log (\/LOG).<\/p>\n<p class=\"MD_p\">The closing message names the right commands. It pointed to an \"MSys\" menu that the formatter does not have; it now names Ctrl+D, Edit &gt; Format Source and the options page under Tools &gt; Options &gt; MSys &gt; Delphi Formatter.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.2.0.24<\/span><span class=\"msysdl-history__date\">18. September 2026 12:07<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-21-1-delphi-132-the-formatter-runs-on-the-ides-own-formatter-interface\" class=\"MD_h2\">1. Delphi 13.2: the formatter runs on the IDE's own formatter interface<\/h2>\n<p class=\"MD_p\">Delphi 13.2 opens the code formatter to third parties, and this release is the first to use it. On 13.2 the IDE itself owns the command, the Edit-menu entry, the editor context menu, the Ctrl+D shortcut and the confirmation prompt \u2014 the formatter is a formatter, not a program that reaches into menus to get called.<\/p>\n<p class=\"MD_p\">What that changes for you is not the look of the menu but what the formatter is finally allowed to do:<\/p>\n<p class=\"MD_p\">Format a selection. Mark a few lines, format only those. The selection is snapped to whole lines and formatted with the whole file as context, so the result is exactly what a full run would have produced for those lines \u2014 and everything outside stays byte for byte as it was. Format when the file is saved. New in this release, off by default. Every save the IDE performs runs through it, including the ones it does on your behalf before a build. Format a line while typing. Reformats the line you leave with Enter, in complete silence. Still a pilot, off by default. Breakpoints and bookmarks keep their place. Formatting moves code between lines; the marks in the gutter now move with the code they were set on instead of staying on a line number. All of it sits behind the same safety gates as before: a file that does not lex, or whose blocks do not balance, is left exactly as it is.<\/p>\n<p class=\"MD_p\">On earlier Delphi versions nothing changes \u2014 the formatter keeps using the way it always has, and the options that only work through the new interface are not shown there at all rather than offered in vain.<\/p>\n<h2 id=\"msysdl-cl-21-2-fixed\" class=\"MD_h2\">2. Fixed<\/h2>\n<p class=\"MD_p\">The new interface is actually used, not just supported. The IDE publishes its formatter services under a versioned name, and asking for the plain one is not enough: the request came back empty, and the plugin quietly fell back to the old menu-based route although the interface was right there. The effect was invisible from the outside \u2014 same menu entry, same shortcut \u2014 but everything the interface offers stayed out of reach. Both names are now asked for. Formatting no longer adds a blank line at the end of the file. When the IDE writes the formatted text back, a trailing line break counts as a separator, while loading a file counts it as a terminator. Handing the break back therefore grew the file by one empty line after end.. The same asymmetry had already been fixed for the older route; both now share one treatment. The growth happened once, not on every run, which is what made it easy to overlook.<\/p>\n<h2 id=\"msysdl-cl-21-3-new\" class=\"MD_h2\">3. New<\/h2>\n<p class=\"MD_p\">Format when the file is saved (General \u2192 Format when the file is saved, default off). Saving runs the formatter over the file \u2014 Ctrl+S, Save all, and the saves the IDE performs on its own.<\/p>\n<p class=\"MD_p\">Two things make this safe to leave on. A file that does not lex or does not balance is saved unchanged, and the save path is completely silent: no confirmation, no notice, ever. Saving must not wait for a click, and a file being written is unfinished more often than not. And files excluded through delphi_format = false are not touched here either, so vendor and generated code stays out of it.<\/p>\n<p class=\"MD_p\">The option is a setting of the IDE integration, not part of a profile, and it deliberately has no .editorconfig key: the IDE asks for it without reference to any one file, so a per-directory value could not be attributed to anything.<\/p>\n<h2 id=\"msysdl-cl-21-4-by-design\" class=\"MD_h2\">4. By design<\/h2>\n<p class=\"MD_p\">No .editorconfig key for format-on-save. See above: the question the IDE asks carries no file, so there is nothing to resolve a per-directory setting against. Guessing one from the current editor window would be wrong the moment Save all writes several files at once. Options that need the new interface are hidden where it is missing, rather than shown and doing nothing. A profile carries their values regardless, so moving a profile between Delphi versions leaves them intact.<\/p>\n<h2 id=\"msysdl-cl-21-5-under-the-hood\" class=\"MD_h2\">5. Under the hood<\/h2>\n<p class=\"MD_p\">Built and verified against Delphi 13.2. The test suite covers 1477 checks; the full corpus run over a large open-source code base reports no file the formatter refuses and no unbalanced result.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.0.0.23<\/span><span class=\"msysdl-history__date\">14. September 2026 10:59<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-22-1-fixed\" class=\"MD_h2\">1. Fixed<\/h2>\n<p class=\"MD_p\">A string of apostrophes ending a line no longer derails the formatter. A literal like '''' \u2014 a regular string holding a single quote \u2014 may legally stand at the end of a line, for example in a wrapped concatenation. The formatter misread such a literal as the start of a multiline string: a file the compiler accepts was refused with a lexical error, and when the same shape appeared twice, everything between the two occurrences was silently treated as string content. Only an odd number of quotes opens a multiline string \u2014 the formatter now reads it that way too. An .editorconfig section listing several masks in braces works. A section such as [{<em class=\"MD_em\">.pas,<\/em>.dpr}] \u2014 a standard-conform way to address multiple file types \u2014 broke the settings resolution outright: on the command line every file under that .editorconfig was skipped with an error, and in the IDE the format command went silently dead. Wildcards inside the braces are now understood exactly like outside them. Alignment no longer pads statements after a case or try block. The column aligner lost track of where executable code begins once a case, try or repeat block closed, and from there on treated statements as declarations: with the initialization alignment switched on, a comparison like Ok := A = 1; gained stray spaces before its =. Declarations still align; statements are left alone again. array of record ... end keeps its shape. The anonymous record body in a type like TItems = array of record N: Integer; end; was not recognized: its fields fell out of the record, its end closed the surrounding type section instead, and every declaration after it dropped to the left margin \u2014 legal code, visibly torn apart. The same applies to file of record. Both now open a proper body, and the metaclass form class of X stays untouched. A {$REGION} pair only pairs when it really is one. The column pairing introduced for region directives assumed every opener and closer stands alone on its line; an {$ENDREGION} written behind code, or a region inside an asm body, silently derailed the bookkeeping and a later, unrelated closer inherited the wrong column. Unclean pairs are now left alone entirely \u2014 they simply follow the surrounding code, as they did before the pairing existed. Alignment options work again after a procedure ... of object; type. Such a procedure-type reference (and a generic constraint like ) was mistaken for the start of a record body that never ends, so from there to the end of the unit the constant and type alignments went silent. Only real bodies count now. threadvar sections wrap like var sections. The one-name-per-line option split var and const name lists but silently skipped threadvar, which declares exactly the same lists. A stray $ with no digits stops the formatter. A bare dollar sign is not a hex literal and does not compile; the formatter used to format the file regardless. It now refuses it untouched, exactly as it does for an unterminated string. The command line warns when the mirror folder overwrites itself. With --out and -r all results land flat in one folder; two same-named units from different subfolders used to overwrite each other without a word, so the mirror looked complete when it was not. Each collision now prints a warning naming both source files; the behaviour itself is unchanged. The options preview spaces its tabs the way you set them. The two panes used a fixed tab width of their own, so a sample containing tabs was laid out differently from the code the formatter would actually produce \u2014 the preview contradicted the very setting it was there to demonstrate. It now follows the tab width currently being edited, so a freshly typed value takes effect at once, like every other option on those pages. A {$REGION} and its {$ENDREGION} stay in the same column. The closer used to follow whatever the last line of code did, so a region wrapped around a routine whose body was indented ended up with its two halves two columns apart. A closer now follows its own opener \u2014 including the other way round, where a region inside a routine body moves along with it. Nested regions pair correctly, and a region written inside one branch of a conditional stays there. The \"indent else line\" setting is remembered again. It was written to the settings store but never read back, so switching it off held until the next IDE start and then quietly returned. Anyone who preferred the RTL-style else placement had to set it again after every restart. Two settings that could not be carried in an exported profile at all \u2014 format on typing, and the alignment at the opening bracket \u2014 now travel with it, alongside the option that joins a wrapped assignment. An inline variable written across two lines keeps its indentation. With var alone on one line and the declaration under it, the declaration was pulled back onto the var column \u2014 while the very same declaration under a routine's var section indents. Two spellings of one thing came out differently, and the one line the author had indented was the one that moved. The declaration now sits one level under its keyword, exactly where the routine section would put it; everything after the closing semicolon stays where it was. Repeated formatting in the editor no longer adds a line to the end of the file. Every run appended one empty line after end., so a file that was already formatted still came back changed, and its end drifted further down with each pass. The cause sat at the boundary to the editor buffer rather than in the formatter itself: the editor reads the last line break of a file as a terminator when it loads the file, but as a separator when text is written back into it, so handing a buffer back unchanged still grew it by one line. The round trip is exact now \u2014 a file whose end the formatter does not touch comes back untouched, and a file that genuinely ends in a blank line keeps it. A keyword used as a member name after a dot is no longer treated as an operator. class operator Vector.In(...) came out as class operator Vector. in (...) \u2014 the qualified name pulled apart and the member lowercased. The same happened to .And, .Div, .Is, .As, .Or and .Not. Operator overloads are exactly the code where such names have to appear, so this hit real libraries. A case label following an arm that ends in a nested case kept the inner case's indentation instead of returning to the label column. Only the first label after the nested block was affected, which is why it read as a one-off rather than a pattern. Nested inline if expressions (Delphi 13) lost every level of indentation: each then\/else line fell back to the statement column, so a four-level expression came out as one flat block. Each level now carries one continuation step, with then and else of the same if in one column. A stray blank line was no longer left before the closing keyword of an initialization or finalization section: with the corresponding option off \u2014 the default \u2014 the statements of such a section were re-indented onto the keyword's column instead of being left alone. The option is documented as \"keep as is\", and now it keeps. A unary sign no longer fuses with the keyword in front of it. then -1, else -2, not -Y and to -1 came out as then-1, else-2, not-Y and to-1 \u2014 legal, but they read as a single token. A class procedure or class function body directly after a uses, const or var section is no longer indented like a section entry. Only the class prefix made the difference: a plain procedure in the same spot closed the section and landed on the routine column, while a class method header was taken for one more entry of the section and pushed to the entries' column \u2014 even when it already stood at column 0, with the standard settings, and stable across runs, so reformatting never repaired it. A comment standing above such a header shared its fate. The section now ends at any routine header, prefixed or not. Reported by a user against a unit whose class-method implementations followed the implementation uses clause; measured against a large open source library, this moves the headers in twelve units back to the column their authors wrote. A routine body that slipped a level comes back. Comment out the end; of a procedure, format, and everything below it moves one level in \u2014 as it should. Restore the end; and format again, and the routine headers came back to the margin, but their begin and end lines stayed where the slip had put them, stable across runs, so reformatting never repaired it. The rule that protects a nested routine's own column had been keeping the outer routine's frame too. It now keeps only what it was made for; the begin, the end and a local var, const or type line are pulled back under their header again. Reported from the field with exactly that three-step sequence.<\/p>\n<h2 id=\"msysdl-cl-22-2-new\" class=\"MD_h2\">2. New<\/h2>\n<p class=\"MD_p\">A blank-line separator can be told not to split what belongs together. A separator guarantees a blank line in front of a keyword without asking whether the line above is part of the same thought. Two cases, and they point in opposite directions: a ruler comment written directly over implementation introduces that section, and a local type\/var\/const belongs to the routine header above it \u2014 both got a blank line pushed into them. The new option leaves both alone. It is off by default, so nothing changes unless you ask for it, and a unit-level type following a forward declaration keeps its blank line either way. Only profiles that have the separators running were ever affected.<\/p>\n<h2 id=\"msysdl-cl-22-3-clarified-and-pinned\" class=\"MD_h2\">3. Clarified and pinned<\/h2>\n<p class=\"MD_p\">The statements of a case-else branch now sit one level under their own else by default. Previously they stayed on the column of the other alternatives' statements, which left two levels between else and the code belonging to it. The setting has existed for a while; only its default changed. It has an effect solely in combination with the RTL-style else placement (the else line on the case column) \u2014 with the else line indented, both readings coincide and nothing moves. The option for that indent has moved into the \"Case statements\" group of the options dialog, where the rest of the case settings live. It used to sit under \"Declarations\", three rows away from anything to do with case. The help texts in the options dialog appear after one second instead of half a second. Crossing the page with the mouse no longer throws up help nobody asked for; a deliberate pause still shows it.<\/p>\n<h2 id=\"msysdl-cl-22-4-under-the-hood\" class=\"MD_h2\">4. Under the hood<\/h2>\n<p class=\"MD_p\">A deep pass over the engine consolidated duplicated internals: the property specifier words, the operator list that recognizes if-expressions and the synthesized-space factory each live in one shared place now, the re-indenter works on its own copy of the token stream instead of the caller's, and the command-line program calls the encoding round-trip unit directly. No behaviour change; the test suite grew by over a hundred checks pinning these and the fixes above.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.7.0.22<\/span><span class=\"msysdl-history__date\">17. August 2026 10:59<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-23-1-new\" class=\"MD_h2\">1. New<\/h2>\n<p class=\"MD_p\">Every option explains itself. Hovering an option anywhere in the settings dialog brings up its help: what the option does, a short example and the default \u2014 laid out for reading instead of squeezed into a single line of tooltip. All 90 options are covered, in English and German. It runs through the IDE's own hint mechanism, so it can never end up as a second popup competing with the usual one. The preview panes are syntax coloured and numbered. The Before and After panes used to paint their sample in one single colour. They now colour it per token \u2014 reserved words, strings, comments, numbers, directives \u2014 and the colours come from your own editor colour scheme, so the preview looks like the editor you actually work in. Both panes carry line numbers in a quiet gutter, which is what makes the two halves comparable: the same number on the left and on the right answers what the formatter did to that line. A scheme that cannot be read falls back to plain text on the correct background rather than to a guess. Collapse a line break after an assignment when the statement fits. A new option on the Line Breaks page \u2014 off by default \u2014 removes the break directly after an assignment's := if the whole statement then still fits within the right margin, so Result := followed by a short expression on the next line becomes one line again. Like the end\/else option it only ever merges: it never breaks a line, it only takes a break away. It stays out of the way where the layout was intentional \u2014 if the statement carries any further break, or the right-hand side is an anonymous method, it is left untouched. The statement is measured as though all its breaks were already gone, so the result does not depend on the current layout and reformatting again changes nothing. Requested by a user.<\/p>\n<h2 id=\"msysdl-cl-23-2-fixed\" class=\"MD_h2\">2. Fixed<\/h2>\n<p class=\"MD_p\">Five defects in this release share one trigger: they only appear once the reflow of line breaks is switched on, and the standard Delphi 12 configuration switches it on. Anyone who imported their existing settings met several of them at once, which is why the import had a reputation for producing odd results. The import itself turned out to be faithful \u2014 it was applying the options exactly as given, and the engine mishandled them.<\/p>\n<p class=\"MD_p\">An inline variable is no longer mistaken for a goto label. With Line break after a label active, var a: Integer := 1; was torn in two after the colon, leaving var a: on one line and Integer := 1; on the next. The rule recognised any identifier followed by a colon; it now requires what a label actually is \u2014 the start of a statement. Real labels still get their line break, and for I: Integer := 0 to 3 do stays in one piece. No more blank line before every inline variable. With Blank lines before a subsection set, a blank line was inserted ahead of any line starting with var, const or type \u2014 including an inline variable in the middle of a routine. In code written for Delphi 10.3 and later that put a blank line between nearly every statement. The separator now fires only where a declaration section can actually begin; genuine sections keep their blank line. Local declarations keep their indentation. Switching on either of the two routine-body indentation options pushed a routine's own var, const and type declarations to column 0 \u2014 actively, even when they had been correctly indented beforehand, while the begin\u2026end body kept indenting normally. Both options now leave the declarations one step under their keyword, for top-level and nested routines alike. Conditional branch-swap tails survive reflow. A tail of the form else{$ELSE}begin{$ENDIF} has to stay on one line \u2014 both passes of the engine depend on it. With Line break after begin active, the begin was separated from the directive behind it, the structural bookkeeping went astray, and the file ended up with unbalanced blocks. The formatter then refused it outright, so the affected units silently stayed unformatted. Measured against a large open source library, six units were affected; now none are. Variant records after a nested section no longer shift the rest of the file. When Indent type\/const sections inside a class or record body was on, a record variant part (case Integer of without an end of its own) following a nested var, const or type section left an open block behind. Every declaration after that record \u2014 up to and including the final end. \u2014 stayed one level too deep and never returned to column 0. Because the result was stable across runs, reformatting never repaired it. Inline variables in initialization and finalization are statements again. Those sections carry statements but open no block, so everything that asks \"are we in executable code?\" read them as declaration territory. An inline var there was taken for a declaration section: it pushed every following statement one level deeper, attracted the blank-line separator meant for real sections, and had the name list of var a, b: Integer; split at its comma. All three are gone, in both passes. A related case: a declaration written across two lines \u2014 var alone, the name below it \u2014 was read as a goto label and pulled to the label column. Directive lines follow their code instead of freezing. With directive indentation switched off, a {$IFDEF} line kept its original column literally. That was invisible until the block settings moved the code around it \u2014 then the directive stayed behind and ended up stranded between lines it no longer lined up with, which reads as if the conditional had not been understood at all. It now moves with the code, keeping exactly the distance the author gave it. Where nothing moves, nothing changes. Anonymous methods get their own indentation level again. An anonymous method passed as a call argument \u2014 TThread.Queue(nil, procedure begin \u2026 end) and every shape like it \u2014 had its whole contents pulled onto the column of its own begin. A for or if inside it lost its level as well, and its local var, const and type declarations sat on the same column as the keyword introducing them. The body now sits one step under its begin, and the declarations one step under their section keyword, while the begin itself stays where it belongs \u2014 attached to the call it is an argument of. This is not tied to an option: it happens with the standard settings, which is why it was reported from ordinary use. Measured against a large open source library, every one of the affected places now matches the column its authors had written by hand. A unit named Inline keeps its name. inline is a directive in Delphi, not a reserved word \u2014 but the formatter had it listed among the reserved words, so every identifier of that name was treated as a keyword and re-cased: unit Inline; came out as unit inline;, and the same happened in a uses clause or a qualified reference. Nothing stopped compiling, since Delphi does not distinguish case in identifiers, but the formatter was changing a name that belongs to the author. It is now handled like every other directive \u2014 overload, stdcall, register, deprecated were all already treated correctly, so this removes an inconsistency rather than adding a rule. One-line anonymous methods no longer make a whole unit unformattable. Passing an anonymous method as a call argument on a single line \u2014 Foo(procedure begin X := 1; end) \u2014 left a stray internal region behind whenever one of the two routine-body indentation options was on. A single occurrence still balanced out by chance; from the second one in a file the bookkeeping came apart, the safety net declared the file unsound, and the formatter refused it. The visible symptom was the worst kind: nothing happened at all, with no explanation. Measured against a large open source library, this was the last file in 366 that could not be formatted under any of six configuration profiles; all of them are now clean. A wrapped assignment keeps its indentation level. When an assignment is broken across lines without brackets, everything below the first line used to fall back to the column of the statement itself, so Result := and the expression belonging to it ended up side by side and the statement read as two. The continuation now sits one step in, anchored on the line that opened the assignment \u2014 so a right-hand side spanning three or four lines stays at one step instead of drifting further right with every line. Where the right-hand side is an anonymous method, its header, its local declarations, its body and its end each land on the level they belong to. Brackets keep priority, so a wrapped argument list is unaffected. Measured against a large open source library, this moves the formatter closer to what the authors wrote by several hundred lines. A for loop is no longer aligned like an assignment. With Align assignments switched on, a loop header standing between two assignments was padded into their column, so for I := 0 to 9 do came out as for I          := 0 to 9 do. The alignment looks for any := outside brackets, and a loop header's is spelled exactly like an assignment's \u2014 only the leading keyword tells them apart. It does now. Comments no longer drift when a section ends. A uses, var or const section ends at its semicolon \u2014 but the formatter kept treating the space after it as part of the section, so a comment standing between the section and the next routine was pulled in one level. That hit { TMyClass }, the comment the IDE itself writes above the first method body: the formatter moved a line nobody had touched. Such a comment now takes the level of the code it introduces. A comment inside a section still moves with its declarations, and one above a nested routine follows that routine rather than dropping to the margin. Measured on a large code base, this restores the author's own column in the great majority of cases. Compiler directives on the same spot follow the same rule, and a closing {$ENDIF} moves together with the {$IF} it belongs to. A note above a routine directive moves with it. The option that indents a stand-alone inline; or overload; line under its routine header moved the directive alone. In the very shape the option was built for \u2014 a note explaining why the directive is wrapped in a condition \u2014 the comment stayed behind on the old column, so a pair that had been written on one column came apart, and the result looked less like the original than before the option existed. The comment now takes the column of the directive it introduces, the same rule a comment above an else already followed. A comment that introduces an ordinary declaration keeps its place, and Indent comments: No still means every comment stays exactly where it is. Measured against a large open source library, this moves one single line in 366 units \u2014 the one from the report. The align page's preview demonstrates its own option again. The sample there had no hand-set columns in it, so switching Keep hand-set columns on changed nothing visible \u2014 the one thing the preview exists for. The sample now carries a hand-aligned = column and hand-aligned trailing comments, which shows all three behaviours in one snippet: the default collapses them, the preserve option keeps them, and the align options re-compute them.<\/p>\n<h2 id=\"msysdl-cl-23-3-under-the-hood\" class=\"MD_h2\">3. Under the hood<\/h2>\n<p class=\"MD_p\">Every defect above is pinned by regression checks that fail without their respective fix \u2014 including the column drift, which no balance check could catch. Verified against a large open source code base \u2014 366 units \u2014 under twelve different configuration profiles, not just the default one: no unbalanced unit, no file the formatter had to refuse, and under every one of the twelve a second pass over the formatted output changes nothing. The alignment options were measured against inline variables and leave them alone in every combination, at every nesting depth \u2014 that immunity is now pinned by a test as well.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.6.0.21<\/span><span class=\"msysdl-history__date\">12. August 2026 11:01<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-24-1-new\" class=\"MD_h2\">1. New<\/h2>\n<p class=\"MD_p\">Indent type\/const sections inside a class body. Many libraries \u2014 and the RTL itself \u2014 put a type or const section inside a class or record body and indent its declarations one level under the keyword. The formatter used to pull them back to the level of the section keyword, and the existing \"indent after sections\" option did not help: that one only ever covered the unit sections interface and implementation. The new option Indent type\/const sections inside a class or record body (Indentation page, or the .editorconfig key delphi<em class=\"MD_em\">indent<\/em>nested<em class=\"MD_em\">sections) covers the class-internal case. Default off, so nothing changes unless you ask for it; the indented region ends at the next visibility specifier, method declaration, further section keyword or the type's end, so it cannot spill into the rest of the file. Indent case-else statements under their own else. With the case-else placed on the case column, its statements used to stay on the arm column \u2014 two levels away from the else they belong to. The new option Indent case-else statements under their own else (Indentation page, .editorconfig key delphi<\/em>indent<em class=\"MD_em\">case<\/em>else<em class=\"MD_em\">contents) closes that gap. It only differs in exactly that pairing; with the default case-else placement both readings coincide. Indent directive lines under their routine header. A stand-alone inline;, overload; or stdcall; line \u2014 including the conditional form {$IF \u2026}inline;{$IFEND} \u2014 can now be indented one continuation step under the header it belongs to, via Indent directive lines under their routine header (Indentation page, .editorconfig key delphi<\/em>indent<em class=\"MD_em\">routine<\/em>directives). This is a matter of style rather than a defect: the ; after the parameter list ends the declaration, so the directive really is a line of its own and the flat reading is just as defensible \u2014 which is why the default is off. A comment between the header and the directive does not break the association. Keep hand-set columns. Manually aligned trailing comments and = columns in const blocks used to be collapsed to a single space \u2014 the formatter threw away work someone had done on purpose. The align options were no answer: they compute the minimal column and so replace one normalisation with another. The new option Keep hand-set columns (Align page, .editorconfig key delphi<em class=\"MD_em\">preserve<\/em>manual_columns) simply leaves such a run alone. It never widens a single space, so it cannot create alignment \u2014 it only keeps what is there. Default off.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.5.0.17<\/span><span class=\"msysdl-history__date\">10. August 2026 11:01<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">All changes in this release were driven by community feedback from the Delphi-PRAXiS beta threads \u2014 thank you to everyone who tested and reported.<\/p>\n<h2 id=\"msysdl-cl-25-1-fixed\" class=\"MD_h2\">1. Fixed<\/h2>\n<p class=\"MD_p\">The branch-swap conditional idiom no longer blocks formatting. The pattern where one preprocessor branch opens a case \u2026 of and the other contributes a begin instead \u2014 both sharing the closing ends, with {$ELSE} and {$ENDIF} sitting in the middle of one code line (else{$ELSE}begin{$ENDIF}) \u2014 used to make the whole file count as structurally unbalanced: with several occurrences the formatter refused the file (this is what made Spring4D's Spring.pas appear \"unformattable\"), and with exactly one occurrence everything after the pattern silently drifted two columns to the right. The formatter now recognizes this shape, follows the first branch \u2014 consistent with how conditional regions are handled everywhere else \u2014 and keeps the indentation stable. Other mid-line directive regions remain deliberately untouched, as documented under Known limits. The options dialog is readable again under a light IDE theme. The pane holding the options took its background from the editor colour scheme instead of the IDE theme. Since that scheme is chosen independently of the theme, anyone running a light IDE with a dark editor scheme \u2014 a very common combination \u2014 got a black options pane while the captions stayed dark, which left whole pages unreadable. Editor colours now dress the two preview panes only, where they belong; everything else follows the IDE theme, in both the light and the dark variant. The command-line formatter carries version information. Formatter.exe shipped without any version resource at all: neither Windows' file properties nor a deployment script could tell which build was in use. It now reports its version and vendor like the plugin does, and both are built from the same version number.<\/p>\n<h2 id=\"msysdl-cl-25-2-new\" class=\"MD_h2\">2. New<\/h2>\n<p class=\"MD_p\">Blank-line separators without switching on reflow. The separators that put blank lines at structural boundaries \u2014 between methods, before the final end., around sections \u2014 used to require the reflow master to be off, which meant that anyone who only wanted a blank line between methods had to hand the formatter their whole line layout as well. Inserting a blank line moves no code, so it never needed that: the new option Apply the separators even when user line breaks are kept (Blank Lines page, or the .editorconfig key delphi<em class=\"MD_em\">apply<\/em>blank<em class=\"MD_em\">line<\/em>separators) releases them on their own. The default is off, so nothing changes unless you ask for it. Verified against a large real-world code base: with the option on, the only difference to a normal run is blank lines \u2014 not a single token moves. Product page, version and contact are now in plain sight. The options dialog carries a slim header above every page: the product name with a link straight to the product page \u2014 opening the English or the German edition to match the IDE language \u2014 and the installed version on the right. Beta testers told us the previous placement was easy to miss, which made it unnecessarily hard to find out where to send feedback. Format while typing (pilot, opt-in). On IDEs that offer the native formatter interface \u2014 prepared for future RAD Studio versions \u2014 the formatter can now re-format the line the caret leaves with Enter \u2014 same rules and safety gates as Ctrl+D, but completely silent: an incomplete or unbalanced buffer (the normal state while typing) or an already-formatted line is a quiet no-op, and no dialog ever appears. Caret, breakpoints and bookmarks follow exactly. Strictly opt-in (default: off) via the new General-page option Format line on Enter or per project via the new .editorconfig key delphi<em class=\"MD_em\">format<\/em>on_type; semicolons, pasting and navigation never trigger it. The command-line formatter no longer overwrites files it could not read properly. When the formatter cannot make sense of a file's structure \u2014 it ends up with more block openers than closers \u2014 its indentation is a guess. The IDE has always refused such a buffer and left it alone; the command-line tool used to mention the fact in passing and rewrite the file anyway, with a success exit code. A batch run over a repository therefore wrote guessed indentation into exactly the files the IDE protects, and --check reported them as an ordinary formatting difference. Both now give the same answer: the file is reported as KEEP and left untouched, the run ends with its own exit code 3 so a build pipeline can tell \"needs formatting\" from \"cannot be formatted safely\", and --out still writes the file into the mirror directory, where it overwrites nothing. The new switch --best-effort restores the previous behaviour for anyone who wants it, exit code included.<\/p>\n<h2 id=\"msysdl-cl-25-3-under-the-hood\" class=\"MD_h2\">3. Under the hood<\/h2>\n<p class=\"MD_p\">Conditional branches no longer add up in the line-break pass. The reflow stage kept one structural tally across all branches of a {$IFDEF} region instead of following the first one, the way the indentation stage already did. A branch that opened or closed a block without closing or opening it again shifted that tally for the rest of the unit, after which whole families of line-break rules quietly stopped applying \u2014 or started applying \u2014 far away from the directive that caused it. The effect was invisible from the outside: the output stayed structurally sound and stable under repeated formatting, only the line breaks were placed as if a different file had been read. Both stages now follow the same rule. This only ever affected profiles with reflow enabled. A var or const parameter is no longer mistaken for a declaration section. With per-element wrapping of var\/const lists enabled, a routine taking a var parameter had the comma in a generic return type (IDictionary) broken as if it were a name-list separator, leaving the continuation dangling. The two meanings of the keyword are now kept apart.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.4.0.10<\/span><span class=\"msysdl-history__date\">23. July 2026 11:01<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Release 0.4.0.10 (from beta build 3.0.1 \/ GetIt). All changes below were driven by community feedback from the Delphi-PRAXiS beta threads \u2014 thank you to everyone who tested and reported.<\/p>\n<h2 id=\"msysdl-cl-26-1-fixed\" class=\"MD_h2\">1. Fixed<\/h2>\n<p class=\"MD_p\">Sources the formatter refused, or changed in ways it must not<\/p>\n<p class=\"MD_p\">Conditional compilation ({$IFDEF} \/ {$ELSE} \/ {$ENDIF}) \u2014 the big one<\/p>\n<p class=\"MD_p\">Sources whose conditional branches open or close blocks (begin, try, class, asm \u2026) could not be formatted at all: the formatter saw the code of every branch at once, counted openers and closers across branches and refused the whole file as \"unbalanced block structure\". The mirror case \u2014 a closer duplicated across branches \u2014 silently produced drifted indentation.<\/p>\n<p class=\"MD_p\">The structural bookkeeping is now branch-aware: at {$IF*} the formatter snapshots its state, walks every {$ELSE} \/ {$ELSEIF} branch from that same entry state and continues after {$ENDIF} \/ {$IFEND} with the first branch's exit state. Both directive families are supported, nested regions work, and column alignment no longer bridges across branch boundaries. The safety guarantee is unchanged: nothing is ever written when the source truly is unbalanced.<\/p>\n<p class=\"MD_p\">Known limits: include files ({$I}) that contribute block edges and directives sharing a line with code are by-design limits \u2014 now documented in the manual's \"Known limits\" section; some reflow-mode edge cases remain tracked.<\/p>\n<p class=\"MD_p\">Variant records refused every unit<\/p>\n<p class=\"MD_p\">Any unit containing a variant record (case Integer of inside a record) was refused with the same \"unbalanced\" message \u2014 without a single compiler directive involved. Fixed.<\/p>\n<p class=\"MD_p\">A closing end at the end of a statement line refused the whole file<\/p>\n<p class=\"MD_p\">A line that both finishes a statement and closes its block \u2014 B; end;, or the end); a compact one-line anonymous method leaves behind \u2014 made the formatter report the source as unbalanced and refuse it entirely, although the code is perfectly valid. The closer was consuming the pending continuation of an enclosing if \u2026 then \/ while \u2026 do instead of the block itself, so the block stayed open until the end of the file. A closer now always ends a block, wherever it sits on the line. This affected the default profile too, not just reflow \u2014 and in the cases that were not refused outright it silently pushed everything after that line further and further right.<\/p>\n<p class=\"MD_p\">asm blocks that end mid-line refused the file<\/p>\n<p class=\"MD_p\">The same class of defect as the previous fix, one code path over: after the end of an asm block the formatter stopped looking at the rest of that line, so a routine written as asm \u2026 end; end; lost its outer block and the file was refused. The remaining closers on the line are now counted.<\/p>\n<p class=\"MD_p\">Reflow could silently change what a string literal means<\/p>\n<p class=\"MD_p\">With line-break rules active, if C = '''' then Q; was reflowed so that the apostrophe literal ended up as the last token on its line. Delphi 12 reads a run of three or more apostrophes followed only by whitespace as the opening delimiter of a multiline string \u2014 so on the next run the formatter (correctly) read its own output as a multiline string and swallowed the following code. The result was a program with different meaning, and in some shapes one that no longer even parses. Such a literal is now never left at the end of a line. This also removes the last known case where formatting twice gave a different result than formatting once.<\/p>\n<p class=\"MD_p\">An unrelated .editorconfig could be applied to your file<\/p>\n<p class=\"MD_p\">The settings cascade walks from the file's own directory upwards \u2014 but one step past the drive root it produced the drive-relative form (C:), and asking Windows for C:.editorconfig means \".editorconfig in the current directory of that drive\". Files that had no .editorconfig of their own therefore silently picked up the one belonging to whatever directory the formatter happened to be started from \u2014 in the IDE that is not even a directory you chose. The cascade now stops at the drive root, so only the file's own path decides its settings.<\/p>\n<p class=\"MD_p\">Broken parentheses no longer produce file-wide indent drift<\/p>\n<p class=\"MD_p\">A source with a missing ) or ] used to pass the safety check silently \u2014 it only measured begin\/end blocks \u2014 and the continuation indent then drifted through the rest of the file. Unbalanced parentheses or brackets now share the same protection as unbalanced blocks: the IDE refuses with a precise message (\"unbalanced parentheses or brackets\") and leaves the buffer untouched. Such files cannot compile anyway; once the syntax is fixed, a single format run restores canonical indentation everywhere.<\/p>\n<p class=\"MD_p\">Layout<\/p>\n<p class=\"MD_p\">Alignment stopped working after branch-asymmetric conditionals<\/p>\n<p class=\"MD_p\">The aligner's nesting counters read every {$IFDEF} branch as if all of them were compiled at once \u2014 a begin in each branch counted twice, so behind such a conditional the aligner believed it was still inside executable code and quietly stopped aligning const\/var\/field blocks. The counters now follow the first branch only (the same first-branch-wins rule the conditional-fork indenter uses); behind the region the alignment is identical to a file containing just that branch.<\/p>\n<p class=\"MD_p\">Generics with conditional type arguments were spaced as comparisons<\/p>\n<p class=\"MD_p\">TList came out as TList ; \u2014 the generic matcher silently swallowed the directives and read both branches as one invalid token stream. The scan now follows the first branch and skips {$ELSE}\u2026{$ENDIF} whole (the same first-branch-wins rule the conditional-fork indenter uses), so the angle brackets stay generic-tight in every branch. Real comparisons next to directives keep their operator spacing.<\/p>\n<p class=\"MD_p\">Box-art comment headers were gutted<\/p>\n<p class=\"MD_p\">Under the default profile, decorative comment blocks such as the classic { Framework Name } unit headers lost their interior padding, and whitespace-only filler lines collapsed to {}. The comment-spacing option now does exactly what it says \u2014 it normalizes the single space inside the delimiters ({x} \u2194 { x }) \u2014 and treats everything beyond that (padding runs, frame lines like {******}, multi-line comments) as deliberate layout that survives byte-for-byte.<\/p>\n<p class=\"MD_p\">Nested if\/else indented misleadingly<\/p>\n<p class=\"MD_p\">In if A then if B then \u2026 else \u2026 chains the else branch was visually re-bound to the outer if, although Delphi binds it to the nearest one. The indentation now follows the language's actual binding \u2014 including through while \u2026 do in between, and without disturbing case-else handling.<\/p>\n<p class=\"MD_p\">Multi-line signatures and calls lost their continuation indent<\/p>\n<p class=\"MD_p\">Continuation lines of a multi-line parameter list or call were flattened to the same column as their head line. They now indent one continuation step past the line that opened the bracket; a closing-bracket line aligns with that opener line.<\/p>\n<p class=\"MD_p\">Statements after a mid-line finally \/ except were mis-indented<\/p>\n<p class=\"MD_p\">try \/ if A then \/ B; finally left the pending then continuation standing, so the statements of the finally part sat one step too deep.<\/p>\n<p class=\"MD_p\">The else of an unparenthesized if-expression looked like a second else<\/p>\n<p class=\"MD_p\">In if C then \/ X := if A \/ then 1 \/ else 2 \/ else \/ Y := 3; the first else belongs to the expression, the second to the statement \u2014 but the formatter pulled both onto the same column, so the code read as if one if had two else branches. The expression's else now stays at the expression's level. (The branch lines themselves keep their layout: an unparenthesized continuation is never indented an extra step \u2014 the same as X := A + \/ B;.)<\/p>\n<p class=\"MD_p\">Generic constraints were spaced as comparisons<\/p>\n<p class=\"MD_p\">TList came out as TList . Constraint lists (class, record, constructor, interface types, multiple parameter groups) are now recognized as generics.<\/p>\n<p class=\"MD_p\">Generics in parameter defaults were torn apart<\/p>\n<p class=\"MD_p\">A default value glued to a generic parameter type \u2014 Symbols: TArray= [] (no space before the =) \u2014 made the scanner read &gt;= as a single greater-or-equal operator. The generic then failed to be recognized and came out spaced as a comparison: TArray = []. Both the tight original and the previously damaged form now heal to TArray = []; a generic &amp;lt; also glues back to its type name. Real comparisons like a = c are untouched.<\/p>\n<p class=\"MD_p\">Delphi 13 if-expressions were staircased<\/p>\n<p class=\"MD_p\">A multi-line if-expression in parentheses \u2014 (if cond then &amp;#039;-&amp;#039; else &amp;#039;&amp;#039;) spread over lines \u2014 had its branch lines indented like a statement-if, one extra level per then\/else. Combined with the bracket-indent option this produced a staircase drifting right with every branch. Inside parentheses an if is always an expression (only an anonymous method&amp;#039;s begin re-enters statement territory \u2014 that case is recognized and unchanged), so the branch lines now get plain continuation indent. Statement-if formatting, dangling- else binding and case-else handling are untouched.<\/p>\n<p class=\"MD_p\">&amp;quot;else if&amp;quot; line breaks left the else hanging<\/p>\n<p class=\"MD_p\">With line-break rules active, if A then B else if C then D reflowed to then B else \u23ce if C. A statement-level else now always starts its own line; the existing option keeps controlling the gap between else and if (both settings of it now produce clean shapes). Delphi 13 if-expressions (x := if a then b else c) are never broken apart.<\/p>\n<p class=\"MD_p\">Line-break rules tore if-expressions apart<\/p>\n<p class=\"MD_p\">With reflow enabled, a Delphi 13 if-expression was laid out like a statement: S := (if A then &amp;#039;yes&amp;#039; else &amp;#039;no&amp;#039;); came back split across four lines. The first round of protection covered only the unparenthesized form and only two of the four rules involved, so both the parenthesized form and \u2014 with the then and simple instruction rules armed \u2014 even the bare one were still broken up. Inside parentheses an if is always an expression (an anonymous method&amp;#039;s begin re-enters statement territory), and those rules now leave both forms alone. Statement ifs keep breaking exactly as configured.<\/p>\n<p class=\"MD_p\">Command line<\/p>\n<p class=\"MD_p\">One bad file no longer aborts the whole run<\/p>\n<p class=\"MD_p\">A source that cannot be decoded (a stray byte in a file claiming UTF-8) made Formatter.exe stop right there \u2014 silently truncating a recursive sweep, even under --check where nothing is written at all. Such a file is now reported, counted as skipped and left untouched; the run continues and the exit code still reports the error.<\/p>\n<h2 id=\"msysdl-cl-26-2-new\" class=\"MD_h2\">2. New<\/h2>\n<p class=\"MD_p\">Blank lines around initialization\/finalization, and before the final end.<\/p>\n<p class=\"MD_p\">Two new structure separators and a new indent option close the gap the section separators left: delphi<em class=\"MD_em\">blank<\/em>lines<em class=\"MD_em\">around<\/em>initialization guarantees blank lines before and after the initialization\/ finalization keywords, delphi<em class=\"MD_em\">blank<\/em>lines<em class=\"MD_em\">before<\/em>final_end puts them before the closing end., and Indent initialization\/finalization contents indents the sections&amp;#039; statements one level like a begin..end block. All three are off by default \u2014 existing output stays byte-identical.<\/p>\n<p class=\"MD_p\">Unusable options are now hidden<\/p>\n<p class=\"MD_p\">When a master option turns a group of settings off, those settings used to stay visible \u2014 at best with a grayed group title, while the controls below still looked active (&amp;quot;It&amp;#039;s disturbing&amp;quot;). Dependent options are now hidden outright: with &amp;quot;Keep user line breaks&amp;quot; on (the default), the line-break rules, the whole Reflow page and the blank-line separators disappear (an explanatory note stays behind); the alignment tuning numbers hide while no alignment case is active; coupled or inert switches (colons-before-types coupling, case options without block indent, bracket indent under reflow) vanish with their masters. Toggling the master brings everything back \u2014 live, across pages, without reopening the dialog.<\/p>\n<p class=\"MD_p\">Readable, complete option texts<\/p>\n<p class=\"MD_p\">Longer labels were cut off \u2014 most visibly the note under Blank Lines and the &amp;quot;colons before type names&amp;quot; switch under Alignment, and more often in German, where the translations are longer than the English originals. Every page was measured against both languages: notes have room for their full text, long switch captions wrap instead of being clipped, and the drop-downs sit far enough right that no label can run into them. The explanatory notes are now laid out in paragraphs instead of one dense block.<\/p>\n<p class=\"MD_p\">The option previews now show real cases<\/p>\n<p class=\"MD_p\">The live before\/after preview on each options page demonstrates the constellations this release fixed: conditional branches carrying a try, case with else, box-art comment headers, generic constraints and defaults, multi-line call continuations, dangling else binding, {$REGION} blank lines and alignment groups broken by a directive \u2014 so every page shows its own options working on real code.<\/p>\n<p class=\"MD_p\">The line-break master is now a regular .editorconfig key<\/p>\n<p class=\"MD_p\">&amp;quot;Keep user line breaks&amp;quot; can be set from a project&amp;#039;s .editorconfig (delphi<em class=\"MD_em\">keep<\/em>user_linebreaks) like every other option, so a team can pin its line-break policy in the repository and an exported profile round-trips completely. This deliberately reverses the earlier safety stance that a repository file must never enable reflow.<\/p>\n<p class=\"MD_p\">Export writes what you see<\/p>\n<p class=\"MD_p\">Both export buttons (.config and .editorconfig) now write the values currently set in the options dialog, including pages you have edited but not yet applied \u2014 previously they silently wrote the last saved state, and the note explaining that is gone along with the behaviour.<\/p>\n<p class=\"MD_p\">The installer now serves both IDEs<\/p>\n<p class=\"MD_p\">The setup installs the 32-bit and the 64-bit design package side by side and registers each with its IDE (Known Packages \/ Known Packages x64) \u2014 Ctrl+D works in whichever RAD Studio 13 you launch. Both packages always carry the same version number; the installer build refuses to package mismatched builds.<\/p>\n<p class=\"MD_p\">Option: placement of the case-else line<\/p>\n<p class=\"MD_p\">A new switch &amp;quot;Indent else line&amp;quot; (delphi<em class=\"MD_em\">indent<\/em>case_else) controls where the else of a case statement sits: at the level of the alternative labels (default, unchanged behaviour) or at the case keyword \u2014 the classic RTL style. The statements below it remain governed by the existing case options.<\/p>\n<h2 id=\"msysdl-cl-26-3-clarified-and-pinned\" class=\"MD_h2\">3. Clarified and pinned<\/h2>\n<p class=\"MD_p\">Blank lines around {$REGION}: both halves of the request are covered by existing options \u2014 set Max. consecutive blank lines to 2 to preserve a two-blank region spacing, and Blank lines around compiler directives (reflow tier) to insert them. Documented in the manual and locked in by tests. &amp;quot;Ensure final newline&amp;quot; and &amp;quot;Enable formatting&amp;quot;: both reported against beta build 3.0.1; the current code base behaves correctly (the disable switch is honoured end to end, including the .editorconfig cascade, and the final-newline option is exact in both directions). Both behaviours are now locked in by tests. The 3.0.1 symptoms came from that build&amp;#039;s Revive-based IDE integration, which the native RAD Studio 13.2 formatter interface has since replaced. Options pages opening slowly: verified not to be the plugin \u2014 even empty pages build up slowly; the cost sits in RAD Studio&amp;#039;s own Tools\/Options page embedding and would affect any add-in equally. The limits of conditional handling are documented<\/p>\n<p class=\"MD_p\">Two constellations the conditional-fork model cannot cover by principle now have their own &amp;quot;Known limits&amp;quot; manual section (German and English): include files that contribute block structure (the formatter refuses honestly or, for an included begin, may indent differently after the spot - never damaging anything), and directive regions starting or ending next to code on the same line (left untouched). Each comes with a minimal example, the observable behavior and an .editorconfig opt-out recipe.<\/p>\n<h2 id=\"msysdl-cl-26-4-by-design\" class=\"MD_h2\">4. By design<\/h2>\n<p class=\"MD_p\">The options tree stays under the MSys node: requested twice from the community (&amp;quot;Third Party&amp;quot; placement); declined deliberately \u2014 the MSys node is the shared home for current and future MSys settings. Ctrl+D stays Ctrl+D: the format shortcut is not configurable \u2014 Ctrl+D has been the Delphi formatter&amp;#039;s key since the built-in one, and on RAD Studio 13.2 the IDE owns the command anyway. Plugins that also claim Ctrl+D (e.g. GExperts) offer configurable shortcuts on their side.<\/p>\n<h2 id=\"msysdl-cl-26-5-under-the-hood\" class=\"MD_h2\">5. Under the hood<\/h2>\n<p class=\"MD_p\">The regression suite grew from 744 to 970 checks; every repository fixture is now also verified to format balanced, and formatting twice is now pinned for reflow profiles too, not just the default one. New shared conditional-directive classifier used by the re-indenter and the aligner; community-provided reproduction sources joined the fixture set. Several of the defects above were found by the fix for another one: the mid-line closer and the multiline-string cases came out of reviewing the if-expression reflow, and the .editorconfig cascade bug out of measuring the multiline-string fix.<\/p>\n<\/div><\/div><\/li><\/ul><\/div><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-bc60c1a e-con-full e-flex e-con e-child\" data-id=\"bc60c1a\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-1f097cd elementor-widget elementor-widget-msysdl_info\" data-id=\"1f097cd\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--version\"><span class=\"msysdl-info__label\">Version: <\/span><span class=\"msysdl-info__value\">1.4.30.176<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-9441d42 e-con-full e-flex e-con e-child\" data-id=\"9441d42\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-5f2dda4 elementor-widget elementor-widget-msysdl_info\" data-id=\"5f2dda4\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--release_date\"><span class=\"msysdl-info__label\">Release: <\/span><span class=\"msysdl-info__value\">26. October 2026 11:12<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-768a6c8 e-con-full e-flex e-con e-child\" data-id=\"768a6c8\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-542abbd elementor-widget elementor-widget-msysdl_button\" data-id=\"542abbd\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-dl\"><a class=\"msysdl-dl__btn\" href=\"https:\/\/maenken.systems\/msysdl\/15309\/latest\/\" rel=\"nofollow\">Download<\/a><span class=\"msysdl-dl__meta\"><\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-629d13d e-con-full e-flex e-con e-child\" data-id=\"629d13d\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;gradient&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-b79efbd elementor-widget elementor-widget-text-editor\" data-id=\"b79efbd\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>Delphi 13<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-a93a40a e-con-full e-flex e-con e-child\" data-id=\"a93a40a\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t<div class=\"elementor-element elementor-element-e53a436 e-con-full e-flex e-con e-child\" data-id=\"e53a436\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-c31b626 elementor-widget elementor-widget-msysdl_history\" data-id=\"c31b626\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_history.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<div class=\"msysdl-history\" data-msysdl-history><button type=\"button\" class=\"msysdl-history__open\" aria-haspopup=\"dialog\">Release notes<\/button><div class=\"msysdl-history__modal\" role=\"dialog\" aria-modal=\"true\" aria-labelledby=\"msysdl-hist-title-4\" hidden><div class=\"msysdl-history__backdrop\" data-msysdl-close><\/div><div class=\"msysdl-history__dialog\" role=\"document\" tabindex=\"-1\"><button type=\"button\" class=\"msysdl-history__close\" data-msysdl-close aria-label=\"Close\">&times;<\/button><h2 class=\"msysdl-history__title\" id=\"msysdl-hist-title-4\">Version history<\/h2><ul class=\"msysdl-history__list\"><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.4.30.176<\/span><span class=\"msysdl-history__date\">26. October 2026 10:31<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-27-fixed\" class=\"MD_h2\">Fixed<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Generic parameter lists keep their tight spacing when an unconstrained parameter comes before a <code class=\"MD_code\">;<\/code>.<\/strong> A declaration such as <code class=\"MD_code\">function RegisterDecorator: TRegistration;<\/code> came out as <code class=\"MD_code\">RegisterDecorator &lt; TService; TDecorator: TService &gt; :<\/code>, spaced like two comparisons. Lists in which every group before the <code class=\"MD_code\">;<\/code> carried a constraint were already fine.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Continuation lines aligned at the opening bracket land under the first argument again<\/strong> when the brackets are padded inside. With <code class=\"MD_code\">delphi_align_at_open_bracket<\/code> and a space inside the brackets, wrapped arguments ended one column to the left of the first one, because the space behind the bracket was not counted.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">The English setup speaks English throughout.<\/strong> Three messages \u2014 the IDE is still running, no Delphi installation was found, and the option to start Delphi on the last page \u2014 appeared in German in the English setup as well.<\/li>\n<\/ul>\n<h2 id=\"msysdl-cl-27-new\" class=\"MD_h2\">New<\/h2>\n<ul class=\"MD_ul\">\n<li class=\"MD_li\"><strong class=\"MD_strong\">Padding inside brackets per side.<\/strong> <code class=\"MD_code\">delphi_space_inside_parens<\/code> and <code class=\"MD_code\">delphi_space_inside_brackets<\/code> now take <code class=\"MD_code\">none<\/code>, <code class=\"MD_code\">open<\/code>, <code class=\"MD_code\">close<\/code> or <code class=\"MD_code\">both<\/code> instead of only on and off, so the space can go behind the opening bracket only, before the closing one only, or on both sides. <code class=\"MD_code\">true<\/code> and <code class=\"MD_code\">false<\/code> stay valid and mean <code class=\"MD_code\">both<\/code> and <code class=\"MD_code\">none<\/code>. In the options dialog a drop-down list per bracket kind replaces the check box. The setting applies to every pair, also to one spread over several lines.<\/li>\n<li class=\"MD_li\"><strong class=\"MD_strong\">Colons of declarations in one column.<\/strong> The new option <code class=\"MD_code\">delphi_align_declaration_colons<\/code> (off by default) lines up the colons of consecutive <code class=\"MD_code\">var<\/code>, <code class=\"MD_code\">const<\/code> and field declarations, with a space in front of each \u2014 the <code class=\"MD_code\">Name : Type<\/code> style, which so far could only be preserved, not produced. Parameter lists follow when parameter types are aligned as well; the colons of properties, case labels and function results stay where they are. In the options dialog the option sits with the other alignment cases.<\/li>\n<\/ul>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.3.27.146<\/span><span class=\"msysdl-history__date\">16. October 2026 14:24<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-28-fixed\" class=\"MD_h2\">Fixed<\/h2>\n<p class=\"MD_p\">Unattended installs run through. With \/SILENT or \/VERYSILENT the installer still showed its closing message and waited for a click. Silent runs now show no dialog at all and write the outcome to the setup log (\/LOG).<\/p>\n<p class=\"MD_p\">The closing message names the right commands. It pointed to an \"MSys\" menu that the formatter does not have; it now names Ctrl+D, Edit &gt; Format Source and the options page under Tools &gt; Options &gt; MSys &gt; Delphi Formatter.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">1.0.0.23<\/span><span class=\"msysdl-history__date\">14. September 2026 12:06<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-29-1-fixed\" class=\"MD_h2\">1. Fixed<\/h2>\n<p class=\"MD_p\">A string of apostrophes ending a line no longer derails the formatter. A literal like '''' \u2014 a regular string holding a single quote \u2014 may legally stand at the end of a line, for example in a wrapped concatenation. The formatter misread such a literal as the start of a multiline string: a file the compiler accepts was refused with a lexical error, and when the same shape appeared twice, everything between the two occurrences was silently treated as string content. Only an odd number of quotes opens a multiline string \u2014 the formatter now reads it that way too. An .editorconfig section listing several masks in braces works. A section such as [{<em class=\"MD_em\">.pas,<\/em>.dpr}] \u2014 a standard-conform way to address multiple file types \u2014 broke the settings resolution outright: on the command line every file under that .editorconfig was skipped with an error, and in the IDE the format command went silently dead. Wildcards inside the braces are now understood exactly like outside them. Alignment no longer pads statements after a case or try block. The column aligner lost track of where executable code begins once a case, try or repeat block closed, and from there on treated statements as declarations: with the initialization alignment switched on, a comparison like Ok := A = 1; gained stray spaces before its =. Declarations still align; statements are left alone again. array of record ... end keeps its shape. The anonymous record body in a type like TItems = array of record N: Integer; end; was not recognized: its fields fell out of the record, its end closed the surrounding type section instead, and every declaration after it dropped to the left margin \u2014 legal code, visibly torn apart. The same applies to file of record. Both now open a proper body, and the metaclass form class of X stays untouched. A {$REGION} pair only pairs when it really is one. The column pairing introduced for region directives assumed every opener and closer stands alone on its line; an {$ENDREGION} written behind code, or a region inside an asm body, silently derailed the bookkeeping and a later, unrelated closer inherited the wrong column. Unclean pairs are now left alone entirely \u2014 they simply follow the surrounding code, as they did before the pairing existed. Alignment options work again after a procedure ... of object; type. Such a procedure-type reference (and a generic constraint like ) was mistaken for the start of a record body that never ends, so from there to the end of the unit the constant and type alignments went silent. Only real bodies count now. threadvar sections wrap like var sections. The one-name-per-line option split var and const name lists but silently skipped threadvar, which declares exactly the same lists. A stray $ with no digits stops the formatter. A bare dollar sign is not a hex literal and does not compile; the formatter used to format the file regardless. It now refuses it untouched, exactly as it does for an unterminated string. The command line warns when the mirror folder overwrites itself. With --out and -r all results land flat in one folder; two same-named units from different subfolders used to overwrite each other without a word, so the mirror looked complete when it was not. Each collision now prints a warning naming both source files; the behaviour itself is unchanged. The options preview spaces its tabs the way you set them. The two panes used a fixed tab width of their own, so a sample containing tabs was laid out differently from the code the formatter would actually produce \u2014 the preview contradicted the very setting it was there to demonstrate. It now follows the tab width currently being edited, so a freshly typed value takes effect at once, like every other option on those pages. A {$REGION} and its {$ENDREGION} stay in the same column. The closer used to follow whatever the last line of code did, so a region wrapped around a routine whose body was indented ended up with its two halves two columns apart. A closer now follows its own opener \u2014 including the other way round, where a region inside a routine body moves along with it. Nested regions pair correctly, and a region written inside one branch of a conditional stays there. The \"indent else line\" setting is remembered again. It was written to the settings store but never read back, so switching it off held until the next IDE start and then quietly returned. Anyone who preferred the RTL-style else placement had to set it again after every restart. Two settings that could not be carried in an exported profile at all \u2014 format on typing, and the alignment at the opening bracket \u2014 now travel with it, alongside the option that joins a wrapped assignment. An inline variable written across two lines keeps its indentation. With var alone on one line and the declaration under it, the declaration was pulled back onto the var column \u2014 while the very same declaration under a routine's var section indents. Two spellings of one thing came out differently, and the one line the author had indented was the one that moved. The declaration now sits one level under its keyword, exactly where the routine section would put it; everything after the closing semicolon stays where it was. Repeated formatting in the editor no longer adds a line to the end of the file. Every run appended one empty line after end., so a file that was already formatted still came back changed, and its end drifted further down with each pass. The cause sat at the boundary to the editor buffer rather than in the formatter itself: the editor reads the last line break of a file as a terminator when it loads the file, but as a separator when text is written back into it, so handing a buffer back unchanged still grew it by one line. The round trip is exact now \u2014 a file whose end the formatter does not touch comes back untouched, and a file that genuinely ends in a blank line keeps it. A keyword used as a member name after a dot is no longer treated as an operator. class operator Vector.In(...) came out as class operator Vector. in (...) \u2014 the qualified name pulled apart and the member lowercased. The same happened to .And, .Div, .Is, .As, .Or and .Not. Operator overloads are exactly the code where such names have to appear, so this hit real libraries. A case label following an arm that ends in a nested case kept the inner case's indentation instead of returning to the label column. Only the first label after the nested block was affected, which is why it read as a one-off rather than a pattern. Nested inline if expressions (Delphi 13) lost every level of indentation: each then\/else line fell back to the statement column, so a four-level expression came out as one flat block. Each level now carries one continuation step, with then and else of the same if in one column. A stray blank line was no longer left before the closing keyword of an initialization or finalization section: with the corresponding option off \u2014 the default \u2014 the statements of such a section were re-indented onto the keyword's column instead of being left alone. The option is documented as \"keep as is\", and now it keeps. A unary sign no longer fuses with the keyword in front of it. then -1, else -2, not -Y and to -1 came out as then-1, else-2, not-Y and to-1 \u2014 legal, but they read as a single token. A class procedure or class function body directly after a uses, const or var section is no longer indented like a section entry. Only the class prefix made the difference: a plain procedure in the same spot closed the section and landed on the routine column, while a class method header was taken for one more entry of the section and pushed to the entries' column \u2014 even when it already stood at column 0, with the standard settings, and stable across runs, so reformatting never repaired it. A comment standing above such a header shared its fate. The section now ends at any routine header, prefixed or not. Reported by a user against a unit whose class-method implementations followed the implementation uses clause; measured against a large open source library, this moves the headers in twelve units back to the column their authors wrote. A routine body that slipped a level comes back. Comment out the end; of a procedure, format, and everything below it moves one level in \u2014 as it should. Restore the end; and format again, and the routine headers came back to the margin, but their begin and end lines stayed where the slip had put them, stable across runs, so reformatting never repaired it. The rule that protects a nested routine's own column had been keeping the outer routine's frame too. It now keeps only what it was made for; the begin, the end and a local var, const or type line are pulled back under their header again. Reported from the field with exactly that three-step sequence.<\/p>\n<h2 id=\"msysdl-cl-29-2-new\" class=\"MD_h2\">2. New<\/h2>\n<p class=\"MD_p\">A blank-line separator can be told not to split what belongs together. A separator guarantees a blank line in front of a keyword without asking whether the line above is part of the same thought. Two cases, and they point in opposite directions: a ruler comment written directly over implementation introduces that section, and a local type\/var\/const belongs to the routine header above it \u2014 both got a blank line pushed into them. The new option leaves both alone. It is off by default, so nothing changes unless you ask for it, and a unit-level type following a forward declaration keeps its blank line either way. Only profiles that have the separators running were ever affected.<\/p>\n<h2 id=\"msysdl-cl-29-3-clarified-and-pinned\" class=\"MD_h2\">3. Clarified and pinned<\/h2>\n<p class=\"MD_p\">The statements of a case-else branch now sit one level under their own else by default. Previously they stayed on the column of the other alternatives' statements, which left two levels between else and the code belonging to it. The setting has existed for a while; only its default changed. It has an effect solely in combination with the RTL-style else placement (the else line on the case column) \u2014 with the else line indented, both readings coincide and nothing moves. The option for that indent has moved into the \"Case statements\" group of the options dialog, where the rest of the case settings live. It used to sit under \"Declarations\", three rows away from anything to do with case. The help texts in the options dialog appear after one second instead of half a second. Crossing the page with the mouse no longer throws up help nobody asked for; a deliberate pause still shows it.<\/p>\n<h2 id=\"msysdl-cl-29-4-under-the-hood\" class=\"MD_h2\">4. Under the hood<\/h2>\n<p class=\"MD_p\">A deep pass over the engine consolidated duplicated internals: the property specifier words, the operator list that recognizes if-expressions and the synthesized-space factory each live in one shared place now, the re-indenter works on its own copy of the token stream instead of the caller's, and the command-line program calls the encoding round-trip unit directly. No behaviour change; the test suite grew by over a hundred checks pinning these and the fixes above.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.7.0.22<\/span><span class=\"msysdl-history__date\">17. August 2026 11:10<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-30-1-new\" class=\"MD_h2\">1. New<\/h2>\n<p class=\"MD_p\">Every option explains itself. Hovering an option anywhere in the settings dialog brings up its help: what the option does, a short example and the default \u2014 laid out for reading instead of squeezed into a single line of tooltip. All 90 options are covered, in English and German. It runs through the IDE's own hint mechanism, so it can never end up as a second popup competing with the usual one. The preview panes are syntax coloured and numbered. The Before and After panes used to paint their sample in one single colour. They now colour it per token \u2014 reserved words, strings, comments, numbers, directives \u2014 and the colours come from your own editor colour scheme, so the preview looks like the editor you actually work in. Both panes carry line numbers in a quiet gutter, which is what makes the two halves comparable: the same number on the left and on the right answers what the formatter did to that line. A scheme that cannot be read falls back to plain text on the correct background rather than to a guess. Collapse a line break after an assignment when the statement fits. A new option on the Line Breaks page \u2014 off by default \u2014 removes the break directly after an assignment's := if the whole statement then still fits within the right margin, so Result := followed by a short expression on the next line becomes one line again. Like the end\/else option it only ever merges: it never breaks a line, it only takes a break away. It stays out of the way where the layout was intentional \u2014 if the statement carries any further break, or the right-hand side is an anonymous method, it is left untouched. The statement is measured as though all its breaks were already gone, so the result does not depend on the current layout and reformatting again changes nothing. Requested by a user.<\/p>\n<h2 id=\"msysdl-cl-30-2-fixed\" class=\"MD_h2\">2. Fixed<\/h2>\n<p class=\"MD_p\">Five defects in this release share one trigger: they only appear once the reflow of line breaks is switched on, and the standard Delphi 12 configuration switches it on. Anyone who imported their existing settings met several of them at once, which is why the import had a reputation for producing odd results. The import itself turned out to be faithful \u2014 it was applying the options exactly as given, and the engine mishandled them.<\/p>\n<p class=\"MD_p\">An inline variable is no longer mistaken for a goto label. With Line break after a label active, var a: Integer := 1; was torn in two after the colon, leaving var a: on one line and Integer := 1; on the next. The rule recognised any identifier followed by a colon; it now requires what a label actually is \u2014 the start of a statement. Real labels still get their line break, and for I: Integer := 0 to 3 do stays in one piece. No more blank line before every inline variable. With Blank lines before a subsection set, a blank line was inserted ahead of any line starting with var, const or type \u2014 including an inline variable in the middle of a routine. In code written for Delphi 10.3 and later that put a blank line between nearly every statement. The separator now fires only where a declaration section can actually begin; genuine sections keep their blank line. Local declarations keep their indentation. Switching on either of the two routine-body indentation options pushed a routine's own var, const and type declarations to column 0 \u2014 actively, even when they had been correctly indented beforehand, while the begin\u2026end body kept indenting normally. Both options now leave the declarations one step under their keyword, for top-level and nested routines alike. Conditional branch-swap tails survive reflow. A tail of the form else{$ELSE}begin{$ENDIF} has to stay on one line \u2014 both passes of the engine depend on it. With Line break after begin active, the begin was separated from the directive behind it, the structural bookkeeping went astray, and the file ended up with unbalanced blocks. The formatter then refused it outright, so the affected units silently stayed unformatted. Measured against a large open source library, six units were affected; now none are. Variant records after a nested section no longer shift the rest of the file. When Indent type\/const sections inside a class or record body was on, a record variant part (case Integer of without an end of its own) following a nested var, const or type section left an open block behind. Every declaration after that record \u2014 up to and including the final end. \u2014 stayed one level too deep and never returned to column 0. Because the result was stable across runs, reformatting never repaired it. Inline variables in initialization and finalization are statements again. Those sections carry statements but open no block, so everything that asks \"are we in executable code?\" read them as declaration territory. An inline var there was taken for a declaration section: it pushed every following statement one level deeper, attracted the blank-line separator meant for real sections, and had the name list of var a, b: Integer; split at its comma. All three are gone, in both passes. A related case: a declaration written across two lines \u2014 var alone, the name below it \u2014 was read as a goto label and pulled to the label column. Directive lines follow their code instead of freezing. With directive indentation switched off, a {$IFDEF} line kept its original column literally. That was invisible until the block settings moved the code around it \u2014 then the directive stayed behind and ended up stranded between lines it no longer lined up with, which reads as if the conditional had not been understood at all. It now moves with the code, keeping exactly the distance the author gave it. Where nothing moves, nothing changes. Anonymous methods get their own indentation level again. An anonymous method passed as a call argument \u2014 TThread.Queue(nil, procedure begin \u2026 end) and every shape like it \u2014 had its whole contents pulled onto the column of its own begin. A for or if inside it lost its level as well, and its local var, const and type declarations sat on the same column as the keyword introducing them. The body now sits one step under its begin, and the declarations one step under their section keyword, while the begin itself stays where it belongs \u2014 attached to the call it is an argument of. This is not tied to an option: it happens with the standard settings, which is why it was reported from ordinary use. Measured against a large open source library, every one of the affected places now matches the column its authors had written by hand. A unit named Inline keeps its name. inline is a directive in Delphi, not a reserved word \u2014 but the formatter had it listed among the reserved words, so every identifier of that name was treated as a keyword and re-cased: unit Inline; came out as unit inline;, and the same happened in a uses clause or a qualified reference. Nothing stopped compiling, since Delphi does not distinguish case in identifiers, but the formatter was changing a name that belongs to the author. It is now handled like every other directive \u2014 overload, stdcall, register, deprecated were all already treated correctly, so this removes an inconsistency rather than adding a rule. One-line anonymous methods no longer make a whole unit unformattable. Passing an anonymous method as a call argument on a single line \u2014 Foo(procedure begin X := 1; end) \u2014 left a stray internal region behind whenever one of the two routine-body indentation options was on. A single occurrence still balanced out by chance; from the second one in a file the bookkeeping came apart, the safety net declared the file unsound, and the formatter refused it. The visible symptom was the worst kind: nothing happened at all, with no explanation. Measured against a large open source library, this was the last file in 366 that could not be formatted under any of six configuration profiles; all of them are now clean. A wrapped assignment keeps its indentation level. When an assignment is broken across lines without brackets, everything below the first line used to fall back to the column of the statement itself, so Result := and the expression belonging to it ended up side by side and the statement read as two. The continuation now sits one step in, anchored on the line that opened the assignment \u2014 so a right-hand side spanning three or four lines stays at one step instead of drifting further right with every line. Where the right-hand side is an anonymous method, its header, its local declarations, its body and its end each land on the level they belong to. Brackets keep priority, so a wrapped argument list is unaffected. Measured against a large open source library, this moves the formatter closer to what the authors wrote by several hundred lines. A for loop is no longer aligned like an assignment. With Align assignments switched on, a loop header standing between two assignments was padded into their column, so for I := 0 to 9 do came out as for I          := 0 to 9 do. The alignment looks for any := outside brackets, and a loop header's is spelled exactly like an assignment's \u2014 only the leading keyword tells them apart. It does now. Comments no longer drift when a section ends. A uses, var or const section ends at its semicolon \u2014 but the formatter kept treating the space after it as part of the section, so a comment standing between the section and the next routine was pulled in one level. That hit { TMyClass }, the comment the IDE itself writes above the first method body: the formatter moved a line nobody had touched. Such a comment now takes the level of the code it introduces. A comment inside a section still moves with its declarations, and one above a nested routine follows that routine rather than dropping to the margin. Measured on a large code base, this restores the author's own column in the great majority of cases. Compiler directives on the same spot follow the same rule, and a closing {$ENDIF} moves together with the {$IF} it belongs to. A note above a routine directive moves with it. The option that indents a stand-alone inline; or overload; line under its routine header moved the directive alone. In the very shape the option was built for \u2014 a note explaining why the directive is wrapped in a condition \u2014 the comment stayed behind on the old column, so a pair that had been written on one column came apart, and the result looked less like the original than before the option existed. The comment now takes the column of the directive it introduces, the same rule a comment above an else already followed. A comment that introduces an ordinary declaration keeps its place, and Indent comments: No still means every comment stays exactly where it is. Measured against a large open source library, this moves one single line in 366 units \u2014 the one from the report. The align page's preview demonstrates its own option again. The sample there had no hand-set columns in it, so switching Keep hand-set columns on changed nothing visible \u2014 the one thing the preview exists for. The sample now carries a hand-aligned = column and hand-aligned trailing comments, which shows all three behaviours in one snippet: the default collapses them, the preserve option keeps them, and the align options re-compute them.<\/p>\n<h2 id=\"msysdl-cl-30-3-under-the-hood\" class=\"MD_h2\">3. Under the hood<\/h2>\n<p class=\"MD_p\">Every defect above is pinned by regression checks that fail without their respective fix \u2014 including the column drift, which no balance check could catch. Verified against a large open source code base \u2014 366 units \u2014 under twelve different configuration profiles, not just the default one: no unbalanced unit, no file the formatter had to refuse, and under every one of the twelve a second pass over the formatted output changes nothing. The alignment options were measured against inline variables and leave them alone in every combination, at every nesting depth \u2014 that immunity is now pinned by a test as well.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.6.0.21<\/span><span class=\"msysdl-history__date\">12. August 2026 11:18<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><h2 id=\"msysdl-cl-31-1-new\" class=\"MD_h2\">1. New<\/h2>\n<p class=\"MD_p\">Indent type\/const sections inside a class body. Many libraries \u2014 and the RTL itself \u2014 put a type or const section inside a class or record body and indent its declarations one level under the keyword. The formatter used to pull them back to the level of the section keyword, and the existing \"indent after sections\" option did not help: that one only ever covered the unit sections interface and implementation. The new option Indent type\/const sections inside a class or record body (Indentation page, or the .editorconfig key delphi<em class=\"MD_em\">indent<\/em>nested<em class=\"MD_em\">sections) covers the class-internal case. Default off, so nothing changes unless you ask for it; the indented region ends at the next visibility specifier, method declaration, further section keyword or the type's end, so it cannot spill into the rest of the file. Indent case-else statements under their own else. With the case-else placed on the case column, its statements used to stay on the arm column \u2014 two levels away from the else they belong to. The new option Indent case-else statements under their own else (Indentation page, .editorconfig key delphi<\/em>indent<em class=\"MD_em\">case<\/em>else<em class=\"MD_em\">contents) closes that gap. It only differs in exactly that pairing; with the default case-else placement both readings coincide. Indent directive lines under their routine header. A stand-alone inline;, overload; or stdcall; line \u2014 including the conditional form {$IF \u2026}inline;{$IFEND} \u2014 can now be indented one continuation step under the header it belongs to, via Indent directive lines under their routine header (Indentation page, .editorconfig key delphi<\/em>indent<em class=\"MD_em\">routine<\/em>directives). This is a matter of style rather than a defect: the ; after the parameter list ends the declaration, so the directive really is a line of its own and the flat reading is just as defensible \u2014 which is why the default is off. A comment between the header and the directive does not break the association. Keep hand-set columns. Manually aligned trailing comments and = columns in const blocks used to be collapsed to a single space \u2014 the formatter threw away work someone had done on purpose. The align options were no answer: they compute the minimal column and so replace one normalisation with another. The new option Keep hand-set columns (Align page, .editorconfig key delphi<em class=\"MD_em\">preserve<\/em>manual_columns) simply leaves such a run alone. It never widens a single space, so it cannot create alignment \u2014 it only keeps what is there. Default off.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.5.0.17<\/span><span class=\"msysdl-history__date\">10. August 2026 11:18<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">All changes in this release were driven by community feedback from the Delphi-PRAXiS beta threads \u2014 thank you to everyone who tested and reported.<\/p>\n<h2 id=\"msysdl-cl-32-1-fixed\" class=\"MD_h2\">1. Fixed<\/h2>\n<p class=\"MD_p\">The branch-swap conditional idiom no longer blocks formatting. The pattern where one preprocessor branch opens a case \u2026 of and the other contributes a begin instead \u2014 both sharing the closing ends, with {$ELSE} and {$ENDIF} sitting in the middle of one code line (else{$ELSE}begin{$ENDIF}) \u2014 used to make the whole file count as structurally unbalanced: with several occurrences the formatter refused the file (this is what made Spring4D's Spring.pas appear \"unformattable\"), and with exactly one occurrence everything after the pattern silently drifted two columns to the right. The formatter now recognizes this shape, follows the first branch \u2014 consistent with how conditional regions are handled everywhere else \u2014 and keeps the indentation stable. Other mid-line directive regions remain deliberately untouched, as documented under Known limits. The options dialog is readable again under a light IDE theme. The pane holding the options took its background from the editor colour scheme instead of the IDE theme. Since that scheme is chosen independently of the theme, anyone running a light IDE with a dark editor scheme \u2014 a very common combination \u2014 got a black options pane while the captions stayed dark, which left whole pages unreadable. Editor colours now dress the two preview panes only, where they belong; everything else follows the IDE theme, in both the light and the dark variant. The command-line formatter carries version information. Formatter.exe shipped without any version resource at all: neither Windows' file properties nor a deployment script could tell which build was in use. It now reports its version and vendor like the plugin does, and both are built from the same version number.<\/p>\n<h2 id=\"msysdl-cl-32-2-new\" class=\"MD_h2\">2. New<\/h2>\n<p class=\"MD_p\">Blank-line separators without switching on reflow. The separators that put blank lines at structural boundaries \u2014 between methods, before the final end., around sections \u2014 used to require the reflow master to be off, which meant that anyone who only wanted a blank line between methods had to hand the formatter their whole line layout as well. Inserting a blank line moves no code, so it never needed that: the new option Apply the separators even when user line breaks are kept (Blank Lines page, or the .editorconfig key delphi<em class=\"MD_em\">apply<\/em>blank<em class=\"MD_em\">line<\/em>separators) releases them on their own. The default is off, so nothing changes unless you ask for it. Verified against a large real-world code base: with the option on, the only difference to a normal run is blank lines \u2014 not a single token moves. Product page, version and contact are now in plain sight. The options dialog carries a slim header above every page: the product name with a link straight to the product page \u2014 opening the English or the German edition to match the IDE language \u2014 and the installed version on the right. Beta testers told us the previous placement was easy to miss, which made it unnecessarily hard to find out where to send feedback. Format while typing (pilot, opt-in). On IDEs that offer the native formatter interface \u2014 prepared for future RAD Studio versions \u2014 the formatter can now re-format the line the caret leaves with Enter \u2014 same rules and safety gates as Ctrl+D, but completely silent: an incomplete or unbalanced buffer (the normal state while typing) or an already-formatted line is a quiet no-op, and no dialog ever appears. Caret, breakpoints and bookmarks follow exactly. Strictly opt-in (default: off) via the new General-page option Format line on Enter or per project via the new .editorconfig key delphi<em class=\"MD_em\">format<\/em>on_type; semicolons, pasting and navigation never trigger it. The command-line formatter no longer overwrites files it could not read properly. When the formatter cannot make sense of a file's structure \u2014 it ends up with more block openers than closers \u2014 its indentation is a guess. The IDE has always refused such a buffer and left it alone; the command-line tool used to mention the fact in passing and rewrite the file anyway, with a success exit code. A batch run over a repository therefore wrote guessed indentation into exactly the files the IDE protects, and --check reported them as an ordinary formatting difference. Both now give the same answer: the file is reported as KEEP and left untouched, the run ends with its own exit code 3 so a build pipeline can tell \"needs formatting\" from \"cannot be formatted safely\", and --out still writes the file into the mirror directory, where it overwrites nothing. The new switch --best-effort restores the previous behaviour for anyone who wants it, exit code included.<\/p>\n<h2 id=\"msysdl-cl-32-3-under-the-hood\" class=\"MD_h2\">3. Under the hood<\/h2>\n<p class=\"MD_p\">Conditional branches no longer add up in the line-break pass. The reflow stage kept one structural tally across all branches of a {$IFDEF} region instead of following the first one, the way the indentation stage already did. A branch that opened or closed a block without closing or opening it again shifted that tally for the rest of the unit, after which whole families of line-break rules quietly stopped applying \u2014 or started applying \u2014 far away from the directive that caused it. The effect was invisible from the outside: the output stayed structurally sound and stable under repeated formatting, only the line breaks were placed as if a different file had been read. Both stages now follow the same rule. This only ever affected profiles with reflow enabled. A var or const parameter is no longer mistaken for a declaration section. With per-element wrapping of var\/const lists enabled, a routine taking a var parameter had the comma in a generic return type (IDictionary) broken as if it were a name-list separator, leaving the continuation dangling. The two meanings of the keyword are now kept apart.<\/p>\n<\/div><\/div><\/li><li class=\"msysdl-history__item\"><div class=\"msysdl-history__head\"><span class=\"msysdl-history__ver\">0.4.0.10<\/span><span class=\"msysdl-history__date\">23. July 2026 11:19<\/span><\/div><div class=\"msysdl-history__log\"><div class=\"msmv-md msysdl-history__md\"><p class=\"MD_p\">Release 0.4.0.10 (from beta build 3.0.1 \/ GetIt). All changes below were driven by community feedback from the Delphi-PRAXiS beta threads \u2014 thank you to everyone who tested and reported.<\/p>\n<h2 id=\"msysdl-cl-33-1-fixed\" class=\"MD_h2\">1. Fixed<\/h2>\n<p class=\"MD_p\">Sources the formatter refused, or changed in ways it must not<\/p>\n<p class=\"MD_p\">Conditional compilation ({$IFDEF} \/ {$ELSE} \/ {$ENDIF}) \u2014 the big one<\/p>\n<p class=\"MD_p\">Sources whose conditional branches open or close blocks (begin, try, class, asm \u2026) could not be formatted at all: the formatter saw the code of every branch at once, counted openers and closers across branches and refused the whole file as \"unbalanced block structure\". The mirror case \u2014 a closer duplicated across branches \u2014 silently produced drifted indentation.<\/p>\n<p class=\"MD_p\">The structural bookkeeping is now branch-aware: at {$IF*} the formatter snapshots its state, walks every {$ELSE} \/ {$ELSEIF} branch from that same entry state and continues after {$ENDIF} \/ {$IFEND} with the first branch's exit state. Both directive families are supported, nested regions work, and column alignment no longer bridges across branch boundaries. The safety guarantee is unchanged: nothing is ever written when the source truly is unbalanced.<\/p>\n<p class=\"MD_p\">Known limits: include files ({$I}) that contribute block edges and directives sharing a line with code are by-design limits \u2014 now documented in the manual's \"Known limits\" section; some reflow-mode edge cases remain tracked.<\/p>\n<p class=\"MD_p\">Variant records refused every unit<\/p>\n<p class=\"MD_p\">Any unit containing a variant record (case Integer of inside a record) was refused with the same \"unbalanced\" message \u2014 without a single compiler directive involved. Fixed.<\/p>\n<p class=\"MD_p\">A closing end at the end of a statement line refused the whole file<\/p>\n<p class=\"MD_p\">A line that both finishes a statement and closes its block \u2014 B; end;, or the end); a compact one-line anonymous method leaves behind \u2014 made the formatter report the source as unbalanced and refuse it entirely, although the code is perfectly valid. The closer was consuming the pending continuation of an enclosing if \u2026 then \/ while \u2026 do instead of the block itself, so the block stayed open until the end of the file. A closer now always ends a block, wherever it sits on the line. This affected the default profile too, not just reflow \u2014 and in the cases that were not refused outright it silently pushed everything after that line further and further right.<\/p>\n<p class=\"MD_p\">asm blocks that end mid-line refused the file<\/p>\n<p class=\"MD_p\">The same class of defect as the previous fix, one code path over: after the end of an asm block the formatter stopped looking at the rest of that line, so a routine written as asm \u2026 end; end; lost its outer block and the file was refused. The remaining closers on the line are now counted.<\/p>\n<p class=\"MD_p\">Reflow could silently change what a string literal means<\/p>\n<p class=\"MD_p\">With line-break rules active, if C = '''' then Q; was reflowed so that the apostrophe literal ended up as the last token on its line. Delphi 12 reads a run of three or more apostrophes followed only by whitespace as the opening delimiter of a multiline string \u2014 so on the next run the formatter (correctly) read its own output as a multiline string and swallowed the following code. The result was a program with different meaning, and in some shapes one that no longer even parses. Such a literal is now never left at the end of a line. This also removes the last known case where formatting twice gave a different result than formatting once.<\/p>\n<p class=\"MD_p\">An unrelated .editorconfig could be applied to your file<\/p>\n<p class=\"MD_p\">The settings cascade walks from the file's own directory upwards \u2014 but one step past the drive root it produced the drive-relative form (C:), and asking Windows for C:.editorconfig means \".editorconfig in the current directory of that drive\". Files that had no .editorconfig of their own therefore silently picked up the one belonging to whatever directory the formatter happened to be started from \u2014 in the IDE that is not even a directory you chose. The cascade now stops at the drive root, so only the file's own path decides its settings.<\/p>\n<p class=\"MD_p\">Broken parentheses no longer produce file-wide indent drift<\/p>\n<p class=\"MD_p\">A source with a missing ) or ] used to pass the safety check silently \u2014 it only measured begin\/end blocks \u2014 and the continuation indent then drifted through the rest of the file. Unbalanced parentheses or brackets now share the same protection as unbalanced blocks: the IDE refuses with a precise message (\"unbalanced parentheses or brackets\") and leaves the buffer untouched. Such files cannot compile anyway; once the syntax is fixed, a single format run restores canonical indentation everywhere.<\/p>\n<p class=\"MD_p\">Layout<\/p>\n<p class=\"MD_p\">Alignment stopped working after branch-asymmetric conditionals<\/p>\n<p class=\"MD_p\">The aligner's nesting counters read every {$IFDEF} branch as if all of them were compiled at once \u2014 a begin in each branch counted twice, so behind such a conditional the aligner believed it was still inside executable code and quietly stopped aligning const\/var\/field blocks. The counters now follow the first branch only (the same first-branch-wins rule the conditional-fork indenter uses); behind the region the alignment is identical to a file containing just that branch.<\/p>\n<p class=\"MD_p\">Generics with conditional type arguments were spaced as comparisons<\/p>\n<p class=\"MD_p\">TList came out as TList ; \u2014 the generic matcher silently swallowed the directives and read both branches as one invalid token stream. The scan now follows the first branch and skips {$ELSE}\u2026{$ENDIF} whole (the same first-branch-wins rule the conditional-fork indenter uses), so the angle brackets stay generic-tight in every branch. Real comparisons next to directives keep their operator spacing.<\/p>\n<p class=\"MD_p\">Box-art comment headers were gutted<\/p>\n<p class=\"MD_p\">Under the default profile, decorative comment blocks such as the classic { Framework Name } unit headers lost their interior padding, and whitespace-only filler lines collapsed to {}. The comment-spacing option now does exactly what it says \u2014 it normalizes the single space inside the delimiters ({x} \u2194 { x }) \u2014 and treats everything beyond that (padding runs, frame lines like {******}, multi-line comments) as deliberate layout that survives byte-for-byte.<\/p>\n<p class=\"MD_p\">Nested if\/else indented misleadingly<\/p>\n<p class=\"MD_p\">In if A then if B then \u2026 else \u2026 chains the else branch was visually re-bound to the outer if, although Delphi binds it to the nearest one. The indentation now follows the language's actual binding \u2014 including through while \u2026 do in between, and without disturbing case-else handling.<\/p>\n<p class=\"MD_p\">Multi-line signatures and calls lost their continuation indent<\/p>\n<p class=\"MD_p\">Continuation lines of a multi-line parameter list or call were flattened to the same column as their head line. They now indent one continuation step past the line that opened the bracket; a closing-bracket line aligns with that opener line.<\/p>\n<p class=\"MD_p\">Statements after a mid-line finally \/ except were mis-indented<\/p>\n<p class=\"MD_p\">try \/ if A then \/ B; finally left the pending then continuation standing, so the statements of the finally part sat one step too deep.<\/p>\n<p class=\"MD_p\">The else of an unparenthesized if-expression looked like a second else<\/p>\n<p class=\"MD_p\">In if C then \/ X := if A \/ then 1 \/ else 2 \/ else \/ Y := 3; the first else belongs to the expression, the second to the statement \u2014 but the formatter pulled both onto the same column, so the code read as if one if had two else branches. The expression's else now stays at the expression's level. (The branch lines themselves keep their layout: an unparenthesized continuation is never indented an extra step \u2014 the same as X := A + \/ B;.)<\/p>\n<p class=\"MD_p\">Generic constraints were spaced as comparisons<\/p>\n<p class=\"MD_p\">TList came out as TList . Constraint lists (class, record, constructor, interface types, multiple parameter groups) are now recognized as generics.<\/p>\n<p class=\"MD_p\">Generics in parameter defaults were torn apart<\/p>\n<p class=\"MD_p\">A default value glued to a generic parameter type \u2014 Symbols: TArray= [] (no space before the =) \u2014 made the scanner read &gt;= as a single greater-or-equal operator. The generic then failed to be recognized and came out spaced as a comparison: TArray = []. Both the tight original and the previously damaged form now heal to TArray = []; a generic &amp;lt; also glues back to its type name. Real comparisons like a = c are untouched.<\/p>\n<p class=\"MD_p\">Delphi 13 if-expressions were staircased<\/p>\n<p class=\"MD_p\">A multi-line if-expression in parentheses \u2014 (if cond then &amp;#039;-&amp;#039; else &amp;#039;&amp;#039;) spread over lines \u2014 had its branch lines indented like a statement-if, one extra level per then\/else. Combined with the bracket-indent option this produced a staircase drifting right with every branch. Inside parentheses an if is always an expression (only an anonymous method&amp;#039;s begin re-enters statement territory \u2014 that case is recognized and unchanged), so the branch lines now get plain continuation indent. Statement-if formatting, dangling- else binding and case-else handling are untouched.<\/p>\n<p class=\"MD_p\">&amp;quot;else if&amp;quot; line breaks left the else hanging<\/p>\n<p class=\"MD_p\">With line-break rules active, if A then B else if C then D reflowed to then B else \u23ce if C. A statement-level else now always starts its own line; the existing option keeps controlling the gap between else and if (both settings of it now produce clean shapes). Delphi 13 if-expressions (x := if a then b else c) are never broken apart.<\/p>\n<p class=\"MD_p\">Line-break rules tore if-expressions apart<\/p>\n<p class=\"MD_p\">With reflow enabled, a Delphi 13 if-expression was laid out like a statement: S := (if A then &amp;#039;yes&amp;#039; else &amp;#039;no&amp;#039;); came back split across four lines. The first round of protection covered only the unparenthesized form and only two of the four rules involved, so both the parenthesized form and \u2014 with the then and simple instruction rules armed \u2014 even the bare one were still broken up. Inside parentheses an if is always an expression (an anonymous method&amp;#039;s begin re-enters statement territory), and those rules now leave both forms alone. Statement ifs keep breaking exactly as configured.<\/p>\n<p class=\"MD_p\">Command line<\/p>\n<p class=\"MD_p\">One bad file no longer aborts the whole run<\/p>\n<p class=\"MD_p\">A source that cannot be decoded (a stray byte in a file claiming UTF-8) made Formatter.exe stop right there \u2014 silently truncating a recursive sweep, even under --check where nothing is written at all. Such a file is now reported, counted as skipped and left untouched; the run continues and the exit code still reports the error.<\/p>\n<h2 id=\"msysdl-cl-33-2-new\" class=\"MD_h2\">2. New<\/h2>\n<p class=\"MD_p\">Blank lines around initialization\/finalization, and before the final end.<\/p>\n<p class=\"MD_p\">Two new structure separators and a new indent option close the gap the section separators left: delphi<em class=\"MD_em\">blank<\/em>lines<em class=\"MD_em\">around<\/em>initialization guarantees blank lines before and after the initialization\/ finalization keywords, delphi<em class=\"MD_em\">blank<\/em>lines<em class=\"MD_em\">before<\/em>final_end puts them before the closing end., and Indent initialization\/finalization contents indents the sections&amp;#039; statements one level like a begin..end block. All three are off by default \u2014 existing output stays byte-identical.<\/p>\n<p class=\"MD_p\">Unusable options are now hidden<\/p>\n<p class=\"MD_p\">When a master option turns a group of settings off, those settings used to stay visible \u2014 at best with a grayed group title, while the controls below still looked active (&amp;quot;It&amp;#039;s disturbing&amp;quot;). Dependent options are now hidden outright: with &amp;quot;Keep user line breaks&amp;quot; on (the default), the line-break rules, the whole Reflow page and the blank-line separators disappear (an explanatory note stays behind); the alignment tuning numbers hide while no alignment case is active; coupled or inert switches (colons-before-types coupling, case options without block indent, bracket indent under reflow) vanish with their masters. Toggling the master brings everything back \u2014 live, across pages, without reopening the dialog.<\/p>\n<p class=\"MD_p\">Readable, complete option texts<\/p>\n<p class=\"MD_p\">Longer labels were cut off \u2014 most visibly the note under Blank Lines and the &amp;quot;colons before type names&amp;quot; switch under Alignment, and more often in German, where the translations are longer than the English originals. Every page was measured against both languages: notes have room for their full text, long switch captions wrap instead of being clipped, and the drop-downs sit far enough right that no label can run into them. The explanatory notes are now laid out in paragraphs instead of one dense block.<\/p>\n<p class=\"MD_p\">The option previews now show real cases<\/p>\n<p class=\"MD_p\">The live before\/after preview on each options page demonstrates the constellations this release fixed: conditional branches carrying a try, case with else, box-art comment headers, generic constraints and defaults, multi-line call continuations, dangling else binding, {$REGION} blank lines and alignment groups broken by a directive \u2014 so every page shows its own options working on real code.<\/p>\n<p class=\"MD_p\">The line-break master is now a regular .editorconfig key<\/p>\n<p class=\"MD_p\">&amp;quot;Keep user line breaks&amp;quot; can be set from a project&amp;#039;s .editorconfig (delphi<em class=\"MD_em\">keep<\/em>user_linebreaks) like every other option, so a team can pin its line-break policy in the repository and an exported profile round-trips completely. This deliberately reverses the earlier safety stance that a repository file must never enable reflow.<\/p>\n<p class=\"MD_p\">Export writes what you see<\/p>\n<p class=\"MD_p\">Both export buttons (.config and .editorconfig) now write the values currently set in the options dialog, including pages you have edited but not yet applied \u2014 previously they silently wrote the last saved state, and the note explaining that is gone along with the behaviour.<\/p>\n<p class=\"MD_p\">The installer now serves both IDEs<\/p>\n<p class=\"MD_p\">The setup installs the 32-bit and the 64-bit design package side by side and registers each with its IDE (Known Packages \/ Known Packages x64) \u2014 Ctrl+D works in whichever RAD Studio 13 you launch. Both packages always carry the same version number; the installer build refuses to package mismatched builds.<\/p>\n<p class=\"MD_p\">Option: placement of the case-else line<\/p>\n<p class=\"MD_p\">A new switch &amp;quot;Indent else line&amp;quot; (delphi<em class=\"MD_em\">indent<\/em>case_else) controls where the else of a case statement sits: at the level of the alternative labels (default, unchanged behaviour) or at the case keyword \u2014 the classic RTL style. The statements below it remain governed by the existing case options.<\/p>\n<h2 id=\"msysdl-cl-33-3-clarified-and-pinned\" class=\"MD_h2\">3. Clarified and pinned<\/h2>\n<p class=\"MD_p\">Blank lines around {$REGION}: both halves of the request are covered by existing options \u2014 set Max. consecutive blank lines to 2 to preserve a two-blank region spacing, and Blank lines around compiler directives (reflow tier) to insert them. Documented in the manual and locked in by tests. &amp;quot;Ensure final newline&amp;quot; and &amp;quot;Enable formatting&amp;quot;: both reported against beta build 3.0.1; the current code base behaves correctly (the disable switch is honoured end to end, including the .editorconfig cascade, and the final-newline option is exact in both directions). Both behaviours are now locked in by tests. The 3.0.1 symptoms came from that build&amp;#039;s Revive-based IDE integration, which the native RAD Studio 13.2 formatter interface has since replaced. Options pages opening slowly: verified not to be the plugin \u2014 even empty pages build up slowly; the cost sits in RAD Studio&amp;#039;s own Tools\/Options page embedding and would affect any add-in equally. The limits of conditional handling are documented<\/p>\n<p class=\"MD_p\">Two constellations the conditional-fork model cannot cover by principle now have their own &amp;quot;Known limits&amp;quot; manual section (German and English): include files that contribute block structure (the formatter refuses honestly or, for an included begin, may indent differently after the spot - never damaging anything), and directive regions starting or ending next to code on the same line (left untouched). Each comes with a minimal example, the observable behavior and an .editorconfig opt-out recipe.<\/p>\n<h2 id=\"msysdl-cl-33-4-by-design\" class=\"MD_h2\">4. By design<\/h2>\n<p class=\"MD_p\">The options tree stays under the MSys node: requested twice from the community (&amp;quot;Third Party&amp;quot; placement); declined deliberately \u2014 the MSys node is the shared home for current and future MSys settings. Ctrl+D stays Ctrl+D: the format shortcut is not configurable \u2014 Ctrl+D has been the Delphi formatter&amp;#039;s key since the built-in one, and on RAD Studio 13.2 the IDE owns the command anyway. Plugins that also claim Ctrl+D (e.g. GExperts) offer configurable shortcuts on their side.<\/p>\n<h2 id=\"msysdl-cl-33-5-under-the-hood\" class=\"MD_h2\">5. Under the hood<\/h2>\n<p class=\"MD_p\">The regression suite grew from 744 to 970 checks; every repository fixture is now also verified to format balanced, and formatting twice is now pinned for reflow profiles too, not just the default one. New shared conditional-directive classifier used by the re-indenter and the aligner; community-provided reproduction sources joined the fixture set. Several of the defects above were found by the fix for another one: the mid-line closer and the multiline-string cases came out of reviewing the if-expression reflow, and the .editorconfig cascade bug out of measuring the multiline-string fix.<\/p>\n<\/div><\/div><\/li><\/ul><\/div><\/div><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-abce72c e-con-full e-flex e-con e-child\" data-id=\"abce72c\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-b75e539 elementor-widget elementor-widget-msysdl_info\" data-id=\"b75e539\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--version\"><span class=\"msysdl-info__label\">Version: <\/span><span class=\"msysdl-info__value\">1.4.30.176<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-f86a2af e-con-full e-flex e-con e-child\" data-id=\"f86a2af\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-1293778 elementor-widget elementor-widget-msysdl_info\" data-id=\"1293778\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_info.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-info msysdl-info--release_date\"><span class=\"msysdl-info__label\">Release: <\/span><span class=\"msysdl-info__value\">26. October 2026 10:31<\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t<div class=\"elementor-element elementor-element-405e519 e-con-full e-flex e-con e-child\" data-id=\"405e519\" data-element_type=\"container\" data-e-type=\"container\" data-settings=\"{&quot;background_background&quot;:&quot;classic&quot;,&quot;ekit_has_onepagescroll_dot&quot;:&quot;yes&quot;}\">\n\t\t\t\t<div class=\"elementor-element elementor-element-fcdb43a elementor-widget elementor-widget-msysdl_button\" data-id=\"fcdb43a\" data-element_type=\"widget\" data-e-type=\"widget\" data-settings=\"{&quot;ekit_we_effect_on&quot;:&quot;none&quot;}\" data-widget_type=\"msysdl_button.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<span class=\"msysdl-dl\"><a class=\"msysdl-dl__btn\" href=\"https:\/\/maenken.systems\/msysdl\/15308\/latest\/\" rel=\"nofollow\">Download<\/a><span class=\"msysdl-dl__meta\"><\/span><\/span>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/main>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Maenken Systems Components Download Center MSys Component Delphi Tools Plug-In&#039;s Addon&#039;s Download Center MSys Download Center MSys Tools zum Download In this section, you will find software components provided by us available for download. Download the applications, extensions and tools you need quickly and easily, and benefit from our high-performance solutions. Maenken System powered Plug-Ins [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_qcld_wpbot_writer_seo_pending":"","footnotes":""},"class_list":["post-13571","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/pages\/13571","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/comments?post=13571"}],"version-history":[{"count":10,"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/pages\/13571\/revisions"}],"predecessor-version":[{"id":15843,"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/pages\/13571\/revisions\/15843"}],"wp:attachment":[{"href":"https:\/\/maenken.systems\/en\/wp-json\/wp\/v2\/media?parent=13571"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}