delphi-2009

Assume you have the following: //Note the original example I posted didn't reproduce the problem so //I created an clean example type IParent = interface(IInterface) ['{85A340FA-D5E5-4F37-ABDD-A75A7B3B494C}'] procedure DoSomething; end; IChild = interface(IParent) ['{15927C56-8CDA-4122-8ECB-920948027015}'] procedure DoSomethingElse; end; TGrandParent = class(TInterfacedObject) end; TParent = class(TGrandParent) end; TChild = class(TParent, IChild) private FChildDelegate: IChild; public property ChildDelegate:IChild read FChildDelegate implements IChild; end; TChildDelegate = class

got a strange problem: I create a TPanele at runtime and change its color - however, the color is still clBtnFace. Here' the code: procedure TForm1.Button1Click(Sender: TObject); var pnlTest : TPanel; begin pnlTest := TPanel.Create(Form1); pnlTest.Parent := Form1; pnlTest.Width := 100; pnlTest.Height := 100; pnlTest.Color := clRed; end; Any ideas? Thanks! When you want to have colored panels under a themed OS you have to set ParentBackground to False. user5512468 Try this :-) procedure TForm1.Button1Click(Sender: TObject); var pnlTest : TPanel; begin pnlTest := TPanel.Create(Form1); pnlTest

I want to apply a fix from QC to a Delphi 2009 unit (DBClient as it happens). I know I need to copy the unit to another directory and make the change to the copy. How do I then get Delphi to compile that unit and use it in favour of the DCU that already exists? If you don't want to modify the original .Pas file, I do this by copy the .Pas file into my application folder, then choose built project, it will create new dcu file in my application folder, which will be used instead of the original one. It's kind of a last resort (and not supported by CodeGear), but I do something similar to

Since my question from yesterday was perhaps not completely clear and I did not get the answer I wanted, I will try to formulate it in a more general way: Is there a way to implement special behaviour based on the actual type of an instantiated generic type either using explict conditional statements or using some kind of specialization? Pseudocode: TGenericType <T> = class function Func : Integer; end; ... function TGenericType <T>.Func : Integer; begin if (T = String) then Exit (0); if (T is class) then Exit (1); end; ... function TGenericType <T : class>.Func : Integer; begin Result := 1;

I'm perplexed. At CodeRage today, Marco Cantu said that CharInSet was slow and I should try a Case statement instead. I did so in my parser and then checked with AQTime what the speedup was. I found the Case statement to be much slower. 4,894,539 executions of: while not CharInSet (P^, [' ', #10,#13, #0]) do inc(P); was timed at 0.25 seconds. But the same number of executions of: while True do case P^ of ' ', #10, #13, #0: break; else inc(P); end; takes .16 seconds for the "while True", .80 seconds for the first case, and .13 seconds for the else case, totaling 1.09 seconds, or over 4 times as

Very recently I have come back to Delphi after a long pause and written a rather straightforward utility app my client requested to support an older release... I know these days the size does not matter much, but it struck me as odd that the one-unit application, when compiled, amounted to 1'084'416 b executable. The one and only .pas unit I wrote is some 20.8k large, mostly because of the richness of the gui. The uses clause is as follows: uses Windows, Messages, SysUtils, Variants, Classes, Controls, Forms, strutils, Dialogs, ADODB, DB, DBGrids, ExtCtrls, DBCtrls, StdCtrls, Grids, Menus,

Delphi 2009 uses build configurations . When you create a new project you have two default build configurations "Debug" and "Release". Now I asked myself how to automate builds using MSBuild (which is supported by Delphi since version 2007). You can start the "msbuild" command in the "RAD Studio Command Prompt" in some Delphi project directory and it will build the default build configuration (the last activated build configuration inside the Delphi IDE). Now, I want to specify a certain (non-default) build configuration by a command line parameter. The Delphi help asserts that the parameter

With Delphi 2009 Enterprise I created code for the GoF Visitor Pattern in the model view, and separated the code in two units: one for the domain model classes, one for the visitor (because I might need other units for different visitor implementations, everything in one unit? ' Big ball of mud ' ahead!). unit VisitorUnit; interface uses ConcreteElementUnit; type IVisitor = interface; IElement = interface procedure Accept(AVisitor :IVisitor); end; IVisitor = interface procedure VisitTConcreteElement(AElement :TConcreteElement); end; TConcreteVisitor = class(TInterfacedObject, IVisitor) public