Several months later, I changed platform to using Delphi 7. I’ve installed TQReport and TQRChart (TeeChart) into Delphi 7 (Since QReport is no longer installed by default in Delphi 7). The program works fine.

Then I decided to add some graphical theme into the software. It works fine too, unless my client finally notices a bug. The program will immediately generate a Stack Overflow when my program prints more than one graphical report.

The funny thing is, it fail to work on most computer (including my PC!), but one; the one that has the Windows Classic theme.

My first guess would be my graphical enhancement. But after I double check, I am using nothing but merely TImage all around the place. That bug must come from somewhere else.

Months go by, and I still couldn’t found the remedy for that problem, until I accidentally found an interesting article in the internet: XPManifest and TeeChart will generate a Stack Overflow.

Surprised, I checked my program again. Yes, it definitely uses the advantage of XPManifest. Guess what, after removing the manifest, I am free of that stupid bug. (Along with the good XP controls…, sigh)

Then again, I still don’t understand why that Stack Overflow occurs when XPManifest and TeeChart goes together… Oh well

1. Open Delphi
2. Click Components -> Install Package
3. A component window will open. Click Add…
4. Browse to Delphi7\bin and locate dclqrt70.bpl (QuickReport), dcltqr70.bpl (TeeChart for QuickReport), dcltee70.bpl (TeeChart)
5. Click OK and you’re set.

Notice that the QuickReport component tab is now available.

Update: I forgot to add two additional Package, the TeeChart for QuickReport and TeeChart, that will be required to use QRChart capability.

Sometimes a visit to the client’s computer is like opening a birthday present. We don’t know for sure whether the inside is good, useless, or full of crap. Various clients prefer various browsers, which generally result in either my CSS isn’t supported, some plug-ins reject my script, using a very old version of Internet Explorer, the screen is less than 1024×768 and we couldn’t find the video driver, or worse, all combined.

There are some alternatives:

1. Making sure the client is using the exact same browser. This means the user cannot use their favorite browser anymore.
2. Develop compatible software to all browser types there is. Quite another troublesome way, since the development cost and time will rise significantly. Not mentioning the user might try to upgrade to a different upcoming browser.
3. Develop your own browser. TWebBrowser unit is good, but remembering it is using internet explorer engine, we cannot be certain which version is compatible.

The third option sounds valuable. But instead of TWebBrowser, we’ll be using TMozillaBrowser to develop our own browser using Mozilla ActiveX Control. The details can be found here.

How do we do that

Here’s a step by step solution:

1. Download and install Mozilla ActiveX Control.
2. Run Delphi (in this case, I’m using Delphi 7)
3. Component -> Import ActiveX Control -> Choose Mozilla Control 1.0 Type Library (Version 1.0)
4. If the component isn’t there, you have to register the DLL first by running regsvr32 mozctlx.dll at the command prompt.

5. Click Install. A new component will appear at ActiveX tab.

That’s all there’s to it. Using the component is pretty much the same with TWebBrowser, albeit the green color and its inability to resize at design time are pretty annoying. The latter one can be resolved by dropping the component into a TPanel, setting the Align to alClient. You can now resize the panel.

I’m still trying to communicate the browser with the JavaScript inside the web application though. This can be quite a hard work.

It’s a collection of great components for Delphi, which lead me to believe I found a treasure.

After I downloaded the ZIP file, I read the manual carefully but cannot found an instruction of installation. No, installing the DPK itself is useless.

I did spotted an install.bat file, but I can’t make it work.

After some googling events, I saw a light of hope, and managed to install it successfully. I’ll describe them in a very short steps:

1. Download the package (Duh!). I was downloading the version 3.33, but after some time, they launch the 3.34. The file should be named JVCL333CompleteJCL1101-build2725.7z with the 333 part as the version number.
2. Decompress this file (You might need a 7z unpacker for this) into {Your Delphi Directory}\Source. This is the reason why I can’t install the package. I was extracting these files into \Lib directory.
3. Run install.bat in the JCL folder. This will compile and run the installer. I guess the JEDI team does a great job huh?
4. The installer will show you all your available Delphi version.
   
5. Install the JCL.
6. Repeat step 3 for JVCL folder, this time the installer will be a little bit different, but you’ll get the grip.
   
7. Run Delphi. You should see lots of component tabs appear.

I’m still trying to figure out how to use them in my projects. Maybe I’ll add more entries after I learned some.

I usually used my Splash Screen as the main form (Since it’s the first one to show up). The problem is I can’t CLOSE it (by doing that will also close the application), and I looked like a totally script kiddies when my code is published. Only God knows what kind of mayhem I produced by using such technique.

Here’s how to make a better (and professional) splash screen

By slicing and analyzing the pattern, this error always occurs when I’m trying to Free and NIL an object. I’m pretty much confident for the array index, so it should not be the reason for this error.

procedure FreeButtons(Buttons: TButtons);
var
  Cnt : integer;
begin
  for Cnt := Low(Buttons) to High(Buttons) do begin
    FreeAndNil(Buttons[Cnt]);
  end;
  SetLength(Buttons, 0);
end;

This error appears after I ported my old SDI framework into an MDI one. It works perfectly fine earlier, but now definitely gives me some headache. I vaguely presume the reason behind this is the component ownership, but I still hasn’t convinced yet.

Then I stumbled on an article at http://delphi.about.com/od/kbcurt/a/dynamiccreation.htm about dynamic object creation. This article point out that if we’re going to free an object later, we should assign NIL as its parent.

Conclusion

So I finally came down to a conclusion and know exactly why the application always point to a non-readable address. It’s simply because when I’m destroying a form, the dynamically created components were also destroyed as well! This feature should not be a problem on its own, but when adding up the array index (which obviously not getting reset when the form destroyed) into account, problem occurs.

The workaround for this solution is to destroy the component myself, and set the value to nil.

FreeButtons(SES_Buttons_Category);
FreeButtons(SES_Buttons_Subcategory);
for I := 1 to MAX_ORDER do begin
  for J := 0 to MAX_OPTION do begin
    FreeSpeedButtons(SES_OR.Data[I].Options[J].Buttons);
  end;
end;

Case Closed.