Database Search

match allmatch any Look in all areasLook in current areas Check all datesPrevious dayPrevious 3 daysPrevious weekPrevious fortnightPrevious monthPrevious 2 monthsPrevious 3 monthsPrevious half-yearPrevious year

TechHome

	COMCONTROL
	Dialog Editor version 5.X
	Dialog Editor version 6.2
	Dialog Editor version 6.X

• Align a Dialog Box in Upper Right
• Automatically Number Dialog Controls
• Bitmaps in a Dialog Box
• Centering and Size Dialog Editor Boxes
• Changing Tab Order in Dialog
• Choosing a Directory in a Dialog
• Determine if All or None of Items are Selected
• Determine User Specified Color in Dialog
• Dialog Box with File Editor Window
• Dialog Boxes and CTL3DV2.DLL
• Dialog Callback Script Generation
• Dialog Editor Limitations
• Dialog Editor which button was pushed
• Dialogbox Creation Failed Error 3104
• Displaying Contents of a File in ItemBox
• FileListBox Specify the Extension
• FileListBox to Display Directories Only
• FileListBox to Display File Mask
• Fonts used in Dialog Editor
• Getting Unlicensed Version Message with Dialog Editor
• How to Create Required Entry Fields
• How to Set up ItemSelect Listbox in Dialog Editor
• Invisible Display
• Itembox Use with Variable
• Long Text Fields in Dialog
• Maximum Controls
• Maximum Length of STATICTEXT control
• Minimize Restore Close Menus
• Multiple Checkboxes
• Order of Controls in Dialog Editor
• Radiobuttons - Several with Only One Selected
• Reading Info from File and Displaying in Dialog
• Repaint Dialog with Variables from Another Dialog
• Rescale Dialog Resolution Change
• Save and Restore a WIL Dialogs Size and Location
• Select an Item by Default in ItemSelect Listbox
• Send Email with dialog
• Set Checkbox as Checked by Default
• Slow Startup of Dialog on Some Machines
• Use of Intcontrol(4,1,0,0,0) with ItemSelect Listbox
• Variable Number of Controls in a Dialog
• Which PushButton was Pushed

Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.

Invisible Display

---

Question:

Why use Display with negative timeout value to display an invisible message?

Answer:

TimeDelay just delays for a time. Display puts up a new window, tells that window to delay for a while, and waits until the window is done delaying. A much more complex version of TimeDelay that invokes (huge - relatively) chunks of code.

If someone is trying to hack an MSIE window into a dialog, and then in a dialog callback procedure tell the hacked-in window to automatically scroll down. But because the code is currently running within a dialog callback, WinBatch message processing hits a standstill waiting for the callback to return, and the scroll down command either gets delayed or simply lost in the shuffle.

It was found that doing a Display or Message function allowed this scrolling of the hacked in control to work properly. But obvious message, since it totally halts processing until it is responded to was not a favorite choice. Display was better, but it did pop up the display message of course, and was distracting. So, using a simple hack that *may* be removed before the end of beta, passing a negative time to the display function causes it to display the display message invisibly. The theory is that whatever un did the jam for the scrolling problem would also be undone by the hidden display box. It is not very likely than the hidden display would have much use outside of dialog callback functions dealing with non-WinBatch window controls hacked into a Windows dialog that was being sent OLE commands and needed a lot of message traffic to occur. Documentation for this feature is likely to be sketchy at best.

---

Article ID:   W16913

File Created: 2007:07:03:14:27:02

Last Updated: 2007:07:03:14:27:02