Results for "Category: Custom Controls/ Forms/ Menus"

A custom message box with 6 differents "skins" (GlassRed, GlassCandy, GlassOrange, Glassblue, GlassWhite, GlassYellow) use any (or none) icon/bmp for the messagebox..any size you wish, an offsetX and offsetY for exact placement of your messagebox picture, and the ability to play either exclamation, or warning sound, or a custom sound of your choice(or no sound at all) and best of all..it looks real nice)

Hide your porgams in the task manager, and from process lists. No one will ever know its there!

XP Menu is none visual component that changes the visual aspects of menus and toolbars to nearly the same look and feel of MS Office XP. No code required, you do not have to reconstruct menus or toolbars using components other than those shipped with Delphi. It's a 1.501 (Beta) version. ----------------------------------------------- ATTENTION : It's not my code. I find it on the web : http://www.shagrouni.com/english/software/xpmenu.html

Here is an example showing how to use the Component Template. You will find it under 'Component' on the Delphi menu. Component Templates are very handy, yet very simple to use.

::UPDATED:: With these procedures, you can make your Delphi forms translucent [see through] using some API that's in Win2k and Windows XP. If you like it, please vote. This is written in the newest Delphi version (6).

To center all of your forms nicely on the screen, use this as the first line in the Form_Load event--resolution independent. 'note:call this function like this: Center_Form Me

When you need to display the history of a changing value, there is a bit of work that must be done. This UserControl does that work for you in all sorts of colors and styles. Don't forget to vote!

Show how to make a text box not beep but do something else when I hit the Enter key. This code example makes nothing happen, for an extended period of time:

This code is reusable and small enough to paste into whatever you're doing and instantly have a form that has no need for a title bar.

You can achieve some cool form wipes with judicious use of the Move method. For example, to draw a curtain from right to left use this routine. It is also possible to wipe a form from bottom to top, and from both sides to the middle, using similar routines

The primary focus here is to allow you to display forms that are larger than the screen can show. Need an 8½" x 11" Form? NO Problem!The size used in this example is 8½" x 11", but it could just as easily be landscape, envelope, or any needed size.

Although using the API is a nice way to create multi-colored forms, there might be a reason why you would wish to create one without using the API.

The Switchboard:A method for handling subclassing in ActiveX controls f you develop ActiveX controls and intend to subclass or hook a window, you'll very quickly discover a problem when you attempt to site multiple instances of your control. The subclassing, which worked fine with a single instance of your control, now no longer works and is, in fact, most likely is causing a GPF. Why is this happening? The AddressOf operator requires you to place the callback routine in a module. This module is shared between all instances of your control and the variables and subroutines that the module provide are not unique to each instance. The easiest way to visualize the problem is to imagine a shared phoneline (or a partyline as we hicks call it) where multiple parties are trying to dial a number, talk, and hangup, all at the same time. What's needed is an operator, a routine that controls the dialing (hooking), the talking (the callback routine), and who routes information to the instance of the control that requested it. The Switchboard subroutine (see below) and it's supporting code provides a method for subclassing from multiple instances of your ActiveX control. It is not memory intensive, nor is it slow. It's biggest weakness is that it is hardcoded to intercept particular messages (in this case, WM_SIZE, to trap resize events) and will require some minor modification on your part to use.

These events are usually ignored or inconsistent amongst programs. For the users benefit, highlighting the current textbox, or tab control will aid in their navigation of your forms. But how to keep all these events consistent? Here is the answer. (Well our answer anyhow... until full-inheritance in VB 5.0)

Visual Basic 5.0 allows you to use UserControls to create ActiveX controls in your projects. The following code snippet does two things: It gets a reference to the form in which a UserControl is placed, and it gets a reference to that control on the form. by David Mendlen

Suppose you have a listbox with some elements and want to drag&drop a selected one into a textbox. http://137.56.41.168:2080/VisualBasicSource/vbdraganddrop.txt

handy code for clearing all text box controls at run-time so you don't have to bother doing it at design time. http://137.56.41.168:2080/VisualBasicSource/vbworkingwithtextbox.txt

Use of 3 types of common dialog boxes:1: choose printer, 2: choose font, 3: choose color. http://137.56.41.168:2080/VisualBasicSource/vb4usecommondialog.txt

Keep a form always on top (topmost floating form) in windows 95. Albetski, Allan"

Short tutorial on how to use the toolbar in VB4/5 32 bit. http://137.56.41.168:2080/VisualBasicSource/vb4toolbar.txt