Database Search
TechHome
 | |
|
- !!A How to Treatise on Dynamic Dialogs
- Add a Status Bar on your Dialog
- Adding CRLF to a Tooltip Message
- Ampersand in Button
- Arrays in Dialogs
- AutoComplete in WinBatch Editboxes
- Autotimeout Example
- Ballon Tool Tips on Dialogs
- Balloon Tool Tips on Dialogs II
- Balloon Tool Tips on Dialogs III
- Bitmap Resizing in Dialog
- Button Dialog With No Default Focus
- Cancel Handler Issues within Dialogs
- Center dialog for any screen resolution
- Change Font in Dialog Controls
- Change Title of Dialog in Call Back Procedure
- Checking Char By Char Input in Dialogs
- Close Dialog Box upon completion of installation
- COMCONTROL Licenses Explained
- De-Activating Dialog Windows
- Dealing with Alt-F4 in Dialog
- Determine Control That Mouse is Hovering Over
- Dialog - Both Single and Multiple Selection Listboxes
- Dialog - Floating Toolbar
- Dialog - ProgressBar example
- Dialog Coordinates
- Dialog Editor 6 and UDS Callbacks
- Dialog Events For Unsupported Controls
- Dialog Significance of Config Parameter
- Dialog Units Explained
- Dialog with No Title bar
- Dialog with two list boxes and buttons to move items
- Dialogs - Adding ToolTips to Controls
- Dialogs - Menus in dialogs
- Disable Entry into DropListBox
- Disable Using ESC Key to Close Dialogs
- Display Dialog Along with RunWait
- Dynamic Dialogs - Creating Controls On The Fly
- Dynamic dialogs and BoxOpen Issue
- Dynamic Dialogs
- EditBox Cursor Placement
- Editbox with Filelistbox
- Error 3220 Dialog Format Version Not Supported
- Event Handling Questions
- File Browser within Dialog
- Get Value of RadioButton in Dialog Callback Procedure
- Hide or Unhide a PICTUREBUTTON
- High CPU Usage and Dialogs
- How to get an Editbox to Appear based on Selection
- How to Use the Spinner Control
- Inherited Check Mark
- IniWrite is Slow in Dialog Callback Procedure
- Japanese Dialog
- Leading 0 in a Spinner Control
- Make WIL Dialog Modal
- Maximized Dialog Hides Taskbar
- More UDFs to Make a Progress Bar Control
- MultiLineBox Limits
- Multiple Dialog Boxes
- Negative numbers in Dialog
- Non rectangular dialogs
- Non Responsive Dialog
- Position Dialog
- Pre-Selected Itembox
- Radio Button Disable Not Working
- Radiobuttons and Tabs
- Remove Border From ItemBox Control
- Right Justify Static or Variable Text
- Setting Spinner Control
- Simple Timer Procedure Example
- Smooth - Rounded Dialog Edges
- Splash Screen - Several Examples
- Start with Focus on Edit with No Selected Text
- Synchronize Two Itemboxes
- Tab Order and GroupBox Controls
- Toolbar UDFs for Drop Down Menus
- Treeview UDFs
- Unable to Load Background Image in Dialog
- Update Font Style in Dialog
- Using a Dialog as a Please Wait Screen
- WaitForKey Inside a Dialog Callback
- WebBrowser Control HTML Dialog
- WebBrowser Inside Dialogs by Guido
- Where are the Bitmaps for Pushbuttons
- Word Wrap
Can't find the information you are looking for here? Then leave a message over on our WinBatch Tech Support Forum.
WaitForKey Inside a Dialog Callback
Question:
I cleaned up a script and added a callback to a dialog (instead of using lots of 'If buttonpushed' options). One of the buttons - named HIDE - initiates WaitForKey. In the prior script when the HIDE button was pushed, the script would then wait for the END key to be pressed, and when it was the dialog would be reinitialized (since the dialog was naturally disposed of).Since a callback does not dispose of the dialog (that's the whole idea), the HIDE button now first initiates WinHide to hide the dialog window, WaitForKey (END) and when the END key is pressed it does a WinActivate to bring the dialog window back up.
Everything works as expected in both scripts. However, the problem now is that the callback script pushes CPU usage way up while it sits and waits for the END key to be pressed. It happens in either debug mode or when compiled.
Here is a short sample of the problem. The first WaitForKey is outside the UDS and behaves as expected. Once inside the UDS is when the problem happens. Can you explain what is going on? Any way out of it?
Windows XP, SP1
Winbatch 2005A
Answer:
Thats just the way it kinda works.You might get (maybe) better results if you disable the dialog with DialogProcOptions 1000 before the wait for key then enable the dialog afterwards.
Still its a naughty thing to do. DialogCallbacks are supposed to return as quickly as possible, the penalty being is that they burn hordes of cpu time.
User Reply:
That seems to have done the trick, Marty. Processer returns to zero when waiting inside the UDS. Whew!! I spent a ton of time on the script conversion to a callback and felt quite trapped by the problem. I'll watch it the next couple of days to see that it continues to run stable. Using the DialogProcOptions to re-enable the dialog adds a teeny bit of delay, but no one would ever really know the difference. Thanks so much for the suggestion!Article ID: W16925
File Created: 2007:07:03:14:27:06
Last Updated: 2007:07:03:14:27:06