Leaderboard

Anything that crashes the ICS web server is something that should be fixed, if you are sure GET with body is fatal, I'll put it on my list to test and try and fix. I get thousands of hacking attempts on my public server daily, even have a dynamic blacklist to block repeats accesses, currently 4,600 IPs blocked for the last thee days. Angus

Well it's a subject I was working on 07/2019 but reworking those days for a tutorial (and future book perhaps) The trick is first to get the style used var sb: TFMXObject; begin if assigned(Scene) then begin if not Assigned(Scene.StyleBook) then sb := TStyleManager.ActiveStyleForScene(Scene) else sb := Scene.StyleBook.Style; then once got you can search the needed properties if assigned(sb) then begin // text color aFMXObj := TStyleContainer(aFMXObj).FindStyleResource('labelstyle'); if Assigned(aFMXObj) then aFMXObj := TLayout(aFMXObj).FindStyleResource('Text'); if Assigned(aFMXObj) then Memo1.lines.Add(AlphaColorToString(TText(aFMXObj).TextSettings.FontColor)); end; but for button color, it's a bit harder, you have 2 cases : Background is a TRectangle; Background is StyleObject (selection in a bitmap). Use the same scheme as exposed for text color (finding 'buttonstyle') and then 'background' if background object is a TRectangle then you can access fill.color property (take care type could be also a gradient ...) else (a FMXObject) I made a try here (by the way you can get button's text color(s) also) Sorry if my links are for French readers. P.S. read a some .style files to understand the principles

Verdict: Can confirm that if I remove the ICSPing.dcr file from the Common project file and the -k from the debug compilation additional parameters, it compiles fine in both debug and release modes, 32-bit. Will try FMX next. Then, will remove everything one more time and try the single-installation method. Edit to add: FMX installed correctly out of the box.

Okay! I've figured out why this was happening. There are a few units for which *only* the .dcr files are included in the icsCommonCBNewRun.cbproj file. Missing from the project file: OverbyteICSLogger.pas OverbyteICSMimeDec.pas OverbyteICSMimeUtils.pas OverbyteICSPing.pas OverbyteICSTimeList.pas In the case if OverbyteICSPing, the .dcr appears in both Common and VCL, but the .pas only appears in VCL. I don't know if it's meant to be in Common or VCL, but it probably shouldn't appear in both. For testing, I'm going to take it out of the VCL, but please let me know. I made these changes, and it compiled and installed in the 32-bit compiler. Will test with my application, but if it works it seems like we might be able to start using this new IDE! Let me know if you need further testing, after making these changes, Angus. Maybe we can get this on GetIt after all. Cheers, Ian

Creating at run-time is pretty straightforward. You need Owner and Parent, and sometimes setting Align property. You can use any FMX control as those - or at least I have been able to use them without a problem. FFrame := TMyFrameClass.Create(AParent); FFrame.Parent := AParent; FFrame.Align := ... And that is it.