Tom Peiffer

Send e-mail to this Author

Looking for the best casino bonus offers in New Zealand? We have them.
Author Products

Total 6 products

HPTimer v.1.2

Components > Date and Time > Timers

By Tom Peiffer.

Freeware + source 30 Jul 1999

Description

A thread driven high resolution timer up to a frequency of your CPU.

Informations

  • Status: Fully functional
  • Source: Included
  • Size: 24kB

Platforms: D4

Registry in a Class v.1.1 beta

Components > System > Registry

By Tom Peiffer.

Freeware + source 18 Sep 2000

Description

This is probably the most easiest way to work with data from the registry. Drop the component on your form, create an own class, fill out the properties and you may access registry data just by calling the properties of your registry class. There are no special methods needed. Just access the registry by reading the appropriate properties.

Informations

  • Status: Fully functional
  • Source: Included
  • Size: 11kB

Platforms: D4, D5

Resource Exporter v.1.0

Components > System > Resources

By Tom Peiffer.

Freeware + source 17 Apr 2000

Description

Many users just use resource files (*.res) for the purpose of saving icons or wave files in them. After compilation, the icons and waves are included in the executable file, so that they need not to be distributed the the application. With this component, you may include any file, also other executables, inside a resource file. The component is able to export these files again and write them to your harddisk. In this way, you can store complete other files inside your application.

Informations

  • Status: Fully functional
  • Source: Included
  • Exe demo: included
  • Size: 478kB

Platforms: D4, D5

SwitchModules v.1.0

Components > System > Apps Communications

By Tom Peiffer.

Freeware + source 19 Aug 2004

Description

Two components enabling interprocess messaging in a simple an effective way. Define Text commands that you may send from one application to another. The commands are received automatically with 2 lines of code and fire an event in the destination application. You have the option to add parameters to each command, and be able to react appropriatly in the fired event in the destination process. If a destination application isn't launched yet, this is done automatically. If the destination application is already running, your can optionally avoid the start of a second instance. In the destination application, this makes no difference.

The package comes with 2 components:

  • TModuleSwitcher, which allows the sending of commands with parameters. The component only needs to be placed in the sender application. The actions can be automatically linked to a menuitem or a speedbutton. The icon can be extracted automatically from the destination file. Just drop a speedbuton and/or an idle menuitem and set the appropriate properties in the component.
  • TCommandReceiver, which is responsible for receiving the commands from TModuleSwitcher, identify the command and extract its parameters values to a TStringList. The component is placed on the mainform of the destination application, and activate by 2 lines of code.
Two techniques are used for receiving the commands. First is by interpreting the startup paramaters (when the destination application is first launched), of by receiving a windows message (if the application is already running and a second instance shell be avoided.

Informations

  • Status: Fully functional
  • Source: Included
  • Exe demo: included
  • Size: 25kB

Platforms: D4, D5, D6, D7

TApplValues v.2.1

Components > System > Registry

By Tom Peiffer.

Freeware + source 14 Sep 2000

Description

In Delphi, you got powerful classes to access both the Windows registry and work with INI-files. But there is still a lot of code needed, to work with these classes. With this component, this becomes much easier. And values from your inifile or registry key are loaded directly into published properties in a predefined class. Just call the Load method, or even more easy, set the LoadOnCreate property to true, and your values are loaded in your published properties at startup of your application. Make changes to your properties and call the Save method (or set SaveOnExit to true) and the values are stored back to registry rsp. inifile. All you need to do is define a new class derived from TApplValues and define published properties in this class. Now, in the values property of the component, define for each published property a location where to store the value (section, subkey, default value if key does not exist etc.). For the rest, one single line of code is needed:

MyValues := TMyValues.create (Self, AP); {supposing that the component name is AP, and your derived class from TApplValues is called TMyValues, where MyValues is a pointer to this class}

Confused? Then take a look to the demo project and you'll discover the power behind it.

Informations

  • Status: Fully functional
  • Source: Included
  • Size: 20kB

Platforms: D4, D5

User Dialog v.3.05

Components > Dialogs > Message Boxes

By Guy Besch, Tom Peiffer.

Freeware + source 18 Sep 2000

Description

Component of MessageDlg function, coming up with many additional features compared to the MessageDlg:
  • You are using a component, so you can edit the message at design time in the Object Inspector itself. So there's no need of writing long code if you want you display large texts in your dialog
  • You can parameters like in TQuery component that you can assign a value during runtime
  • Caption of the buttons is user defined
  • Background color of dialog is user defined
  • User defined font
  • User defined title caption
  • Possibility of showing the glyphs on the buttons
  • User definable icons (or standard icons from MessageDlg)
  • User definable WAV sound (or standard Windows Sound)
  • Possibility of making a preview already during runtime.

Informations

  • Status: Fully functional
  • Source: Included
  • Size: 31kB

Platforms: D2, D3