Lajos Juhász

Mobile platforms are changing very fast. Sometimes it is difficult for Embarcadero to provde a solution in a reasonable time frame when the new requirements are released to be able to continue to compile for new versions. Unfortunately nowdays Delphi support too many platforms. They are playing catch up games against other products. Delphi is by rule almost always way behind.

It is in lines property,

(In theory) you can use the TXMLDocument if you select a cross platform DOM vendor. (https://docwiki.embarcadero.com/RADStudio/Alexandria/en/Using_the_Document_Object_Model)

At the second row is not the end of the dataset, eof is going to be true when you call next on the last row. You can check recno or a value of the group field.

procedure TForm1.FormCreate(Sender: TObject); begin Var Boy: string; Girl: string; Couple: string; end; For those who doesn't have a modern compiler. Of course inline var is not a block thus it will produce errors: [dcc32 Error] Unit1.pas(29): E2003 Undeclared identifier: 'Girl' [dcc32 Error] Unit1.pas(29): E2029 '(' expected but ';' found [dcc32 Error] Unit1.pas(30): E2003 Undeclared identifier: 'Couple' [dcc32 Fatal Error] Project1.dpr(5): F2063 Could not compile used unit 'Unit1.pas' Failed

You have to select a checkbox during the install process (Technology - Teechart standard). Unfortunately Embarcadero has licenced the product without the source code. I did not noticed problems with the Teechart.

I can shrink it like this:

Set the transparent property to false: var num: TStaticText; begin num:=TStaticText.create(self); num.parent:=self; // rect:=wc.boundsrect; // num.caption:=' '+inttostr(lastnumnum)+' '; num.caption:=' Test'; num.font.name:='Arial'; num.font.color:=clred; num.Transparent:=false; end; Edit. You have to use StyleElement only if your application is using VCL Styles.

This was written by Copilot. I can not test the code as I do not have the iOS units installed on my system. To change the screen brightness on iOS using Delphi, you can use the UIScreen class from the iOS API. Here's a basic example of how you can achieve this: 1. Import the necessary iOS units: uses iOSapi.UIKit, iOSapi.Foundation; 1. Set the screen brightness: procedure SetScreenBrightness(Brightness: CGFloat); begin UIScreen.mainScreen.setBrightness(Brightness); end; 1. Call the procedure with the desired brightness level: begin SetScreenBrightness(0.5); // Set brightness to 50% end; In this example, UIScreen.mainScreen.setBrightness is used to set the brightness level. The brightness value should be between 0.0 (minimum brightness) and 1.0 (maximum brightness)https://www.reddit.com/r/iOSProgramming/comments/whtu5q/is_there_a_way_to_control_screen_brightness/https://forums.developer.apple.com/forums/thread/717234. Would you like more details on integrating this into a full application?

OP is on older version of Delphi 10.4 your example is Delphi 12.

Embarcadero could have that: https://docwiki.embarcadero.com/Libraries/Athens/en/System RTLVersion RTLVersion: Comp = 36; RTLVersion121 RTLVersion121: Boolean = True; RTLVersion122 RTLVersion122: Boolean = True; RTLVersion123 RTLVersion123: Boolean = True;

program Project1; {$APPTYPE CONSOLE} {$R *.res} uses System.Classes, Winapi.Windows; type TMyRecord = class data: Integer; class procedure Queue(const AThread: TThread; AMethod: TThreadProcedure); end; class procedure TMyRecord.Queue(const AThread: TThread; AMethod: TThreadProcedure); begin OutputDebugString(PChar('In TMyRecord.Queue')) end; begin TThread.Queue(nil, procedure begin OutputDebugString(PChar('Hello !')) end); TMyRecord.Queue(nil, procedure begin OutputDebugString(PChar('Hello !')) end); end. It should be TThreadProcedure not method.

FireDAC is very strict. When I have moved projects from BDE and DBX that involved a lot of changes.

As a result it can not be assigned to an event.

You can set the datatype before prepare qryWork.Params[0].DataType:=ft...... the data type of field1.

this is fmx while the question is about VCL.

You can change it on a new form and leave parentfont to true on the components you drop. You should accept the new default font. On newer monitors event font size 9 is a bit hard to read.

No, a file is a file a folder is a folder two different things. In case of a folder you should use the TPath (record). attributes:=TPath.GetAttributes(PathName)

You have some hidden unicode character there. It can happen if you copy paste from the internet. var FileName : String; attributes: TFileAttributes; begin FileName := 'Test'; attributes:= TFile.GetAttributes(FileName); Include(attributes, TFileAttribute.faHidden); TFile.SetAttributes(FileName, attributes); end; This compiles.

According to the documentation the object property of the stringlist is used to handle the shortcuts not the text version: TCustomShortCutList is a descendant of TStringList, which manages a collection of strings. As such, TCustomShortCutList adds, deletes, and searches for shortcuts using their text representation. TCustomShortCutList stores shortcuts that correspond to a text representations as values of the Objects property for these strings. Do not change values of the Objects property, or the shortcut list will not operate correctly.

In the official documentation there is no mention that it would be a language specific shortcut: Description Stores shortcuts (in addition to ShortCut) for triggering the action. Actions can execute in response to multiple shortcut key combinations. SecondaryShortCuts lists all the shortcut key combinations (other than the one specified by the ShortCut property) that can trigger the action. This lets you provide additional, secondary shortcuts. When the user types one of the key combinations listed in SecondaryShortCuts, the action's Execute method is called.

In that case I am the unlucky one. Have had no issues using Delphi 12.2 update 1 on Windows 11.

I would recommend to use only that threading library not the others you will save a lot of time. A more serious answer is that you should give us more details. Anyo of those can create a thread which library to choose really depends on the requirements.

I believed it is a different aproach. They give to us something that compiles and is working. Then based on user review and bug reports they are accepting suggestions how to make it work. If everything else fail they buy some source code to make things working again.

I have no problem to compile it: const // The highlight colors here are defined twice so the compiler doesn't complain. YELLOW = $00BBFF; BLUE = $F0CF89; HIGHLIGHT_COLORS: array[0..1] of TColor = (YELLOW, BLUE); You can also compile: const // The highlight colors here are defined twice so the compiler doesn't complain. YELLOW = TColor($00BBFF); BLUE = TColor($F0CF89); HIGHLIGHT_COLORS: array[0..1] of TColor = (YELLOW, BLUE);