Lars Fosdal

Do you know if there is a QP report for this issue?

@Fr0sT.Brutal Valid point on the auto increment.

Doesn't this mean that if you have two devices accessing the same database, they can create duplicate AssetKeys? I prefer to use auto incremented ID fields in the database. If I was being security minded - I would also add GUID identities per row so that it would be much harder to abuse Id values in illegitimate queries if the keys are exposed in a web or REST UI. MS SQL example CREATE TABLE [dbo].[t_company_code]( [CoyId] [int] IDENTITY(1,1) NOT NULL, [CoyCode] [nchar](3) NOT NULL [CoyCreated] [datetime] NOT NULL ) ON [PRIMARY]; GO ALTER TABLE [dbo].[t_company_code] ADD CONSTRAINT [DF_t_company_code_Created] DEFAULT (getdate()) FOR [CoyCreated]; GO CREATE TABLE [dbo].[t_assets]( [AssetId] [int] IDENTITY(1,1) NOT NULL, [CoyId] [int] NOT NULL, [Description] [nchar](63), [AssetCreated] [datetime] NOT NULL ) ON [PRIMARY]; GO ALTER TABLE [dbo].[t_assets] ADD CONSTRAINT [DF_t_Asset_Created] DEFAULT (getdate()) FOR [AssetCreated]; GO -- You would then use a view to join them CREATE VIEW [dbo].[v_CoyAssets] AS SELECT dbo.t_company_code.CoyId, dbo.t_company_code.CoyCode, dbo.t_company_code.CoyCreated, dbo.t_assets.AssetId, dbo.t_assets.Description, dbo.t_assets.AssetCreated FROM dbo.t_company_code INNER JOIN dbo.t_assets ON dbo.t_company_code.CoyId = dbo.t_assets.CoyId; GO and do a select from the view SELECT CoyCode, AssetId from v_CoyAssets order by CoyCode, AssetId;

If that is the case, it sounds like a bug.

How old is the device? Does it come with an installer for the ActiveX driver? If you can identify the installed ActiveX control, you can in Delphi use the menu entry Component | Import Component... and choose either the Type Library or the ActiveX Control, depending on what you have at hand. If the device is old and you lack drivers - you would probably save money by finding a replacement.

It is often possible to reduce the problem to a small example - it just that it is sooo much work - and hey, we don't work in EMBT QA. Edit: ... or do we?

I leave the PC and IDE running 24/7 (unless travelling). I do however check in to git before I go have a beer on Friday 🙂

I´m still annoyed with the fact that not even a running Delphi is able to appropriately deal with DST changes while running. "No, all those files didn´t change... the time did."

@de la Mancha- you asked and got a relevant answer from someone known for doing heavy math with Delphi. No reason to be rude.

On Android, you should be able to move the caret to the right by tapping and dragging?

I am getting questions about supporting TLS 1.3 on our https interfaces again...

IMO, The .NET bits should be replaced instead of once more being patched to fix the broken code completion and refactoring.

Closed as cannot reproduce. Without sample code that actually can reproduce the problem, it is impossible to resolve the cause.

It is a problem that you have zero error handling around the Win32 operations in the Cmd method. Without the precise error information from the failing API(s), we are completely in the dark. F.x. if CreateProcess fails, you need to call GetLastError and log or pass on the error info somehow. Almost every Win32 API method will update last error.

Typed consts are not consts unless you type them on the right side of the expression. const NotAConst: Integer = -1; IsAConst = Integer(-1); The record type simply becomes a "scope" for const declarations. Benefit: the consts can be non-uniquely named without polluting your name spaces since you always need to prefix with the type name to access the const. Added bonus - you can have methods in the record declaration that can deal with logical operations related to the constants. type cButton = record const ThisIsFine = mrOK; end; cAnswer = record const ThisIsFine = String('This is fine'); end; cLimit = record const ThisIsFine = Double(3.14); end;

Without the actual error(s), we'll be guessing. Is it lack of process security elevation so that it fails due to insufficient rights?

type xConst = record const ButtonId = 1; end; procedure Test; var bId: Integer; begin bId := xConst.ButtonId; end;

Eurekalog or MadExcept would both be good choices to get to the bottom of any leaks or buffer overruns.

I tried changing the WP background. The setting doesn't take.

Also missing the other Parnassus plugins, as well as an updated XMLMapper.

To me, that is so blindingly obvious that either someone completely missed the mark, or said - "shit, that is too much work".

For some reason, 11.1 decided to discard the TMS and Eurekalog components on install, but it kept the general reg settings for the IDE. Didn't check the 64-bit paths - because we are still on 32-bit due to the state of the 64-bit debugger.

...or don't want to deal with all the positioning and scaling issues for forms that are opened by multiple developers with different DPI and scaling settings...

At least people seem to actually use QP now - even if not all of us bothers checking for existing issues 😛

@qubits You should report that on QP. Are you able to make a minimal project that shows the same leak?