Stefan Diestelmann
Active subscription
-
Joined
-
Last visited
Everything posted by Stefan Diestelmann
-
Sample attached FormHideCloseDemo_R518.zip
-
Hello Yaroslav, thank you, that was it. After reinstalling FGX Native 1.20.1.0 with the iOS targets selected, the library path for iOS Simulator ARM64 now contains $(FGX)\Libs\370\iOSSimARM64\Release, and both a sample and our app build and link for iOSSimARM64 again (error F1027 for FGX.Consts is gone). One observation that may help other users: the installed files were byte-identical to the previous installation — only the IDE library path for the simulator platform was missing. It seems the installer only writes that path when the iOS targets are checked, so a hint in the installer or in the release notes could save others some time. Best regards, Stefan
-
Since 1.20.0.0 Show/Close animate by themselves. Existing code that hides the form on its own and calls Close afterwards now crashes on iOS: FAnimation.OnFinishCallback := procedure begin Camera.Active := False; Hide; // form is already hidden here end; procedure TFormScanner.btnBackTap(Sender: TObject); begin FAnimation.Stop; // Stop calls Finish -> OnFinishCallback -> Hide Close; // animated close on an already hidden form end; Result: Exception EAccessViolation in module libobjcMsgSend.dylib [WARNING] [Animation] You are destroying an animation that is marked for autodeletion! (TfgiOSAnimationFormPadding) Runtime error 217 Show(TfgFormPresentationStyle.None) avoids it, because the form then closes without animation as well. It might be worth guarding Close/Hide against being called on a form that is already hidden.
-
Environment FGX Native 1.20.1.0 RAD Studio 13 (BDS 37.0), iOSDevice64, Debug iPhone 17 Pro Max, built against iPhoneOS27.0.sdk Android: same code works fine Problem If a form containing a TfgCameraPreview is created but not shown right away, the preview stays black forever on iOS — even after the form is shown later and the camera has started. The camera itself works perfectly in this state: the session starts, OnStateChanged reports Started, and an attached TfgBarcodeScanner keeps detecting barcodes. Only the preview shows nothing. How to reproduce // A: preview stays black constructor TScannerHolder.Create; begin inherited; FForm := TFormScanner.Create(nil); // created here, shown later end; procedure TScannerHolder.Scan; begin FForm.Show; // black preview, camera is running end; // B: works procedure TScannerHolder.Scan; begin if FForm = nil then FForm := TFormScanner.Create(nil); // created right before showing FForm.Show; end; The form itself is unchanged between A and B — only the moment of creation differs. What makes this hard to diagnose Everything you would normally check looks correct while the preview is black: IsBufferAvailable returns True, so the surface exists and the preview is attached to the camera CalculatedFrameRect is correct (e.g. 537.75 x 956 for a 440 pt wide control, the usual AspectFill overhang) size 440 x 956, Visible = True, form visible, no error overlay all events run on the main thread, only one form instance exists no exception is raised anywhere I verified it is none of the usual suspects by taking a bare TfgForm with nothing but TfgCamera + TfgCameraPreview (which works) and adding the properties of the failing form one at a time. All of these kept the picture alive: a custom base form class, a TfgBarcodeScanner attached to the same camera, nesting the preview inside a TfgLayout with a background, an infinitely repeating scale animation, Enabled = False on the preview, calling RequestPermission in the constructor, registering a TfgNavigationBar as Toolbar plus SystemStatusBar.Visibility = Invisible, two full-size overlay layouts, TfgArc / TfgActivityIndicator / TfgLabel / icon buttons, and the exact same call path. The picture only disappeared when the form was created in advance instead of immediately before Show. What I noticed in the log: when the form is created in advance, OnResized of the preview already fires at creation time — so the preview is laid out (and its surface created) while the form has never been on screen. That surface seems to stay unusable. Workaround Create the form lazily, right before showing it. Question Is this expected? If a preview may not be laid out before its form is shown, it would help a lot if FGX either re-created the surface on the first Show, or logged a warning — right now nothing indicates that anything is wrong.
-
-
Title[Build] Precompiled iOSSimARM64 DCUs are rejected by the compiler (F1027) on RAD Studio 13.2 BodySummary With FGX Native 1.20.1.0 on RAD Studio 13.2, no project can be compiled for the iOS Simulator (iOSSimARM64). The compiler rejects every precompiled FGX DCU shipped in Libs\370\iOSSimARM64\ with F1027 Unit not found. The same installation compiles fine for Android64 and iOSDevice64. Your own samples fail as well, so this is not specific to our application. Environment FGX Native 1.20.1.0 (installed with the designer version for RAD Studio 13.2) RAD Studio 13.2 — bds.exe / dcciossimarm64.exe file version 37.0.60952.8797, dated 2026-09-09 Host Windows 11 Mac Xcode 27.0 (27A266a), PAServer 37.0_13.2, SDK iPhoneSimulator27.0.sdk Library path $(FGX)\Libs\$(FGXCOMPILER)\$(PLATFORM)\... with FGX = c:\projekte\delphi_sp\FGX Native, FGXCOMPILER = 370 Symptom Building any FGX project for iOSSimARM64 (msbuild or IDE library path, Debug or Release): BSYSMobileApp.dpr(91): error F1027: Unit not found: 'FGX.Application' or binary equivalent (.dcu/.o) Your own sample Samples\ActivityIndicator - Tint fails with exactly the same error: ActivityIndicatorDemo.dpr(7): error F1027: Unit not found: 'FGX.Application' or binary equivalent (.dcu/.o) Minimal reproduction t.dpr: program t; uses FGX.Consts; begin end. dcciossimarm64.exe --no-config ^ -U"c:\projekte\delphi_sp\FGX Native\Libs\370\iOSSimARM64\Debug;C:\Program Files (x86)\Embarcadero\Studio\37.0\lib\iOSSimARM64\debug" ^ -NSSystem t.dpr t.dpr(1) Fatal: F1027 Unit not found: 'FGX.Consts' or binary equivalent (.dcu/.o) FGX.Consts.dcu (758 bytes) and FGX.Consts.o (3868 bytes) are both present in that directory. The same happens for every FGX unit we tried (FGX.Types, FGX.Controls, FGX.Application, …), for both Debug and Release, and with or without the .o file present. What we verified (to rule out the usual causes) The search path is fine. A DCU we compiled ourselves, placed in the same directory as the rejected FGX.Consts.dcu, is found and loaded by the very same compiler invocation. The RTL for that platform is fine. uses System.SysUtils against lib\iOSSimARM64\debug compiles and only stops at the (locally unavailable) Mac linker. Other platforms work. The FGX DCUs for Android64 (dccaarm64) and iOSDevice64 (dcciosarm64) from the same installation load correctly — compilation succeeds and the run only stops in the linker. The source is fine — only the shipped binary is not. Compiling Sources\FGX.Consts.pas ourselves with this exact compiler produces a DCU that loads without any problem. Interesting detail: our .o has exactly the same size as the shipped one (3868 bytes), while our .dcu is 799 bytes versus the shipped 758 bytes. So the code is identical; the DCU container is not. Not a regression of 1.20.1.0 alone. The iOSSimARM64 DCUs of 1.20.0.0 and 1.19.6.0 (we keep the library in git) are rejected in the same way by this 13.2 compiler. The DCU header looks correct. Platform magic and compiler tag are identical to a DCU produced by this compiler: our own DCU: 4D 88 00 25 F3 00 00 00 ... + FE 27 FE EF 07 96 01 shipped FGX: 4D 88 00 25 F6 02 00 00 ... + FE 27 FE EF 07 96 01 RTL System.dcu (iOSSimARM64): 4D 88 00 25 ... + FE 27 FE EF 07 96 01 Our interpretation Since only the iOS Simulator platform is affected, while Android and iOS device binaries from the same package are fine, it looks like the iOSSimARM64 libraries of 1.20.1.0 were not built against the same RAD Studio 13.2 / iOS 27 simulator RTL as the other platforms — or the simulator platform was not rebuilt for the 13.2 package at all. Question Could you please check the Libs\370\iOSSimARM64\Debug and ...\Release binaries of the 13.2 package? At the moment we cannot build or test anything on the iOS Simulator. Happy to provide any further output (full compiler command line, hex dumps, the failing sample).
-
-
-
Access violation при открытии формы в дизайнере в RAD Studio 13.2 FGX Native: 1.20.0.0 IDE: RAD Studio 13.2 (BDS 37.0), bds.exe 37.0.60952.8797 При установке выбран вариант: Designer (13.1+) При открытии любого .xfm в дизайнере IDE выдаёт ошибку: Error creating form in Form.Main.xfm: Access violation at address FB7A59E9 in module 'bds.exe' (Offset FB7A59E9). Execution of address FB7A59E9. (в немецкой локализации: «Fehler beim Erzeugen des Formulars in Form.Main.xfm: Zugriffsverletzung bei Adresse FB7A59E9 in Modul 'bds.exe' …») Воспроизводится на любом проекте, включая штатные примеры, например Samples\ActivityIndicator - Tint\Form.Main.xfm. Что удалось выяснить: - Пакеты загружаются без ошибок: все импорты FGXNative.Designer.370.bpl присутствуют в пакетах 13.2 (проверено по таблицам импорта/экспорта PE). Ошибка возникает только при первом виртуальном вызове. - Адрес FB7A59E9 лежит далеко за пределами адресного пространства 32-битного bds.exe, и сообщение говорит «Execution of address», то есть вызов по некорректному указателю (смещённая VMT). Похоже на ту же несовместимость design-time пакетов, что была с 12.3 (1.18.11.0) и 13.1 (1.19.6.0). - Компиляция и сборка не затронуты: пример под Android64 собирается через msbuild успешно (exit code 0). Проблема только в design-time. - FGXNative.Designer.370.bpl: link timestamp 2026-09-08 21:58 UTC, версия файла 1.20.0.0. - В инсталляторе 1.20.0.0 варианта дизайнера для 13.2 нет — только 13.0 и 13.1+. Вопрос: нужна ли отдельная сборка дизайнера для 13.2?
-
-
Hello, I tried using colored SVG files, but unfortunately only a black image is displayed. What do I need to keep in mind when creating SVG files, for example with Adobe Illustrator? Are there any specific settings or requirements I should follow to ensure that the colors are displayed correctly?
-
TYVM i can open the Forms with this new Version, i ll test it and give report if everything is fine now
-
There is no option for 13.1 only 12.3
-
For Test reason i disabled all my other vcl libs, only fgx left, but same exception comes
-
Hello Yaroslav, i just created a new FGX App ann dooble clicked the main Form. Exception comes. Any Idea what i can test ?
-
Hi just for your information, i downgraded to 19.4.0 (to test it) and get same error opening Form Editors (May be it depends on Rad Studio 13.1 ?)
-
The Exceptiíon comes from the ide not the program, i can open any app in Rad Studio 13.1 if i open or create a TFgForm the Exception comes. may be from form designer.
-
Under Rad Studio 13.1 with 1.19.5.0 i get this Exception opening a Form (derived from TfgForm: This occurs also opening a sample and then opening the main form
-
Hi we had today the problem, that color resources where not found as we set in in code with constants from Assets.Consts.pas The Problem is that ypu use TfgAsset.FolderSeparator instead of TfgAsset.ThemeSeparator so the genrated String ist wrong class function TfgAssetsConstants.TfgThemeColors.BACKGROUND: TfgAssetName; begin Result := Application.ThemeSettings.ThemeName + TfgAsset.FolderSeparator + 'Background'; end;
-
Yes, it is solved - Thank you
-
I Found the Error: camBarcodeScanner.MaxFrameSize.Width := ModuleInfoManager.EinstellungenManager.ReadInteger(cBSYSMobilePhotoMaxBreite); camBarcodeScanner.MaxFrameSize.Height := ModuleInfoManager.EinstellungenManager.ReadInteger(cBSYSMobilePhotoMaxHoehe); Setting this Values was the Problem.
-
In our Apps we take lots of Photos and save them. I testet Android, iOS i will add later We get this Errors: Call Stack: Latest Visible line of Code
-
Buildiung app for android store we get error message keystore password not found but we put in Projekt Options as usual, Is this a FGX Issue ? For FMX we can work as usual ?
-
I discoverd atm 2 things which we can call bugs: At Compile Start for Android you copy System.Permissions.Android from wrong path libs300 the Folder is called libs370 as workaround i made a link libs370 to libs300 in Assets.Consts: class var &File instead of files
-
