I will give you some keys and some tips to choose the most adapted Logging system for you. This article will deal only with Delphi applications.

Have your ever live this situation?

 Just replace the underlined Italic Text to get your favorite situation!

User 1: Hi, I have a problem with your software when I click on the button it doesn’t work he must do this thing, after that the software crashes and I’m losing all my work….

User 2: Hello, Today I try a new function but it looks like doesn’t working as expected. For proof I haven’t successfully done this thing.

User 3: Hi, Your software is great but after two weeks, it’s so slow, what is the problems?

User 4: Hi, you app is really unstable when I use too much objects.

Personally I hate this !  WTF? What is “The button”? What are you doing with “this function” ? Before using “this function” ? Fortunately, when there is a bug, there are often more messages from many customers and you get some precious clues!
Generally I send another mail to have more information. Waiting for the hypothetical answer, I’m trying to search the code. But if it isn’t reproducible this is really difficult.

First solution doing your own Log Solution:

For my application, I started to code a log viewer and integrate an object TDBB_LOG which handle everything when I need to log things. It’s a derivated class from TDatabase (it’s mine) which contains all the necessary tools when I need to deal with SQLite Databases. So as you see it’s a really simple class which show a procedure named add_log. I used this procedure to add something to the LOG database.

 TDBB_LOG = class(TDatabase)
private

public

constructor Create(const the_pass: string); reintroduce; overload;
destructor Destroy; override;

procedure Add_log(const Processus, Description, Groupe: string; const Level: TLOG_Level; const Resultat: TLOG_Result);
procedure Listing_LOG(Retour: TObjectRetour; const SQL_END: string);

protected
end;

var
BDD_Log: TDBB_LOG;

And the two type :

// Type pour le log
// ---------------------
TLOG_Result = (tlr_normal, tlr_warning, tlr_error);
TLOG_Level = (tll_highest, tll_high, tll_normal, tll_low, tll_lowest);

It was working pretty great; I had created a G.U.I to allow the user to see the log.

My old log viewer

The user could select time/date interval, the number of log entries to show and the type of entries (normal, warning, error). I also add a way to expand and contract some categories, sorting, moving, re-sizing column…

It works !

At the beginning it was ok, but after some times, I realize that it was not the alpha and the omega. A lot was missing ; the performance was not fantastic (but not bad at all). And I had no time to spend more on this. My goal was to integrate a complete logging framework to correct bugs very fast and provide a good experience for my customer when they have a problem.

I also really would like to have a remote (and secure) access to the log for beta testers. But it will cost me again, time…

Pros:

-         Price! It’s free !
-         You have the Full Source, and you are not dependent of updates.
-          You are doing what you want and you have access to everything In your app.
-          The log system and viewer are directly in your app.
-          No extra app and extra code from strangers.
-          Maybe more secure?
-          You add only needed things but you are often disappointed when the problem occurred and you forgave something…
-          You could be proud of you : D, it’s your own logging system.

Cons:

-          It takes you time, and you don’t have time.
-          It’s full of bugs, and it’s not reliable at the beginning.
-          The log viewer is not “great” for hunting bugs and problems, really, you haven’t time to create a first world class viewer.
-          The log system and viewer are directly in your app (And if it crashes?)
-          You must code well and pay attention to every detail. Databases, Thread Safety, …
-          The log file and viewer will not be optimized at first.
-          You must code the remote access, it will takes time to code, test, debug…
-          How to manage multiple instances of software ? Tobject, published property ? (-> Need to code more…)
-          If you have a Suite (multiple applications for one software), it will takes you again time (If you have a thread safe log manager, it will not be very long, I guess.)

Rate : 

It’s not an exhaustive list and not fully objective, forgive me I’am not omniscient.

Surfing on the web for a solution I found two solutions to handle logs without spending too much times coding it : SmartInspect  by Gurok and CodeSite by Raize (which is provide in an express edition by Embarcadero in Delphi XE and Delphi XE2).

We will see the pros and cons of theses two solutions.

CodeSite by Raize :

