Tom Mueller

There are not so many resource strings. In my DevExpress package I include 45 units with "resourcestings" in it - that will extracted about ~5000 resource stings. PS: Sorry for the delayed answer.

Yes, I tried this approach - but it is a clumsy way. - limit the units by try_and_error per package - merge the resulting drc-files into one drc-file per 3rd party for the translation tool Actually Delphi raises the error after the creation of the drc-file (so the linker does its job with the drc-file but then raises E2621 when trying to create the bpl-file). Our automated building process will stop because of this error. I wonder if there is an option to tell the linker to just extract resources?

When changing a property value, for example the name property of a TLabel in the object inspector and then directly select another component on the form, the changed name value is not saved. Only pressing the Enter key or changing to an other property saves the changed value. Steps to reproduce: add two TLabel on an empty form and select one change the name of the label without pressing the enter-key select the second label select the first label again -> your changed name is gonne! In Delphi 10.2.3 Tokyo this error was not present. It is not a killer bug but a very annoying issue! Can anyone reproduce this issue? PS: I reported the bug on https://quality.embarcadero.com/browse/RSP-23694

Yes - some properties get refreshed during typing and some not. So far I checked the properties for some basic components that do not refresh: - BevelWidth - Top - Left - Width - Height - Tag - ImageIndex - Margins (Bottom, Left, Right, Top) - Constraints (MaxHeight, MaxWidth, MinHeight, MinWidth) - TabOrder It seems most numeric properties (beside the Name property) do not fire a change event when loosing the focus.

Thank you for your tests - so it seems that this error came with 10.3 Update 1. I will comment this in the bug report https://quality.embarcadero.com/browse/RSP-23694 Please vote for the fix for this error in the bug report - so we might have a chance to see the error fixed in 10.3 Update 2 soon.