dormky

Ah, it might be the debug info indeed for the big changes when formatting. But there's still differences when compiling 2 times in a row, which I can't explain (see attached files in the OP)

Well, I just checked on the effects of formatting on .dcu files and they seem to be affected a lot. Very strange that intermediate compiler files would be affected by formatting. Does delphi output other intermediate files that I could check ?

When I build .dcu files, they often aren't the same size. Does anyone know why that is ? I literally just build two times in a row, and between 5 and 10% of .dcu will have a size difference of a few dozen bytes. I'm trying to apply formatting to the whole project and want to verify that the output is not affected (trust but verify, heh ?) but if building the same thing twice already leads to significant changes this will be quite difficult to achieve... And yes, we have 0 test coverage. Edit : Example with this small file, where 4 bytes are added at around 3/4ths of the file. UConfigEchelle_big.dcu UConfigEchelle_small.dcu

DataSetHelper does indeed seem to be what I'm looking for ! Too bad I'm almost finished writing the RTTI solution described just above by Lars, which I suppose is what DataSetHelper is doing. Writing it myself was what i wanted to avoid, but alas. Since I've written tests for it I'll use my code, but thanks for coming though anyway 🙂

Damnit, the debugger is showing the error on the wrong line. I had an invalid typecast, but in the next block of code... Thanks :')

I'd like to create a TValue that holds a TBytes array. From what I see of TValue's code, it doesn't seem to be designed for such, even by using variants. Alternatively, if I can just get a pointer to the relevant instance field from TRttiField and cast it to a TBytes, that'll work too.

I had two version of RAD Studio installed. 10.3 under license, 11 under free trial. I uninstalled 11, and now 10.3 doesn't work anymore (no debugging). I'd like to re-install it, but can't find the installer anywhere on Embarcadero's website. There's only the free trial.

I'm trying to have the dialogs like MessageDlg be translated. Looking at the code in Vcl.Dialogs, it uses the LoadResString function to get the string for the buttons. It doesn't look like it can handled multiple sources for the same string, but I could be wrong because it would be kind of insane to force dialogs to be in one language only. But this is Delphi, they aren't known for making logical design decisions.

Frames look great, thank you for sharing !

Hello, I have a series of 4 numbers describing current atmospheric conditions, currently shown in a TGroupBox with each number in a TEdit. I'd like to encapsulate the behavior related to these numbers (color changes) into a component so I can re-use it in multiple places. I've created a new component based on TGroupBox, but when opening it there's no Design tab, and I don't want to use code to describe the UI as this runs opposite to what is generally done in Delphi (where you use a graphic UI editor). How can I get my custom TGroupBox component in a Design tab so I can edit it (with a .dfm) ?

The TLabel was just for demonstration purposes, I'd like to be able to do that with all components...

I don't want to change anything about other controls, I just need a control to be on top of all others. Yes, that's why I'm looking for an alternative. Do you know of any component that could work on the same group as my TPageControl here ? I suppose I could use such a component, make it invisible but keep a child control of it visible, if that's possible.

The following code shows that BringToFront does not work. Are there any alternatives I can use to put a control on top of all other controls in a window ? interface uses Vcl.Forms, Vcl.ComCtrls, System.Classes, Vcl.Controls, Vcl.StdCtrls, UUtils, Vcl.ExtCtrls; type TFormMain = class(TForm) PageControlMain: TPageControl; Sheet1: TTabSheet; Button1: TButton; procedure FormCreate(Sender: TObject); procedure Button1Click(Sender: TObject); private dynLabel: TLabel; end; var FormMain: TFormMain; implementation {$R *.dfm} procedure TFormMain.Button1Click(Sender: TObject); begin dynLabel.BringToFront(); end; procedure TFormMain.FormCreate(Sender: TObject); begin dynLabel := TLabel.Create(self); dynLabel.Parent := self; dynLabel.Height := 200; dynLabel.Width := 500; dynLabel.Top := 100; dynLabel.Left := 100; dynLabel.Caption := 'BAMKLJDOUZEHFOZEI'; dynLabel.Visible := True; dynLabel.BringToFront(); end;

It doesn't adapt the image size to the control size. Mods, please delete this post 🙂

It's because with the default connection parameters, it was connecting to the production database. Which of course did not have the added column. Don't ask me why this is done by default at design time, I inherited this project...