CodeSite Studio/Express is a third-party tool developed by Raize Software (http://www.raize.com), an US enterprise directed by Ray Konopka. When you have questions, the support is fast, reactive and competent. The express version is available when you bought Delphi; it’s a third party tool integrated since Delphi XE. Usually when Embarcadero/Borland says “express” edition from, you must hear limited version. It’s a sort of Trial without time restriction but with fewer functions.

Let’s look at the description:

“The CodeSite Logging System gives developers deeper insight into how their code is executing, which enables them to locate problems more quickly and ensure their application is running correctly. CodeSite’s logging classes let developers capture all kinds of information while their code executes and then send that information to a live display or to a log file. Furthermore, both styles of logging, live logging and file logging, can be performed locally or remotely.”

So in order to use CodeSite logging system, you need two things:

1. Adding CodesiteLogging unit to your project. In fact when you will add it, some methods will be accessible.
2. Running a “Dispatcher” (I will explain just after) in background! Even if you are the customer! It’s needed, it’s not an option!

How CodeSite is working?

When you add CodeSiteLogging.pas in uses, a TCodeSiteLogger Object is created in initialization section. This object is accessible with the variable CodeSite in your unit Implementation.

Don't forget to add CodeSiteLogging.pas

How CodeSite works ?

This CodeSite object will send all the log-informations using SendMessage (http://msdn.microsoft.com/en-us/library/windows/desktop/ms632590%28v=vs.85%29.aspx) to send the information to the dispatcher. The goal of the dispatcher will be to “dispatch” the data to the log viewer, to a remote computer (Tcp/ip using Indy) or to a log file….

That’s why you NEED to have the dispatcher running!

About the dispatcher:

It’s an app provided by Raize (you don’t have sources). It’s redistributable and free for your users. So if a user wants to have logging features working on his computer he will need to Install the software from Raize…

Here you see what are the command line option of this redistribuable packages :

“// The CodeSite Tools can be installed silently by specifying some
// command line options when executing the CS4_Tools.exe program.
//
// To run CS4_Tools in silent mode, use the following options:
//
//     CS4_Tools /s
//
// The above statement will install the CodeSite Tools using default settings.
// Specifically,
//
// 1. All Tools are installed (Dispatcher, Controller, File Viewer, Live Viewer)
// 2. NO program group is created for the installed Client Tools
// 3. The Dispatcher runs in Stealth mode
//
//
// If you would like to change any of the defaults, you can run the setup
// program with the following options:
//
//     CS4_Tools /s /m=CodeSiteToolsSetup.txt
//
// The above statement also runs the setup program silently, but also allows
// the various setup options to be customized.  By specifying this file, in
// the /m parameter, the following settings can be customized as needed.

// Set to NO to prevent the CodeSite Controller from being installed
INSTALL_CONTROLLER=YES

// Set to NO to prevent the CodeSite File Viewer from being installed
INSTALL_FILE_VIEWER=YES

// Set to NO to prevent the CodeSite Live Viewer from being installed
INSTALL_LIVE_VIEWER=YES

// Set to YES to create a program group for installed client tools
CREATE_PROGRAM_GROUP=NO

// Set to STEALTH, RESTRICTED, or UNRESTRICTED
DISPATCHER_MODE=RESTRICTED”

Personally I don’t like this. It’s not “cool” to force the user to install software from another company to use all the capability of yours. Silent installation is not a great choice for the user (I don’t want to force them to install third-party tool! It could be problematic in the futur…). Finally I don’t know if Raize gives the sources for the dispatcher, I think it’s a minimum (I hope). If I could recompile it, and adapt the gui to integrate it in my software suite it could be great. But it’s not.

Now it’s time to log:

If you want to trace your CodeSource you will need to add a lot of lines of code (like always)! What are the CodeSite procedures to send log?

Please look at the example below, you will understand very fast.

procedure TForm1.Button1Click(Sender: TObject);
var
i: Integer;
begin
// When you want to send a simple message
CodeSite.SendMsg(csmWarning, 'Message');
// If you want to send the published property of a TObject by example
CodeSite.Send(csmYellow, 'The form !', Form1);
// If you want to send an exception
CodeSite.SendException(Exception.Create('It''s an exception'));
// If you want to send a Color
CodeSite.SendColor('A color', clred);
// If you want to send a warning
CodeSite.SendWarning('Blablabla');

// Add a separator
CodeSite.AddSeparator;

for i := 0 to 5 do
begin
// Add a checkpoint
CodeSite.AddCheckPoint;
end;

// Add a separator
CodeSite.AddSeparator;

// Another great thing is to indent log in order to have a clearer view
CodeSite.EnterMethod('A METHOD');
try
// Send a screenshot of the form
CodeSite.SendScreenShot('ScreenShot', self.Handle);

CodeSite.EnterMethod('Imbricated Method');
try
// Send Version info
CodeSite.SendVersionInfo(csmInfo);
finally
CodeSite.ExitMethod('End of it');
end;

finally
CodeSite.ExitMethod('End of A METHOD');
end;

end;

Let’s see the result on the live viewer :

The CodeSite log viewer

There is a way to integrate faster Codesite loc : the templates.

Templates

You have a lot more functionality like creating different levels for entry, changing color, add separator, reminder etc… I’am not using daily CodeSite so my judgement is surely subjective… But this is the list of the pro and cons for me.

Pros:

-       VERY EASY TO USE !!!!!
-       Price! The express edition is free in Delphi XE/XE2…
-       With “CodeSite Method Tracer expert” you could insert in every method (code) the EnterMethode and LeaveMethod lines of code.
-       It’s really reliable, you don’t have to reinvent the wheel.
-       Great Support !
-       Viewer is great. You could filter, search, add breakpoint and a lot of other stuffs.
-       Ability to log TObject, to indent method, to send to a remote machine, etc…
-       Plugins could be added.
-       Communication with Messages is great and fast (too much messages slowdown Windows). (No Firewall is triggered). You could use TCP/IP if you want.
-       It’s pretty easy to log multiple software. If you are developing a Suite ?

Cons:

-       The express edition is limited…
-       The price !! 400$ !
-       The dispatcher is not the best solution for me. I don’t want to add several tools for every functionality of my software.
-       If there is a bug and Raize don’t want to correct it, you will be in trouble.
-       I don’t think the dispatcher source is available. You are launching a blackbox on customer computer…

Rate : 

SmartInspect by Gurok :

The last but not the least : SmartInspect by Gurok. It’s a German product. This is my favorite one and the solution I choose for my software. Don’t forget it’s just a point of view. Please keep in mind that I’am not a Delphi Guru.

Log what you want, in the format you want :

Smartinspect is providing as much Codesite provide but with small differences. I will detail the ones I have found. And show you how it works in my application.

One thing I love is the ability to easily change at runtime/designtime the way of SmartInspect is managing the log. Gurok is providing a tool named “SmartInspect Configuration Builder” which is designed to help you to create “configuration file”. Don’t worry you are not forced to use theses.

Main Form of SmartInspect Configuration Builder

In the first tab named “general”, you can enable the login, set the application name, the level of logging and the default level of logging.  The second tab is named “Connections” you could choose what sort of protocol you would like to use to store/send the log. Please see below :

Protocol Combobox of SmartInspect Configuration Builder

Info : The pipe protocol is used to log directly to a local SmartInspect Console over a named pipe.

After you add it, you could configure a lot of things : please see the example for File Logging :

File logging option - SmartInspect Configuration Builder

The last tab is “Sessions”, it permits to configure new “sessions”, you could change the name, color, level of logging for each one. If no entry session is found, SmartInspect will use the default one.

Adding SmartInspect to your app :

Like CodeSite you need to add units to your code : SiAuto, SmartInspect.

Add SmartInspect units to the uses section.

Now, the TSmartInspect Si TObject is created and will help you to handle log. If you would like to Load a configuration file use :

 Si.LoadConfiguration('configuration.sic'); 

I prefer in my app not using Configuration Builder. I use my own solution and avoid the multiplicity of configuration files in main directory. So I created a special tab in the configuration Form of my app, in this tab I let the user change logging conf and save them to an INIFile.

My own logging configuration builder

A first version of my unit which is dedicated to load SmartInspect is available below :

{$REGION 'Informations'}
{
Auteur : Rémi MEVAERE (OnKeySoft)
---------------------------------
Date de création : 30 Mars 2012
Description : Le log est important ici...
Version : 0.0.0.1
Dernière modification : 30 Mars 2012
---------------------------------
Historique :
0.0.0.1 : Création du fichier
}
{$ENDREGION}

// Load the log
function Load_the_log: boolean;
var
INI_File: TIniFile;
Chemin_Ini: String;
// Variables_Utiles
Config: TConfiguration;
Con_config: string;
Buffer: string;
begin
result := False;
si.Enabled := False;

// Ou se trouve le fichier de configuration
Chemin_Ini := extractfilepath(Application.ExeName) + Nom_P_Filename + '.ini';
try
// On charge le INI et l'objet conteneur
INI_File := TIniFile.Create(Chemin_Ini);
Config := TConfiguration.Create(False);

try
with Config do
begin
{$IFDEF DEBUG}
Log_Enable := INI_File.ReadBool(Ini_Log, Ini_Log_Enable, true);
{$ELSE}
Log_Enable := Conf.ReadBool(Ini_Log, Ini_Log_Enable, False);
{$ENDIF}
if Log_Enable then
begin
// On Charge le reste
Log_EnableRemote := INI_File.ReadBool(Ini_Log, Ini_Log_EnableRemote, False);
Log_EnableText := INI_File.ReadBool(Ini_Log, Ini_Log_EnableText, False);
Log_TextPattern := INI_File.ReadString(Ini_Log, Ini_Log_TextPattern, '[%timestamp%] %level%: %title%');
Log_Path := INI_File.ReadString(Ini_Log, Ini_Log_Path, GetRoamingUserAppDataPath + Path_App_Data + Path_Log_Dir);
ForceDirectories(Log_Path); // Creation du repertoire
Log_IPRemote := INI_File.ReadString(Ini_Log, Ini_Log_IPRemote, '127.0.0.1');
{$IFDEF DEBUG}
Log_Level := TLog_Level(INI_File.ReadInteger(Ini_Log, Ini_Log_Level, 0));
{$ELSE}
Log_Level := TLog_Level(Conf.ReadInteger(Ini_Log, Ini_Log_Level, 1));
{$ENDIF}
Log_MaxFiles := INI_File.ReadInteger(Ini_Log, Ini_Log_MaxFiles, Log_Default_Files);
Log_MaxSize := INI_File.ReadInteger(Ini_Log, Ini_Log_MaxSize, Log_Default_Size);
Log_Rotate := TLog_Rotate(INI_File.ReadInteger(Ini_Log, Ini_Log_Rotate, 3));

// Création des parametres du log

// 1 - Direct PIPE
{$IFDEF LOCAL}
Buffer := 'pipe(reconnect=true, reconnect.interval=1s, level="debug")';
if (Con_config <> '') then
Con_config := Con_config + ',' + Buffer
else
Con_config := Buffer;
{$ENDIF}
// 2 - Le fichier ISL
Buffer := 'file(append="true"';
Buffer := Buffer + ', filename="' + Log_Path + 'log.sil' + '"';

if Log_MaxFiles <> 0 then
Buffer := Buffer + ', maxparts="' + inttostr(Log_MaxFiles) + '"';

if Log_MaxSize <> 0 then
Buffer := Buffer + ', maxsize="' + inttostr(Log_MaxSize * 1024) + '"';

case Log_Rotate of
LOG_HOURLY:
Buffer := Buffer + ', rotate="hourly"';
LOG_DAILY:
Buffer := Buffer + ', rotate="daily"';
LOG_WEEKLY:
Buffer := Buffer + ', rotate="weekly"';
LOG_MONTLY:
Buffer := Buffer + ', rotate="monthly"';
end;

case Log_Level of
LOG_DEBUG:
Buffer := Buffer + ', level="debug"';
LOG_VERBOSE:
Buffer := Buffer + ', level="verbose"';
LOG_MESSAGE:
Buffer := Buffer + ', level="message"';
LOG_WARNING:
Buffer := Buffer + ', level="warning"';
LOG_ERROR:
Buffer := Buffer + ', level="error"';
LOG_FATAL:
Buffer := Buffer + ', level="fatal"';
end;

Buffer := Buffer + ', encrypt="true", key="' + Pass_LOG + '"';
Buffer := Buffer + ', reconnect="true", reconnect.interval=1s)';

if (Con_config <> '') then
Con_config := Con_config + ',' + Buffer
else
Con_config := Buffer;

// 3 - Le fichier Text

if Log_EnableText then
begin

Buffer := 'text(append="true"';
Buffer := Buffer + ', filename="' + Log_Path + 'log.txt' + '"';

if Log_MaxFiles <> 0 then
Buffer := Buffer + ', maxparts="' + inttostr(Log_MaxFiles) + '"';

if Log_MaxSize <> 0 then
Buffer := Buffer + ', maxsize="' + inttostr(Log_MaxSize * 1024) + '"';

case Log_Rotate of
LOG_HOURLY:
Buffer := Buffer + ', rotate="hourly"';
LOG_DAILY:
Buffer := Buffer + ', rotate="daily"';
LOG_WEEKLY:
Buffer := Buffer + ', rotate="weekly"';
LOG_MONTLY:
Buffer := Buffer + ', rotate="monthly"';
end;

case Log_Level of
LOG_DEBUG:
Buffer := Buffer + ', level="message"';
LOG_VERBOSE:
Buffer := Buffer + ', level="message"';
LOG_MESSAGE:
Buffer := Buffer + ', level="message"';
LOG_WARNING:
Buffer := Buffer + ', level="warning"';
LOG_ERROR:
Buffer := Buffer + ', level="error"';
LOG_FATAL:
Buffer := Buffer + ', level="fatal"';
end;

Buffer := Buffer + ', pattern="' + Log_TextPattern + '"';
Buffer := Buffer + ', reconnect="true", reconnect.interval=1s)';

if (Con_config <> '') then
Con_config := Con_config + ',' + Buffer
else
Con_config := Buffer;

end;
{$IFDEF REMOTE}
// 4 - Le Remote
if Log_EnableRemote then
begin
Buffer := 'tcp(';

Buffer := Buffer + ', host="' + Log_IPRemote + '"';
Buffer := Buffer + ', level="debug"';
Buffer := Buffer + ', reconnect="true", reconnect.interval=1s)';

if (Con_config <> '') then
Con_config := Con_config + ',' + Buffer
else
Con_config := Buffer;
end;

{$ENDIF REMOTE}
si.Connections := Con_config;
si.Enabled := true;
si.DefaultLevel := lvDebug;
// Debut du Logging
siMain.ResetCallstack;
SiMain.LogSystem;
SiMain.LogMemoryStatistic;
SiMain.LogMessage('Log is loaded');
SiMain.LogObject(lvDebug, 'Starting the Log : ' + Con_config, Config);

end;
end;
result := true;
finally
INI_File.Free;
Config.Free;
end;
except

end;

end;

So as you can see, SmartInspect is flexible and you could change everything in Runtime (and at anytime). Don’t forgive here you don’t have to install blackbox or third party exe.

Lets log begin :

After adding correct units, you could use the SiMain or any else Sesssions (see on top) which are both TSiSession Object. SiMain is exposing all the function to log string, object, color, screenshot, memory….

Some methods exposed by TSiSession

I will not describe everything it’s very close to CodeSite. Use the adapted methods to log the things you want.

To help you, SmartInspect is providing templates (like CS) : (here you can see the Method LeaveThread which will permit to separate all Threads in the Viewer).

Code Templates

SmartInspect also provide Delphi Expert to assist you when you want to EnterMethod and LeaverMethod (you know, like with CS when you want to have a better visibility).

Open SmartInspect Delphi Expert, Menu -> SmartInspect -> Instrument Unit

Now opening the Log Viewer :

And start the app to begin logging.

Main Screen of Log Viewing

I will not spend time to details “standard” functions like searching, copying, moving into log entries, adding breakpoints… I will just show you why I’am prefering SmartInspect Console.

Why the SmartInspect Console is better !

1 : As you can see you could create different categories, in each categories you could add views. And each view gives you the opportunity to have a more clear and more precise idea of the log to understand problems and correct them.

2 : As CodeSite you could see the Call Stack, it’s a precious information.

3 : As in Delphi Debuggers, you could watch/track some variables. It’s useful when you want to remote debugging and understand in what conditions your program are running (How much thread ? How much dbb ? How much data ?)… This value is change when you are using this code :

{$IFDEF DEBUG} SiMain.IncCounter('#Open DBB'); {$ENDIF}

4 : Just imagine you have 5 beta testers currently running your software, you are running it on your own computer… To avoid headache you could use this list to view where the processes are running and use it to filter the one you wants !

5 : As in CodeSite you could track TObject, Pictures and other data. It’s terribly useful.

6 :  Each Tab is a view. In a view you could filter data and accept only some things. Highlight stuff with Regular Expression (In the screenshot I’am highlighting each lines with “Create”).

7 : The main Window, it’s fast and clear. You could see indentation, highlighting and other things.

 8 : A reason why i’am choosing SmartInspect is this Watches Graph. You could draw graph with Watches data to see the evolution. Here I’am tracking the number of databases opened. If someone have a problem I will see in one second if there is too much DBB opened !

For me the SmartInspect Console is better. In conclusion :

Pros:

-       Easy to use and much faster.
-       More complete than CodeSite.
-       Work with .NET (C# VB.Net), Java, Delphi.
-       More affordable : 200 €
-       Don’t add a blackbox to customer computer.
-       A lot of communication ways available. File, Memory, Pipe, TCP, Text.
-       On the fly configuration.
-       Maximum log files, encryption, log rotation, log level, backlog, asynchronous !
-       It’s really reliable, you don’t have to reinvent the wheel.
-       Great Support, Gurok brothers are very kind.
-       Viewer is really great. Better than CodeSite. Powerful filters to manage multiple “sources” of log (If you are tracking several beta-testers)
-       Watch and Monitor resources and trace graphs.
-       Ability to log TObject, Screenshot, Memory information and everything you want.
-       It’s pretty easy to log multiple software.
-       Fully ThreadSafe, Synchronized and support a lot of threads.
-       Redistribuable Console for your users.
-       Library for PHP/Python and adapter for Log4j, Log4net, PostSharp
-       SDK available to access log.

Cons:

-      Can’t add plugin !
-      The price : it’s not free.
-      Not full sources.
-      Need to pay update every year (50€)

Rate : 

Conclusion :

I know, I haven’t describe every features of this two tools but I have just bought the second one. It’s just a point of view. In my app I’am combining the power of TEurekaLog with TSmartInspect in that way when there is an exception I’ve got usefull information from the Exception Manager and the log is automatically send so I hope I will not have as much problem as in the past when a user get a problem. I will not use anymore the trick :

 showmessage('First thing'); 

Which is really time hunger and very frustrating. CodeSite is a great tool, directly integrated in Delphi Third Party bundle and the author is really kind. It could maybe be more adapted in several situations but I prefer the freedom of SmartInspect.

You could also code your own tool but it will cost you time and maybe more money cause it will not be operational at beginning (unless you are a Genius coder (but i’am not)).

I hope this article will be useful for you, if you want to add some things don’t hesitate to add a comment I know you are reading this !

Introduction

So I installed Tortoise 64bits (Win64 here), I create a repository and I started to use this fabulous tool directly in the Explorer. But I remembered something ? Is there any tool directly integrated in Delphi IDE ? I checked the features chart :

And tried to use it (just tried)…

Subversion is really great, but it’s a pain in the ass to use it directly in Delphi IDE. I always have some mystical and strange errors/bugs/warnings when I’am using it. I will try to help you to beat this one:

“The path ‘blablabla’ appears to be part of a SubVersion 1.7 or greate corking copy rooted at ‘blablabla’. Please upgrade your SubVersion Client to use this working copy.”

I will explain you how to upgrade it simply and fastly.

Uninstalling Embarcadero SubVersion Integration

• Delete the Expert, directly in the IDE (Component -> Install Packages)
• Delete the Subversion directory in Embarcadero Rad Studio Folder (\Embarcadero\Rad Studio\X.0\bin\subversion
• Delete the BPL (Search *svn* files in Explorer)
• It’s done, SubVersion Integration is removed

Installing SubVersion updated

Be careful,  Delphi IDE is a Win32 application, so it can load just 32bits DLL. We need to install last version of SubVersion but in 32 bits (If you are using Win64, download Win32 version !!)

http://sourceforge.net/projects/win32svn/

Remember in which directory you are installing SubVersion

Installing Subversion Insight

Now we must install the IDE expert, there are several versions. I’am actually using Uwe’s Expert (Version Insight Plus Beta 8), but may be it’s better to use the last version. You can download it here.

http://www.bitcommander.de/blog/index.php/downloads/

Linking the expert to the right DLL

We have destroyed the subversion Dll when we deleted the subversion directory in embarcadero setup folder. We must tell the IDE to watch for the DLL in the updated subversion folder.

Open the registry editor (cmd -> regedit) And go to the key HKEY_CURRENT_USER\Software\Embarcadero\BDS\9.0\Subversion

Create the key Subversion and the Value (string) :

SvnDllDir “D:\Program Files (x86)\Subversion\bin\”

Now restart IDE and test !

As you can see, you will have a new version, updated, corrected ! And Working fine.

I hope it will help some peoples.

Rémi

D:\Program Files (x86)\Embarcadero\RAD Studio\9.0\source\soap\wsdlimporter\MessageDigest_5.pas

Just add this unit to the uses and declare this two functions.

function GetMd5(const Value: AnsiString): string; overload;
var
hash: MessageDigest_5.IMD5;
begin
hash := MessageDigest_5.GetMD5();
hash.Update(Value);
Result := hash.AsString();
end;

function GetMd5(const Value: UnicodeString): string; overload;
var
hash: MessageDigest_5.IMD5;
begin
hash := MessageDigest_5.GetMD5();
hash.Update(Value);
Result := hash.AsString();
end;

That’s all folks !

Introduction

Ce petit article n’a pas la prétention d’être exempt d’erreurs, il est écrit par un physicien audiophile et non un ingénieur du son. Le but de celui-ci est avant tout de vulgariser des concepts qui peuvent sembler obscurs aux néophytes. Vous trouverez des informations bien plus précises sur des sites spécialisés et notamment sur GenerationMp3.

Le problème avec la mesure de la qualité audio d’un appareil, c’est qu’elle est très subjective. Chacun perçoit la musique de manière différente car nous n’avons pas la même éducation musicale, la même oreille et les mêmes attentes en ce qui concerne la musique. Difficile donc de juger si un son est « bon » ou bien s’il est « mauvais » . Parler de “mauvais son” et de “bon son” est un abus de langage, il vaut mieux parler de qualité de la sortie audio, c’est d’ailleurs le sujet de cet article

Pour les appareils électroniques, on considère que le signal n’est globalement pas abimé en étant stocké, ni même décompressé par le processeur (vers 44100Hz, 16Bit, Stereo). Le principal responsable de l’altération du signal est le composant DAC (le convertisseur digital vers analogique) qui contient aussi un amplificateur sur ce type d’appareil.

Actuellement sur les Smartphones haut de gamme le son est de bonne qualité, on comparera le son avec un lecteur MP3 IAudio d’excellente facture : le Cowon IAudio 9.

Fast Track Pro est le système utilisé.

Donc pour juger la qualité d’une sortie audio on cherche à vérifier comment retranscrit le lecteur, un signal que l’on a créé et que l’on connait. Par là j’entends que l’on crée un fichier contenant un signal audio codé en numérique. On lit ce fichier avec le lecteur et en sortie on récupère le signal analogique soit :

• directement avec la prise jack (20000 Ohm)
• avec un casque (ici AKG 32 Ohm) directement avec un microphone de très bonne qualité si l’on veut tenir compte de l’impédance ajoutée par celui-ci.

Les tests suivants ont été réalisés à volume maximum ce qui permet d’accentuer la distorsion que l’appareil inflige au signal. En effet, certains lecteurs détériorent grandement le signal à volume max.

Pour le test, le casque utilisé est de 32 Ohm, l’intensité est plus importante qu’un casque avec une plus haute impédance. L’amplificateur est plus sollicité donc travaille moins bien. De plus, on pousse le son à fond pour avoir une plus grande intensité. Ces tests sont réalisés par des professionnels. Vous trouverez à la fin de cette article les sources. Le logiciel utilisé est RightMark Audio.

En comparant le signal donné et le signal que nous renvoit le casque on peut discuter quantitativement de la qualité d’une sortie audio. Les résultats doivent être reproductibles et comparables sinon cela n’a pas d’intérêt.

La réponse en fréquence

Cette mesure ne permet pas de dire si le son est agréable, mais uniquement si le son qui sort des écouteurs est le son tel qu’il est enregistré sur le fichier audio. Pour comprendre cette partie, il faut savoir ce qu’est un signal audio. Très rapidement, un signal audio est une information provenant d’un émetteur et attendant un récepteur composé d’une multitude de signaux sinusoïdaux purs avec des fréquences différentes.

Rappel sur la fréquence :

Une fonction sinusoïdale est décrite par sa phase ϕ (“décalage par rapport à l’origine“), son amplitude Ĝ et sa fréquence (ici pulsation ω). On peut l’écrire de cette manière.

Ici, ce terme contient toutes les fonctions sinusoïdales, que ce soit un cosinus ou un sinus. Le cosinus étant juste un sinus déphasé. Mais c’est vrai que l’on s’en fiche, continuons…

Voila deux signaux sinusoïdaux mais de fréquences différentes.

Au-dessus fréquence basse (son grave), au-dessous fréquence élevée (son aiguë)

Un signal quelconque peut être décomposé en une somme de signaux sinusoïdaux. Par exemple : ci-dessous avec le signal audio composé en noir qui est en fait la somme pondérée des signaux en vert, rose, bleu, rouge etc… Ainsi notre oreille perçoit le signal comme une somme de signaux sinusoïdaux de fréquences différentes.

Le signal noir est la somme pondérée des autres signaux...

 

Grâce à un outil mathématique appelé “transformée de Fourier” on peut décomposer le signal du dessous en une somme de sinus de fréquences différentes avec une intensité différente. C’est ce qu’on voit au-dessus (à chaque pic correspond une intensité particulière pour une certaine fréquence). Plus le pic est grand plus la fréquence correspondante est “présente”.

Revenons à nos moutons, on cherche à déterminer par rapport à un signal envoyé si toutes les fréquences sont bien restituées et dans les mêmes proportions. Si j’envoie un signal « plat »  et que les basses sont plus intenses que les aiguës c’est que le lecteur ne restitue pas correctement le son. C’est mauvais ou alors un équaliseur altère le signal.

Les limites de perception de l’oreille humaine se situent entre 20Hz et 20Khz. Mais globalement on se fiche de cette bande passante car la plupart des appareils électroniques sont capables de restituer un signal dans cette gamme de fréquence et puis l’oreille humaine ni verra que du feu même si l’on est entre 30 Hz et 19 KHz. Non ce qui nous intéresse c’est si la restitution est « uniforme ».

A propos de l’unité Décibel :

Partout dans le monde, pour mesurer la puissance d’une onde sonore (ou plutôt pour comparer deux puissances) on utilise une unité appelée Décibel. C’est un nom un peu barbare en l’honneur de Mr Bell et inventé par les ingénieurs des laboratoires Bell pour quantifier l’atténuation d’un signal Audio sur une liaison téléphonique. C’est une fonction logarithmique (pourquoi, parce que notre oreille est un récepteur logarithmique !!) de rapport de puissance (ce que l’on envoie par rapport à ce que l’on reçoit). On multiplie enfin par 10 pour avoir une unité plus pratique (d’où le nom déci-bel).

Gain en décibel, permettant de comparer deux puissances P1 et P0

Si la puissance du signal de sortie est égale au signal de puissance de l’entrée, le logarithme vaut 0 (en effet log(1)=0) et donc pas d’atténuation. Si la puissance du signal de sortie est 10 fois plus faible (log(10) = 1) donc on aura une atténuation de 10 dB (-10dB) et s’il est 100 fois plus faible -20dB, 1000 fois -30 dB.

Pour mesurer la réponse en fréquence on envoie donc un signal et on mesure l’atténuation (ou l’amplification) de certaines fréquences. On note [+ x dB, – y dB].

Exemple :

Pour le HTC Sensation, directement sur le jack (en blanc) et avec un casque (en vert)

On s’intéresse d’abord à la courbe blanche. Sur celle-ci nous voyons que la réponse en fréquence est plutôt bonne (attention c’est une échelle logarithmique) entre 40Hz et 15 Khz. +0.05 dB,-0.34dB au bord. Par contre quand on rajoute la résistance du casque c’est un peu moins bon +0.71 dB (pour les basses), -0.15 dB pour les aiguës. Comme on l’a vu c’est normal le courant augmente et l’amplificateur souffre.

Voici l’évolution de la réponse en fréquence pour quelques Smartphones :

Sans casque	Réponse en fréquence (dB)		Étendue
HTC Desire HD	0,09	-0,44	0,53
HTC Sensation XE	0,05	-0,34	0,39
Cowon IAudio 9	0,03	-0,16	0,19
Apple IPhone 4S	0,02	-0,11	0,13
Samsung Galaxy S II	0,04	-0,09	0,13
Apple IPhone 4	0,01	-0,07	0,08
LG Optimus 2X	0,01	-0,03	0,04

Plus l'étendue est faible plus la réponse en fréquence est bonne. Les HTC sont les moins bons ici.

En charge les résultats sont tout de suite différents mais bien plus intéressants :

Avec casque	Réponse en fréquence (dB)		Étendue
Samsung Galaxy S II	1,05	-0,22	1,27
HTC Sensation XE	0,71	-0,15	0,86
HTC Desire HD	0,09	-0,44	0,53
LG Optimus 2X	0,14	-0,04	0,18
Apple IPhone 4S	0,05	-0,1	0,15
Apple IPhone 4	0,01	-0,07	0,08

Le Samsung Galaxy S II est le moins bon. Je suis désolé je n'ai pas de valeur pour le Cowon IAudio 9 avec un casque. Les téléphones d'Apple se comportent très bien !

Le niveau de bruit :

Quand le son sort de l’appareil celui-ci peut être perturbé par des signaux parasites qui peuvent venir par exemple du champ Électromagnétique environnant (le téléphone communique) si le blindage de l’appareil n’est pas terrible, cela peut venir aussi du processeur etc… (Rendez vous ici pour écouter ce bruit sur le Samsung Galaxy S II http://soundcloud.com/anandtech/galaxysii-cpu-edge-noise )
Ici la mesure se fait en dB (A), c’est l’unité retenue pour représenter les niveaux sonores en tenant compte de la sensibilité (selon la fréquence) de l’oreille humaine (l’humain entend moins bien les graves que les aiguës). Alors on fixe comme origine 40 dB au dessus du seuil d’audibilité. C’est à dire qu’à 0 dB(A) on est 40 dB au dessus du seuil où l’on entend plus rien.

On classe ci-dessous  les appareils en fonction de leur niveau de bruit.

Sans casque	Noise Level (dB(A))
Samsung Galaxy S II	-91,4
Apple IPhone 4S	-91,2
HTC Desire HD	-90,6
Cowon IAudio 9	-90,5
HTC Sensation XE	-90,2
Apple IPhone 4	-90,1
LG Optimus 2X	-90,1

Le Samsung Galaxy S II est ici le meilleur dans cette catégorie en tout cas sans charge. C'est à dire sans casque.

Sans casque	Noise Level (dB(A))
HTC Desire HD	-93,2
Apple IPhone 4S	-91,3
Apple IPhone 4	-90,4
Samsung Galaxy S II	-90
LG Optimus 2X	-89,8
HTC Sensation XE	-89,1

Le HTC desire HD est roi. Et le HTC Sensation XE le moins bon.

Je tiens à modérer ces résultats, soyons honnêtes le HTC Sensation XE à un rapport signal bruit de -89 dB ce qui signifie que le bruit est 77 000 fois trop faible pour être entendu par l’être humain. Pour le Desire HD, c’est 200 000 fois…

La gamme dynamique :

C’est la capacité qu’a un appareil à reproduire en même temps un son peu intense et très intense. Pour éviter la triche, on mesure uniquement les signaux qui ne subissent pas de distorsion (grossièrement de déformation). Par exemple si un appareil est capable de produire des sons pour une fréquence donnée de 9 dB(A) à 1 dB(A), la gamme dynamique vaut 8 dB(A). Plus cette gamme (dynamic range) est grande et mieux c’est !

Nom	Dynamic Range (dB(A))
HTC Desire HD (Casque)	92,90
Samsung Galaxy S II	91,90
Apple iPhone 4S (Casque)	91,30
Apple iPhone 4S	91,20
Cowon Iaudio 9	90,50
Apple iPhone 4 (Casque)	90,40
HTC Desire HD	90,40
Samsung Galaxy S II (Casque)	90,20
HTC Sensation	90,20
HTC Sensation (Casque)	90,10
LG Optimus 2X	90,10
Apple iPhone 4	90,00
LG Optimus 2X (Casque)	89,90

Avec un casque le HTC Desire HD est encore une fois le meilleur suivi des IPhone et du Samsung. Le HTC Sensation semble à la traine...

Le taux de distorsion harmonique :

La distorsion harmonique, notée THD est une spécificité des amplificateurs (ou préamplificateurs). Comme nous l’avons vu tout à l’heure on peut décomposer n’importe quel signal audio sous forme de signaux sinusoïdaux. Le signal prépondérant est le fondamental (ce signal donne la hauteur de la note), les autres les harmoniques (elles donnent le timbre, la note LA du piano ne s’entend pas comme le LA d’une clarinette). En fait plus la quantité d’harmoniques est grande plus le signal est précis :

Plus le nombre d'harmoniques augmente plus le signal reconstitué est proche du signal carré.

Pour conclure le taux de distorsion harmonique est le résultat d’un calcul mathématique ayant pour but de comparer le signal de sortie (ce qui sort du jack) et le signal d’entrée (le fichier audio). Plus ce taux est important plus la différence est importante et donc plus l’amplificateur est médiocre.

Nom	THD (%)
Apple iPhone 4S	0,002
Apple iPhone 4 (Casque)	0,0036
Samsung Galaxy S II	0,0042
Cowon Iaudio 9	0,0048
Apple iPhone 4S (Casque)	0,0068
Apple iPhone 4	0,0068
LG Optimus 2X (Casque)	0,0098
LG Optimus 2X	0,011
HTC Sensation	0,012
Samsung Galaxy S II (Casque)	0,013
HTC Desire HD	0,014
HTC Sensation (Casque)	0,019
HTC Desire HD (Casque)	0,02

 

On remarque que cette fois ci le Desire HD est en retrait en ayant le plus haut THD. Le HTC Sensation ne brille toujours pas. Par contre les IPhones sont vraiment bons.

Distorsion d’intermodulation + bruit :

C’est un phénomène complexe qui est la conséquence de la non linéarité du DAC. Si on a un signal avec deux fréquences différentes en entrée nous n’obtenons pas deux fréquences en sortie mais une multitude de signaux. Au premier ordre on voit bien ci-dessous deux pics secondaires en plus des deux pics de base ) gauche et à droite.

C’est ce phénomène qui est mesuré par l’IMD. Plus ce nombre est faible moins la distorsion est importante, mieux c’est.

Nom	IMD (%)
Cowon Iaudio 9	0,0094
Apple iPhone 4S	0,012
Apple iPhone 4	0,012
LG Optimus 2X	0,016
HTC Sensation	0,021
Samsung Galaxy S II	0,066
Apple iPhone 4S (Casque)	0,071
Apple iPhone 4 (Casque)	0,092
LG Optimus 2X (Casque)	0,111
HTC Desire HD	0,517
HTC Sensation (Casque)	0,522
Samsung Galaxy S II (Casque)	0,647
HTC Desire HD (Casque)	0,728

Le HTC Desire HD a encore de grandes difficultés ici. Le Samsung Galaxy S II galère aussi (c'est relatif). L'IPhone 4 est encore une fois très très bon.

Conclusion

Pour finir comparons deux smartphones haut de gamme avec trois appareils (sans casque) :

• La Nintendo DS Lite réputée pour avoir un son très mauvais.
• Le lecteur Mini Disc Sony MZ-R3 représentant le haut de gamme… Il y a 15 ans.
• Le Cowon IAudio 9, un excellent lecteur contemporain.

	Etendue réponse en Fréquence (dB)	Noise level (dB(A))	Dynamic Range (dB(A))	THD (%)	IMD + Noise (%)	Stereo CrossTalk (dB)
Sensation	0,39	-90,2	90,2	0,012	0,021	-91,1
IPhone 4S	0,13	-91,2	91,2	0,002	0,012	-93
Nintendo DS Lite	8,78	-66	64,5	1,8	3,836	-69,1
Mini Disc Sony MZ-R3	1	-86	86,1	1,658	2,128	-67,1
Cowon Iaudio 9	0,12	-79	79	0,0058	0,032	-79,4

Comparaison de deux smartphones avec trois autres appareils. Les unités sont modifiées pour être représentées sur le même graphique.

On voit sur ce graphique que relativement à la DS et au MiniDisc, les smartphones et le lecteur MP3 sont relativement proches. Globalement la qualité audio est là et je doute que l’oreille humaine avec un casque à moins de 500 € puisse y voir quelque chose. Ce n’est pas avec les écouteurs Beats de Dr. Dre que l’on verra une différence flagrante.

On a vu que la qualité Audio évolue avec l’impédance du casque. Plus l’impédance est faible, plus l’ampli abime le signal.

Comme je l’expliquais en introduction, la qualité audio dépend beaucoup de chacun et l’objectif principal est de se faire plaisir. Ce matériel n’est de toute manière pas adapté aux professionnels et il n’a même pas été conçu pour ça. Vous pouvez adapter le signal à vos goûts : si vous aimez les basses vous pouvez régler l’équaliseur en conséquence (c’est d’ailleurs ce que fait la technologie Beats de HTC) ou acheter des écouteurs favorisant les basses.

La qualité audio dépend aussi de beaucoup d’autres éléments que nous n’avons pas pris en compte, par exemple :

• Écoutez vous la musique dans un endroit bruyant ? Si vous êtes dans le métro, mais avec un casque très isolant, le bruit extérieur sera audible. Le Noise Level avec ses -80 dB(A) semble ridicule à côté…
• Que vaut votre casque ? Si votre casque force sur les basses, la réponse en fréquence sera totalement différente…
• Quelle est la qualité de vos fichiers musicaux ? Peut être écoutez vous du streaming ? La compression est souvent destructrice (lossy).
• Avez vous une très bonne oreille ? Plus on vieillit, malheureusement, plus notre oreille perd en sensibilité. C’est un fait…
• etc…

L’autre question à se poser est : êtes vous un puriste ?

• Avez vous un casque valant plusieurs centaines d’euros ou des intras à 500 € et un MP3 d’une très grand marque (souvent cher et moche ‘Je rigole’) ?
• Écoutez vous constamment de la musique compressée en FLAC (lossless) et avez vous mis tout vos MP3 (lossy) à la corbeille ?

Peut être que la qualité audio n’est pas l’élément principal à prendre en compte lors de l’achat de votre smartphone vu le peu de différences entre-eux. En tout cas cela ne semble pas être une question prépondérante lors de l’achat d’un téléphone.

Sources :

GSMArena

About Stereos

Wikipedia

Engadget

ElectroKrishna

ArnandTech

Remarques :

Si vous avez des remarques n’hésitez pas, je suis toujours à l’écoute. Je suis audiophile mais pas professionnel, les informations présentes ici sont donc à remettre dans leur contexte.

Rémi MEVAERE

First Part DVCLAL and licensing information

Yesterday I was asking me a question. What information could we extract from a Delphi executable about the compiler, the license and all these things?

First thing I done was just compiling a simple application form (Delphi XE) and watch if there is something in it.

I have three Executable:

1. With a valid license
2. With the same valid license
3. With another valid license from a friend
4. Without license

MD5

1. aa937b519d3dc7748658339d74beab71
2. 3a052680d1baa16b53a7376e94d88bb6
3. eb66631ce3aa2ab2bfeb27779164dfa1
4. 35f29fbcbf468dc1a683f742893d54b1

The files are different, even the first and second (which are compiled with the same license in less than 2 minutes). Something is added in the file, like a date or a time.

DVCLAL – Resource Name for RC_DATA

1. 000DEF00  26 3D 4F 38 C2 82 37 B8 F3 24 42 03 17 9B 3A      &=O8‚7¸ó$B••›:
2. 000DEF00  26 3D 4F 38 C2 82 37 B8 F3 24 42 03 17 9B 3A      &=O8‚7¸ó$B••›:
3. 000DEF00  26 3D 4F 38 C2 82 37 B8 F3 24 42 03 17 9B 3A      &=O8‚7¸ó$B••›:
4. 000DEF00  26 3D 4F 38 C2 82 37 B8 F3 24 42 03 17 9B 3A      &=O8‚7¸ó$B••›:

DVCLAL (Delphi Visual Component Library Access License) are the same for the three files, this is pretty strange.

To detect the change between file I am using the command line tool “compare” included in Windows. So as you can see the differences between file are exactly at the same offset and are equal. It is unbelievable to store huge license information in 16 bytes (word) or 32 bytes (dword).

In green this is the beginning of the executable (low offset). In MSDN documentation you can find info about PE (Portable Header which is the structure of executable files).

If we open it in Hex Edit.

The PE chars follow by two null values are signature of the beginning of the executable. After that we have IMAGE_FILE_HEADER.

Syntax

typedef struct _IMAGE_FILE_HEADER {

WORD  Machine;

WORD  NumberOfSections;

DWORD TimeDateStamp;

DWORD PointerToSymbolTable;

DWORD NumberOfSymbols;

WORD  SizeOfOptionalHeader;

WORD  Characteristics;

} IMAGE_FILE_HEADER, *PIMAGE_FILE_HEADER;

We have in HexEdit the first word which is 4C01, and the second one NumberOfSections 0A00. The DatetimeStamp is 14DEE84D. Clearly it’s the time information of the build.

 

TimeDateStamp

The low 32 bits of the time stamp of the image. This represents the date and time the image was created by the linker. The value is represented in the number of seconds elapsed since midnight (00:00:00), January 1, 1970, Universal Coordinated Time, according to the system clock.

So let’s return to DVCLAL, and see when it is used by Delphi. So I search the string DVCLAL in Embarcadero folder. And the only file which is return is Sysutils.pas. (For copyright reasons I can’t share the code of the function in Delphi main pascal files)

The ALR function returns a pointer handle that can be used to obtain a pointer to the first byte of the specified resource in memory. Here the string DVCLAL.
The GDAL function is testing the value of the DVCLAL and if there is a problem, the exe raise an exception.

The RPR function is testing the validity of DVCLAL and if there is a problem, raises an exception.

I don’t know if RPR is used in the last version of Delphi but in older version, when the exe was loading module he was launching the procedure RPR.

So in conclusion, just understand that DVCLAL is one way to detect Delphi app, but it is not secure, you could easily delete this value and nothing will appear.

Manifest file attached to the executable and PackageInfo

In the RC_DATA resource of Delphi executable you could find a Resource named PackageInfo. You will find more information in sysutils.pas. (Function GetPackageInfo)

A variable of type PackageInfoTable provides information about initializing or finalizing a series of package units.

The manifest file is in the resource type RC_Manifest with the name 1036 could help you to detect if the compiler is Delphi. (CodeGear Rad Studio in Assembly Name)

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <assemblyIdentity
    type="win32"
    name="CodeGear RAD Studio"
    version="15.0.3953.35171"
    processorArchitecture="*"/>
  <dependency>
    <dependentAssembly>
      <assemblyIdentity
        type="win32"
        name="Microsoft.Windows.Common-Controls"
        version="6.0.0.0"
        publicKeyToken="6595b64144ccf1df"
        language="*"
        processorArchitecture="*"/>
    </dependentAssembly>
  </dependency>
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel
          level="asInvoker"
          uiAccess="false"/>
        </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>
 

So I hope it will help you if you need to detect Delphi application. But the Application could be crypt, the resource could be easily modified and the DVCLAL deleted.

Have a nice day

I would like to show you how to use it in Delphi.

First Step : Listing all the resources

How to open an executable file ?

LoadLibraryEx is described on this page of MSDN

var
hinstance: HMODULE;
begin
hinstance := LoadLibraryEx(PChar('c:\the_file.exe'), 0, LOAD_LIBRARY_AS_DATAFILE);

//HERE code with hinstance

FreeLibrary(hinstance);

To list all the resources we will use the EnumResourceTypes (function also described in MSDN) which is calling the function CallbackEnumResTypes.

EnumResourceTypes Function

Enumerates resource types within a binary module.

Syntax

BOOL WINAPI EnumResourceTypes(
  __in_opt  HMODULE hModule,
  __in      ENUMRESTYPEPROC lpEnumFunc,
  __in      LONG_PTR lParam
);

Parameters

hModule [in, optional]

Type: HMODULE 

lpEnumFunc [in]

Type: ENUMRESTYPEPROCA pointer to the callback function to be called for each enumerated resource type. For more information, see the EnumResTypeProc function.

lParam [in]

Type: LONG_PTRAn application-defined value passed to the callback function.

Return Value

Type: BOOL

Returns TRUE if successful; otherwise, FALSE. To get extended error information, call GetLastError.

Remarks

For each resource type found, EnumResourceTypes calls an application-defined callback function lpEnumFunc, passing each resource type it finds, as well as the various other parameters that were passed to EnumResourceTypes.

 EnumResourceTypes(hinstance, @CallbackEnumResTypes, Integer(ListBox1.Items));

//The first parameter is the Hinstance of the Executable, the second one is pointing on a function which will received the result of EnumResourceTypes and the last one is what you want !! Here a pointer to Listbox1.Items 

The ResType parameter is described by MSDN

Type: LPTSTR

The type of resource for which the type is being enumerated. Alternately, rather than a pointer, this parameter can be MAKEINTRESOURCE(ID), where ID is the integer identifier of the given resource type. For standard resource types, see Resource Types. For more information, see the Remarks section below.

The return value is the specified value in the low-order word and zero in the high-order word.

What is stdcall ?  I have forgotten !

When you declare a procedure or function, you can specify a calling convention using one of the directives register, pascal, cdecl, stdcall, and safecall. Calling conventions determine the order in which parameters are passed to the routine. They also affect the removal of parameters from the stack, the use of registers for passing parameters, and error and exception handling. The default calling convention is register.

• register Left-to-right Routine Yes
• pascal Left-to-right Routine No
• cdecl Right-to-left Caller No
• stdcall Right-to-left Routine No
• safecall Right-to-left Routine No

function CallbackEnumResTypes(HInstance: HMODULE; ResType: PChar; OutList: TStrings): Integer; stdcall;
begin

if HiWord(Cardinal(ResType)) <> 0 then
OutList.Add(ResType) // The HighWord <> 0 This is strange MSDN explain us that hi-order word must be zero
else
OutList.Add(Format('Resource Number %d: Description %s', [loword(Cardinal(ResType)), StockResourceType(ResType)]));

EnumResourceNames(HInstance, ResType, @enumResNamesProc, Integer(OutList));  // Enum all the Resources

Result := 1;   // Continue The enumeration
end;

So we have used a function name StockResourceType wich are giving us a String describing the Type of the Resource (All the information on this page)

Function StockResourceType(ResType: PChar): string;
const
ResTypeNames: Array [1 .. 24] of String = ('RT_CURSOR',
'RT_BITMAP',
'RT_ICON',
'RT_MENU',
'RT_DIALOG',
'RT_STRING',
'RT_FONTDIR',
'RT_FONT',
'RT_ACCELERATOR',
'RT_RCDATA',
'RT_MESSAGETABLE',
'RT_GROUP_CURSOR',
'UNKNOWN',
'RT_GROUP_ICON',
'UNKNOWN',
'RT_VERSION',
'RT_DLGINCLUDE',
'UNKNOWN', 'RT_PLUGPLAY',
'RT_VXD',
'RT_ANICURSOR',
'RT_ANIICON',
'RT_HTML',
'RT_MANIFEST'
);
var
ResID: Cardinal absolute ResType;
begin
if ResID in [1 .. 24] then
Result := ResTypeNames[ResID]
else
Result := 'UNKNOWN';
end;

What is absolute directive ?  I have forgotten !

You can create a new variable that resides at the same address as another variable. To do so, put the directive absolute after the type name in the declaration of the new variable, followed by the name of an existing (previously declared) variable. We can here use Restype which is a Pchar in a particular address in a ResId function which is a Cardinal.

For the Callback function EnumResourceNames, this is the same thing.

BOOL CALLBACK EnumResNameProc(
  __in_opt  HMODULE hModule,
  __in      LPCTSTR lpszType,
  __in      LPTSTR lpszName,
  __in      LONG_PTR lParam
);

Parameters

lpszType [in]

Type: LPCTSTR

The type of resource for which the name is being enumerated. Alternately, rather than a pointer, this parameter can be MAKEINTRESOURCE(ID), where ID is an integer value representing a predefined resource type. For standard resource types, see Resource Types. For more information, see the Remarks section below.

lpszName [in]

Type: LPTSTR

The name of a resource of the type being enumerated. Alternately, rather than a pointer, this parameter can be MAKEINTRESOURCE(ID), where ID is the integer identifier of the resource. For more information, see the Remarks section below.

function EnumResNamesProc(module: HMODULE; ResType, ResName: PChar; list: TStrings): Integer; stdcall;
begin
if HiWord(Cardinal(ResName)) <> 0 then
list.Add('  ' + ResName)
else
list.Add(Format('  #%d', [loword(Cardinal(ResName))]));
Result := 1; // Continue !
end;

Second Step : Adding, Editing, Deleting resources

UpdateResource Function

Adds, deletes, or replaces a resource in a portable executable (PE) file. There are some restrictions on resource updates in files that contain Resource Configuration (RC Config) data: language-neutral (LN) files and language-specific resource (.mui) files.

Syntax

BOOL WINAPI UpdateResource(
  __in      HANDLE hUpdate,
  __in      LPCTSTR lpType,
  __in      LPCTSTR lpName,
  __in      WORD wLanguage,
  __in_opt  LPVOID lpData,
  __in      DWORD cbData
);

Parameters

hUpdate [in]

Type: HANDLEA module handle returned by the BeginUpdateResource function, referencing the file to be updated.

lpType [in]

Type: LPCTSTRThe resource type to be updated. Alternatively, rather than a pointer, this parameter can be MAKEINTRESOURCE(ID), where ID is an integer value representing a predefined resource type. If the first character of the string is a pound sign (#), then the remaining characters represent a decimal number that specifies the integer identifier of the resource type. For example, the string “#258″ represents the identifier 258.

For a list of predefined resource types, see Resource Types.

lpName [in]

Type: LPCTSTRThe name of the resource to be updated. Alternatively, rather than a pointer, this parameter can be MAKEINTRESOURCE(ID), where ID is a resource ID. When creating a new resource do not use a string that begins with a ‘#’ character for this parameter.

wLanguage [in]

Type: WORDThe language identifier of the resource to be updated. For a list of the primary language identifiers and sublanguage identifiers that make up a language identifier, see the MAKELANGID macro.

lpData [in, optional]

Type: LPVOIDThe resource data to be inserted into the file indicated by hUpdate. If the resource is one of the predefined types, the data must be valid and properly aligned. Note that this is the raw binary data to be stored in the file indicated by hUpdate, not the data provided by LoadIcon, LoadString, or other resource-specific load functions. All data containing strings or text must be in Unicode format. lpData must not point to ANSI data.

If lpData is NULL and cbData is 0, the specified resource is deleted from the file indicated by hUpdate.

cbData [in]

Type: DWORDThe size, in bytes, of the resource data at lpData.

Return Value

Type: BOOL

Returns TRUE if successful or FALSE otherwise. To get extended error information, call GetLastError.

Adding

var
FileHandle: THandle;
Filebuffer: ShortString;
Test: PChar;

Filebuffer := 'Something to add this is a string ! Not Unicode here   ! ';
FileHandle := BeginUpdateReSource(PChar('c:\the_exe.exe'), False); // begin updating our resource
UpdateReSource(FileHandle, RT_RCDATA, 'THE_NAME_OF_THE_RESOURCE', 0, @Filebuffer[1], Length(Filebuffer));  // Updating the resource
EndUpdateReSource(FileHandle, False); // End of the update

Editing

UpdateReSource(FileHandle, RT_RCDATA, 'EXIST_NAME', 0, @Filebuffer[1], Length(Filebuffer));  // Updating the resource, the EXIST_NAME resource exist !

Removing

Filebuffer := ''; // To delete just create something empty or clear !
UpdateReSource(FileHandle, RT_RCDATA, 'EXIST_NAME', 0, @Filebuffer[1], Length(Filebuffer));  // Updating the resource, the EXIST_NAME resource exist !

Third Step : And for a bitmap ?

This is a small piece of code which will give you an example of how to add a bitmap in resource… After that you will now how to add Cursor, Song etc…

var
HInstance: THandle;
bitmap: Pointer;
FS: TFILESTREAM;
dwSize: DWORD;
begin
HInstance:= BeginUpdateResource(THE_EXECUTABLE_PATH, false);

FS := TFileStream.Create(THE_BITMAP_PATH, fmOpenRead or fmShareDenyWrite); // Opening a TFileStream
GetMem(bitmap, FS.Size + 1); // Get memory to add the Bitmap in memory
FS.ReadBuffer(bitmap^, FS.Size); // Full this part of the Memory with Bitmap DATA
dwSize := FS.Size; // Size of the Bitmap
FS.Free; // Closing the TFileStream

UpdateResource(HInstance, PWideChar(RT_BITMAP), '6805'  , LANG_SYSTEM_DEFAULT, bitmap, dwSize); // 6805 is the name, and the language is the default of my system

EndUpdateResourceW(HInstance, false);
end;

I hope it will help you to use Resources.

Have a good week,

I would like to share my experience about this program of distributed computing. First I have one powerful computer (Quad Core CPU and 2 GPU) and one server (okay it’is not a powerfull one, but it is enough for me and my several websites).

New software of Folding@Home V7

When I am coding, I am using a small part of the power of my system and my server is not overload . So my computers could be useful to help science and research like all the servers of Google which are also supporting this project ! In only two months, I am  in the top five percent position. Let’s see the graph.

My rank in Folding@Home

Actually I am student and I can’t give money to charity association, and I don’t like this, I think this is the job of government. But I prefer being active on a global and worldwide project with a lot of peoples (1552132 peoples at this time, number of registration). This is, in my opinion, a form of donation !

Like me you could be a part of this adventure, don’t wait just click here !

In the uses dont forget to add the IDPop3 file which contains all the information for TIDPop3.

uses
Idpop3;
type
POP3Client: TIdPOP3;

The first thing I do is write a procedure to retrieve the status from the TIDPop3 :

procedure Thread_POP3.POP3Status(ASender: TObject; const AStatus: TIdStatus; const AStatusText: string);
begin
Synchronize
( procedure begin
// USE AStatusText
end);
end;

// After the creation of POP3Client we can assign this event
POP3Client          := TIdPOP3.Create(nil);
POP3Client.OnStatus := POP3Status;

To connect to the server just use the procedure Connect, lets see other methods :

POP3Client.Connect; // Connection
POP3Client.login; // Use it to Connect

If you want to get the number of mails just use the function CheckMessages, and to get the mail the mail number I RetrieveMsgSize(I) :

FNbrMailsOnline := POP3Client.CheckMessages; // Retrieve the number of mails on the server
FTailleDernierMail := POP3Client.RetrieveMsgSize(FNbrMailsOnline); // Retrieve the size of the Last Mail

To delete a mail just do this :

POP3Client.Delete(I); // The mail will only be delete when you will disconnect
// If you want to cancel the deletion just use the
POP3Client.Reset; // Cancel the deletion

Now let’s see how to retrieve mails :

Tell Delphi where to find the TIDMessage class

uses
IDMessage;
type
Message: TIDMessage;

If you want to retrieve only the header of a mail (not the all mail, just the basics information) :

POP3Client.RetrieveHeader(Position_Mail, Message); // Retrieve only the header
POP3Client.Retrieve(Position_Mail, Message); // Retrieve the all mail

To retrieve a Raw Mail (the text without processing the mail in TIDMessage MIME parser) :

POP3Client.RetrieveRaw(Position_Mail, Down_MemStream);

And in conclusion, disconnection :

POP3Client.Disconnect; // Disconnection

Bye,

Is this tool in Rad Studio IDE?

When you are developing software and you want to build a solid code like a rock. You need some tools to give you “Metrics”. Metrics give you answers to the following questions:

• How much files in your project? How much modules, lines, constants, class, variables?
• Give you information about complexity of your code. How much Comments/Total lines in your code? What is the complexity of functions or procedures? About objects programming: What is the complexity of methods per class, the number of children and lot of other things?

To introduce the tool, let’s see what Delphi IDE offer in the feature Matrix :

As you can see, this is not cool for the professional Delphi customers. Ok I think these functions are totally essential when you are developing software in a Team or when you are project manager. But this is also cool when you are independent developer and you want to keep a watch on the quality of the code. I hate Embarcadero for this; they are giving you ersatz of softwares, ersatz of Intraweb, AQTime, FinalBuilder… Why they aren’t reduce the price of Delphi and give a total liberty for their users to buy the tools they need… I hate this! Haaaaaa! So what is the solution for analyzing our code? Buying an extension of Delphi for 1300 €! Not sure, you could get really more in buying Peganza Analyser for only 120 € (see coupon at the end). But this is not the exact same software! Peganza Pascal Analyser is far more complete than Delphi IDE cause it don’t give only metrics it gives you a lot of other things. The goal is not the same, so now I will stop to compare original tool include in Delphi and Peganza Analyser.

Review and tutorial of Peganza Pascal Analyser 5 :

To introduce and review this tool I will use the example of my software. After having setup my project and click Analysis-> Run!

Reports – General

Status: This report presents important facts about the current analysis, e.g. selected compiler directives and search paths.

Strong Warning: In this report you will see severe errors; they will often cause failures or erroneous results. (Property access in read/write methods or Ambiguous unit references). Sorry I haven’t this kind of problem in my software (It’s pretty good news), so no example. But sometimes it could happen if you are a bit dizzy !

Warning reports: It will give you some advises to improve your code:

Interfaced identifiers that are used, but not outside of unit (3, was 0):

TMailIMAPAccount = Class Type, Interfaced obj_mailaccount (98)

If I double click on the line, it opens me Delphi IDE and I see directly what the problem is.

// -----------------------

// TMailAccount  IMAP4

// -----------------------

TMailIMAPAccount = class(TMailAccount)

private

public

procedure Assign(Source: TObject); override;

end;

I don’t use this Class, but I wrote it to be use in a near future. So it’s a false positive ! When you have false positive you could delete them in adding

 //PALOFF 

Interfaced class identifiers that are public/published, but not used outside of unit (5, was 5):

————————————————————————————————

Colonnes : Array (static)      Property                listview_tools\TList_Colonne (61)

// Liste Colonne

TList_Colonne = class(TObjectList)

private

function GetColonne(Index: Integer): TColonne;

procedure SetColonne(Index: Integer; const Value: TColonne);

public

function NewOnlineColonne(TypeC: TColumnOnline; Position: Integer; Visible: Boolean; Size: Integer): TColonne_Online;

property Colonnes[index: integer]: TColonne read GetColonne write SetColonne; // PROBLEM HERE, the Class is public but not used...

end;

The problem is very simple to correct, the visibility of the property Colonnes is too high. The best way to correct it is to transfer it in private section.

Variables that are set, but never referenced (9, was 9):

—————————————————————————-

con_sasl_encours : tidsasl     ClassField              Thread_POP\Thread_POP3 (89)

Thread_POP3 = class(tthread)

private

FProcessName: string;

con_sasl_encours:   tidsasl; // What is the problem...

// FThread origine

FThread_IM: TIMThread;

//...

protected

// ...

public

// ...

end;

If I delete the con_sasl_encours, the program can’t compile. The only time con_sasl_encours is used it is for :

con_sasl_encours   := nil; 

So this object is totally useless, I can delete it. As you can see Peganza Analyser could help me to delete some objects totally useless. Maybe when I code it I had something in mind, but now, I dont know what it was… On my 22467 lines of code it is hard to find. Pascal Analyser could help you to clean your code.

Another one :

Variables that are set, but never referenced (8, was 9):

—————————————————————————-

Created : TDateTime            Var, Local              database_running\TDBB_RUN\Load_Main_Database (111)

 function TDBB_RUN.Load_Main_Database(const Path_BDD: String; const Ident: String): boolean;

var

Created: TDateTime;

begin

Created    := sqlite3_column_double(Stmt, 1);

//....

Created is a double that is never used ! It is set but never used. So I could delete it (or not if it is planned to be used in the future but this is not probable, I can’t remember a variable that is declared two years ago lool) !

I will not give you an example for ALL the reports in the Warning reports. But we have seen that this tab could really help use to find useless code, or strange code. Sometimes we do some very strange thing like:

for-loop variables read after loop (1, was 1):

—————————————————————————-

I : Integer                    Var, Local              Thread_POP\Thread_POP3\Execute\delete_mails (991)

try

for I := 0 to Liste_de_Mail.Count - 1 do

begin

// blablablblalaalal

end;

except

// Using of I

end;

This is an error from me, I was maybe drunk… The try except must be inside the loop and must be abort. So the code must be correct in :

for I := 0 to Liste_de_Mail.Count - 1 do

try

begin

// blablablblalaalal

except

Abort;

// Using of I

end;

end;

And the last one I would like to show you :

Functions called as procedures (37, was 37):

—————————————————————————-

configuration.sauvegarder_config at frm_principale (199)

procedure Tfrm_main.FormDestroy(Sender: TObject);

begin

sauvegarder_config;

// ....

end;

// The function

function sauvegarder_config: boolean;

begin

// ....

end;

As you can see, Pascal Analyser gives us a good way to find which part of the software is missing. When I developed Sauvegarder_Config it was designed to give true if the function works properly and false if there is a problem. So it’s totally useless to code a function if I don’t use the result and use it like a Procedure. Here PA could really improves my software if I use it correctly, I’m forced to consider the result of the function.

Optimization: By example the compiler of Delphi is optimized to work differently with constants and variables. So if you need speed and you are using variable for data which will not be modified it’s highly recommended to use constant instead. There are some other tricks to speed up your software. Pascal Analyser will help you to fix some leaks. Let’s see some examples:

Missing “const” for unmodified string parameter (3, was 3):

—————————————————————————-

BDD_Pass : String              ValParam                Thread_POP\Thread_POP3\Execute\Retrieve_Mails (594)

 // Procedure pour télécharger des mails

procedure Retrieve_Mails(BDD_Path: String; BDD_Pass: String);

var 

Here it’s not a variable that I would communicate to the function but a constant. This value will not be modified.

Array properties that are referenced/set within methods (1, was 0):

—————————————————————————-

Accounts : Array (static)      Property                obj_mailaccount\TList_MailAccount (123)

Referenced/set (1):

Assign                         Proc, Method            obj_mailaccount\TList_MailAccount (121)

For performance reasons it is faster to directly access the private array field. However, if the Get- or Set-method performs side effects, it makes sense to access the property.

// -----------------------

// TList_MailAccount

// -----------------------

TList_MailAccount = class(TObjectList)

private

function GetAccount(Index: integer): TMailAccount;

procedure SetAccount(Index: integer; const Value: TMailAccount);

public

procedure Assign(Source: TObject);

function NewPOPAccount: TMailPOPAccount;

property Accounts[index: integer]: TMailAccount read GetAccount write SetAccount;

end;

// Here Assign details

procedure TList_MailAccount.Assign(Source: TObject);

var //...

begin

//...

POPA.Assign(From.Accounts[I]); // THe problem is here

//...

end;

Must be change to

POPA.Assign(TMailPOPAccount(From.Items[I]));

And for the last example :

Local subprograms with references to outer local variables (6, was 6):

—————————————————————————-

GetIndex                       Proc, Local             frmpnl_show_offline_mail_\Tfrmpnl_show_offline_mail\offline_gridGetDisplText (368)

procedure Tfrmpnl_show_offline_mail.offline_gridGetDisplText(Sender: TObject; ACol, ARow: Integer; var Value: string);

var

Mail_Offline: TMail_Offline;

Index:        Integer;

procedure GetIndex;

begin

Index        := strtoint(offline_grid.AllCells[1, ARow]);

Mail_Offline := TMail_Offline(Data_Liste.Objets[Index].Data);

end;

Using some local variables in inner routines cost a bit CPU cause the compiler need to do special stacks manipulation.

I change it in :

procedure Tfrmpnl_show_offline_mail.offline_gridGetDisplText(Sender: TObject; ACol, ARow: Integer; var Value: string);

var

Mail_Offline: TMail_Offline;

procedure GetIndex(Mail: TMail_Offline);

var Index:Integer;

begin

Index        := strtoint(offline_grid.AllCells[1, ARow]);

Mail := TMail_Offline(Data_Liste.Objets[Index].Data);

end;

I’m not an expert on this subject, I hope this is not totally stupid. If someone could tell me if the solution is correct…

Memory:

It allows you to manage all the objects you are creating in the memory; Pascal Analyser could make some test. Like telling you if you are making unprotected calls to free (Use Finally end) on local or non-local object. It will also count number of Create and Free and tell you if there is something strange…

It’s you work to interpret all the reports

Code Reduction:

This report pinpoints unnecessary code that could be deleted, resulting in a smaller amount of code to maintain and search for errors.

Convention Compliance/Inconsistent Case/Prefix:

When you are coding in Delphi, there is some convention (not exhaustive):

• Like user-define type names start with the letter T (TForm_Tool), pointer by P, Exception by E…
• Classfields must be declared in private section.
• Get, Set exposed by properties (write/read).
• Unsuitable names, numerals etc.
• Not the same name for different identifiers.
• Not too much long identifiers.

Pascal Analyser gives you two other report one for inconsistent case (in fact when you are writing Buffer and bUFfer it is the same identifiers but it is most hard to read!). You could also detect which objects have not the right prefix.

Reports – Metrics

The next report is dedicated to Metrics. We have talk about this in the first part of this review/tutorial. The total metrics give you a rapid count of files, modules, lines and all kind of identifiers in Total/Local/Global/Interfaced/Unused. You could have this information for each module.

Extract from the manual:

1. Start with a value of 1 for the normal flow through a subprogram.
2. Add 1 for each of these keywords: IF, WHILE, REPEAT, FOR, AND, OR, XOR, GOTO. Note that PAL always counts AND, OR, XOR, even if they are used as arithmetic operators in the actual code.
3. Add 1 for each case label in a CASE statement. When the CASE does not have an ELSE, add 1 more.

DP (Decision Point equivalent to McCabe’s metric) is a way to quantify the hardness to understand a function. If the subprogram or module has a DP > 10 it is a kind complex subprogram, with PA you could see easily what are the most hardcore to understand function. But sometimes you need to work with long function, which will give you a high DP. You can consider the result with DP/LOC (Lines of Code), if the DP/LOC is too high it is not good. After you need to see if the function is commented enough (if you have a high DP/LOC but a high Cmt(Comment)/LOC this is not a real problem, cause you are documenting enough your function (this is a subjective view).

There is a lot of other statistics with metrics. The metrics here are not a lot, but enough to understand your program if you are self-developer.

Let’s compare with Delphi Metrics  :

This is really more complex and complete, I think this is not totally useful when your are independent developer. But if you are directing a project you will need more information, and this tool is great. But like every tool there are some limitations, by example in this particular situation Delphi Audits tell me that this code is never execute ! But this is an error, this code is always performed ! Sometimes just rewriting differently the code correct the problem.

Synchronize( procedure begin

// ...

end);

Personally I prefer Pascal Analyser. It’s more easy to find problem and to optimize my code. Pascal Analyser gives you also Object Oriented Metrics :

• Weighted Methods per Class (WMC)
• Depth of Inheritance Tree (DIT)
• Number of children (NOC)
• Coupling between Object Classes (CBO)
• Response for a Class (RFC)
• Loack of Cohesion in Methods (LCOM)

With all these metrics, without directly watching the code, you could know if your code is great, just ok or really bad ! Just test the software and open the manual to learn more about these metrics.

And a lot of other tools !

Pascal Analyser comes with a lot of other tools. It could give you some infos about Modules, Identifiers, Duplicate Identifiers name (yes it’s not good to give the same name to different variables, most hard to read), similarity. This software could also list :

• The Subprogram Index
• Bindings
• Third-party dependencies
• Most called subprograms
• Call Tree/ Reverse Call Tree/ Call Index
• All the exceptions
• All the todos
• All the directives
• All the conditional Symbols
• The Brief Cross-reference
• Interfaced identifiers that are used outside their units
• And lof of other things !

Just before conclusion, I will give a last function that I like a lot on this Analyser. In pascal you need to tell the compiler which files you want to include into your program with the uses, but sometimes you have some useless units in uses and it takes time to compiler to test if it useful or not. Here PA tells me directly which units I could delete easily. Example :

Program ClientMail uses:

Used units:

sysutils in implementation

==> ExceptionLog unnecessary

Forms in implementation

dateutils in implementation

frm_principale in implementation

==> memstreamini unnecessary

==> database unnecessary (has initialization)

==> ressourcestrings unnecessary (used by unit with init)

==> imail_type unnecessary

==> obj_mailaccount unnecessary

==> database_online unnecessary

==> chemins unnecessary

==> tools_strings unnecessary

==> constantes unnecessary

==> msgbox_tools unnecessary

==> database_cfg unnecessary

==> listview_tools unnecessary

==> configuration unnecessary

frm_configuration in implementation

==> Thread_Manager unnecessary

==> database_mails unnecessary

==> database_maj unnecessary

==> frm_update_database unnecessary

==> load_skin unnecessary

==> combobox_tools unnecessary

==> database_running unnecessary

==> database_log unnecessary

==> obj_standard unnecessary

==> Thread_POP unnecessary

==> Interface_manager unnecessary

==> Treeview_tools unnecessary

==> menu_tools unnecessary

==> affichage unnecessary

==> frmpnl_log_ unnecessary

==> frmpnl_show_online_mail_ unnecessary

==> frmpnl_threads_ unnecessary

==> frmpnl_show_offline_mail_ unnecessary

==> crypt_decrypt unnecessary

==> frm_status unnecessary

==> reinit unnecessary

frm_splashscreen in implementation

==> frm_lecture_mail unnecessary

Conclusion !

In conclusion this is a really valuable tool, you will save a lot of precious time if you maintain a high quality and reliable code. Maybe it will takes some hours to decrypt all the tools and use it correctly in your project (and correct some strange things), but after some times it will be automatic and you will do this naturally. You will write better code with less effort ! For me Pascal Analyser is a must have if you just have the professional version of Delphi.

I have negotiated a reduction just for you, use the coupon code “PALBLOG” when ordering and you will get 10% of reduction.

Click here to go to Peganza Website

Then

Kaspersky protection softwares

Delphi and C++ Builder IDE

Fruity Loops audio producing tools

The great installer InstallAware

Audio library manager MediaMonkey

are compiled by a ghost !