Results for "Author: duncan jones"

Everyone knows how useful Debug.Print can be when debugging a program in the run time environment...but why not make these debug comments available from an executable. Simply replace Debug.Print with the following, and then when your application is running as an executable you can use a debugger (such as DBMON.EXE, downloadable form MSDN) to see the debug comments as they occur:

Shows the printer document properties dialog box from code.

Often especially when dealing with the API, byte and integer data types will be packed into LONG INTEGER (32 bit) values. Thes snippets allow you to decode/encode these 32 bit longs:

Purpose: -------- A tool to allow you to attach a debugger to a process and be notified when debug events (such as a thread starting, a dll unloading etc.) occur and optionally to pause that application on such an event. Demonstrates: ------------- Using the windows API to attach to a process and read it's memory

Shows how the executable is laid out so that you can browse it's contents...

Drop the control on your form and then when your app is running the "ClipboardChanged" event will trigger whenever the clipboard contenst change, system wide.

A class to allow you to print a data grid across multiple pages, with defined sty;es and with a header and footer on each page.

Shows how the executable is laid out so that you can browse it's contents...

Drop the control on your form and then when your app is running the "ClipboardChanged" event will trigger whenever the clipboard contenst change, system wide.

A beginners guide to how windows (tm) works

3 tips that you should definitely use to make your own developed ActiveX controls more developer friendly:

This program allows you to send Windows Messages to any active window on the system in order to find out what happens when you do. Hours of fun...

2 controls that vastly extend the cababilities of Visual basic. *** VBEventWindow - provides a simple subclassing control. Events: - ActiveApplicationChanged, fired when your app gains or loses user focus - LostCapture, fired when your app gains or loses the capture - KeyPressed, fired when any of the keys are pressed - LowMemory, fired when the system is running low on memory - Move, fired when the form is moved - VerticalScroll, HorizontalScroll, fired when the form scrollbars are set - WindowsSettingsChanged, WindowsINIChanged , fired when the windows environment settings are changed - NonClientMouseMove,NonClientMouseDown,NonClientMouseUp,NonClientDblClick, fired when a mouse event occurs in the non-client part of your form - MinMaxSize, fired when the OS wants to know what size to make your form either in response to a minimise/maximise command or when the user is dragging the resize box. - MouseOverMenu, fired when the mouse is over a top level menu - WindowMessageFired fired for all the other windows messages Methods: - InvalidateRect, Sets part of the form invalid to indicate that it needs to be repainted Properties: - ClassName, returns the windows class name fo the form - DeviceContext, returns the device contect of the form (for graphical operations) - HorizontalScrollbar, VerticalScrollbar, sets or unsets scrollbars on the form - TopMost sets the form to float over the top of other forms - Transparent, makes the formclient area invisible Use: In the form load... Private Sub Form_Load() Me.VBEventWindow.ParentForm = Me.hWnd End Sub *** VBSysTrayCtl - Provides a simple control to allow your application to use the SysTray Events: - MouseMove, Fired when the mouse moves over the tray icon - MouseDown, Fired when a mouse down event occurs over the tray icon - MouseUp, Fired when a mouse up event occurs over the tray icon - MouseDblClick, Fired when the user double clicks the Tray Icon Methods: - ShowIcon, displays the icon in the system tray area - Hideicon, removes the icon from the system tray area - Refresh, updates the icon displayed in the system tray area Properties: - Tooltip, the tip that is displayed if the user hovers the mouse over your systray icon Use: In the form load.... Private Sub Form_Load() Me.VBSysTrayCtl1.Tooltip = "Merrion Computing" Me.VBSysTrayCtl1.ShowIcon End Sub Private Sub Form_QueryUnload(Cancel As Integer, UnloadMode As Integer) Me.VBSysTrayCtl1.Hideicon End Sub

This articles shows how you can use windows messages to communicate between two (or more) applications.

Temporarily change the currently selected (default) printer within your VB program

This code allows you to record the interaction between the user and application and then play it back later. This allows you to implement rudimentary macros and automation to your existing applications without extensive changes. Also the record is saved in a text file that is very easy to change - useful for creating automatic test cases.

Shows how you can use the Windows API to return additional information about the printer above and beyond that which is available through the Visual Basic Printer object.

Installs a system wide hotkey which triggers the HotkeyPressed event whenever the chosen hotkey combination is pressed - regardless of whether your application has the focus or not. Release 1.0.5 allows the hotkey to be changed at runtime and also to be enabled/disabled.

Allows you to Peek and Poke memory (For those not old enough to remember these commands, read a value from an address in memory and write a value to an address in memory)

Everyone knows how useful Debug.Print can be when debugging a program in the run time environment...but why not make these debug comments available from an executable. Simply replace Debug.Print with the following, and then when your application is running as an executable you can use a debugger (such as DBMON.EXE, downloadable form MSDN) to see the debug comments as they occur: