Leaderboard

I have just built an installer for GExperts 1.3.24 Beta1 for Delphi 12. Note the word “Beta” in the release name! We are one step up from Alpha, there are still many bugs, but overall it seems to be stable. Most of the bugs manifest themselves as display glitches on high DPI monitors. Continue reading in the blog post

Reporting error dialogs from thread pool threads sounds terrible. Stop doing it at all and then you don't need to think that one message box function is better than any other.

In forward declaration of a class, compiler immediatelly knows the size of that type. For records, their size would be unknown in forward declaration.

I think you'll have to wait a bit; It's only just entered puberty. 13 years old....

Which has changed in the last few weeks, and is now dependent on AppTrackingTransparency. See the updated readme.

If your project requires AppTrackingTransparency, you also need to add that framework to the SDK, as per these instructions.

This is indeed very instable. One would need to extend the current internals significantly to make this work. Nevertheless one can achieve some results by setting AcceptExpressions to True and override these two methods: type TNumberBox = class(Vcl.NumberBox.TNumberBox) protected function GetValidCharSet(AAcceptExpressions: Boolean): TSysCharSet; override; function IsNumericText(const AText: string): Boolean; overload; override; end; function TNumberBox.GetValidCharSet(AAcceptExpressions: Boolean): TSysCharSet; begin Result := inherited GetValidCharSet(AAcceptExpressions); if Mode = nbmFloat then Result := Result + ['e', 'E', '+', '-']; end; function TNumberBox.IsNumericText(const AText: string): Boolean; begin Result := inherited; if AText.LastIndexOfAny(['e', 'E']) = AText.Length - 1 then Result := False; end;

There is source in the Visualizers folder: Embarcadero\Studio\23.0\source\Visualizers It doesn't include the .dpk though.

There is a reason why that is not supported: type TRecA = record; TRecB = record FieldA: TRecA; end; TRecA = record FieldB: TRecB; end;

Hardly, because you've now ruined your production program.

Example code for how to do it: uses Macapi.AppKit, Macapi.Helpers; procedure TForm1.Button1Click(Sender: TObject); var LMenu: NSMenu; LIndex: Integer; begin LMenu := TNSApplication.Wrap(TNSApplication.OCClass.sharedApplication).mainMenu; LIndex := LMenu.indexOfItemWithTitle(StrToNSStr('Window')); if LIndex > -1 then LMenu.itemAtIndex(LIndex).setHidden(True); end;

You did not show the code that receives the file path from the file chooser and puts it into the TEdit, or show what the file path actually looks like. But ACTION_GET_CONTENT is documented as returning a "content:" uri, which requires you to use the ContentResolver class to access the file data. But TIdMultipartFormDataStream.AddFile() uses TFileStream, which wants direct access to the file, which will not work with a "content:" uri on modern Android versions. So you will likely have to either: access the file yourself via Android APIs and read its byte data into a TMemoryStream or TByteStream, or create a custom TStream that wraps an Android InputStream from the ContentResolver.openInputStream() method And then use TIdMultipartFormDataStream.AddFormField() instead of TIdMultipartFormDataStream.AddFile() to send whichever TStream you end up using. Alternatively, you can use ContentResolver to extract the underlying "file:" uri from a "content:" uri, and then you should be able to open the file using a normal TFileStream (provided you have permissions to the file). Also, when using ACTION_GET_CONTENT, the ACTION_GET_CONTENT documentation says to wrap your Intent with Intent.createChooser(), and also include CATEGORY_OPENABLE and FLAG_GRANT_READ_URI_PERMISSION on your Intent.

My top 3 'wish' list items: - MCCGA. Make ctrl-click great again (and actually work.) - A code formatter that handles all language features. AND don't add another language feature that isn't accompanied with an update to the code formatter to support it. - Refactoring tools that handles all language features. AND don't add another language feature that isn't accompanied with an update to the refactoring tools to support it. You have to be able to navigate code and I have wasted too many hours of life with a ctrl-click that does nothing. You shouldn't have to spend precious brain cycles on code formatting tasks. If refactoring doesn't work - the IDE doesn't work. Others: - Much more focus on debuggers - Quality, quality, quality - Keep current with platform support

You should not have to manually create missing folders. Even if you did, the files that the compiler needs would not be there. If there was a missing PrivateFrameworks folder, you may have to re-import the SDK using these steps: In the folder C:\Users\(username)\Documents\Embarcadero\Studio\SDKs, where (username) is the logged in user name, delete the relevant iPhoneOS SDK folder (e.g. iPhoneOS17.2.sdk) Delete the SDK from the SDK Manager in Delphi On the Mac, in the ~\PAServer\scratch-dir folder, remove any folders starting with cache-dir In Delphi, re-add the iOS SDK Repeat the steps mentioned earlier for importing Swift frameworks, ensuring that you also follow the manual step involving copying of folders.

They are not supported. But in our solution you can use any VCL conrtol on full client area (our or third-party with GDI drawing). With Aero Snap or Snap Layouts (native caption area) you can put on caption area only controls with specifc drawing, which prepeared to draw on DWM border.