Results for "Author: gduncan"
A button that you would use to minimise your app to the system tray. I liked a submission made earlier by AB Software (code id = 58679) but didnt like the need for external controls and bas files. This submission does the same job but everything is contained within one usercontrol making it easy to just drop into any project. It has its limitations and there is scope for further development. If I do anything further on it I will post updates. Feedback appreciated. Acknowledgements made within the code where appropriate.
A datepicker. See screenshot. Supports themes, different date formats, hand cursor, short day names, non month days and first day of week assignment. The main advantage of this code is that it is a single usercontrol, not an OCX. Update: Changed the test to see if themes were enabled for 2000 users.
The screenshot should give you a good idea of what this control does. It slows down your code. It's like a DoEvents you can manage. Great for background tasks. I had an app that needed to do database maintenance to a very large number of records. Firing the maintence sub caused the cpu to run at 100% for several minutes during which time the user could not do anything as their system all but locked up. Hence this handbrake. Using it you can run your process in the background without causing the user any inconvenience. If you set CPULimit to 0 it will introduce a one second wait into each itteration of your loop. This will create a burst effect where your routine does a process, then waits for 1 second, then does another burst etc. Alternativly you can set CPULimit to the maximum level at which your app can process to. So you could create a situation such as... do the work, but dont exceed 10% of the cpu useage. If the user is doing something then the control will just hold your app suspended until CPU useage falls, or if the user isnt using the CPU then your app can grab it and process in the background. It is important to structure your loop properly. See sample for how to use.
A button that changes its display based upon the theme capabilities of the computer it is run on. See screenshot to see what I mean. If themes are detected buttons can: Include Icons. Be shown in Toolbar or Button style. Offset the Caption and Picture so they can be drawn exactly where you want. Draws icon disabled when button is disabled. If no themes are detected you get a normal graphical button. The button: Changes display with theme change. Contains No Timer. Is in a single usercontrol. You would use this button to provide backward comptability in your display whilst presenting modern buttons with icon support. Suggestions, Votes and Feedback appreciated. Update: Fixed bug on midi forms and added a deleteobject for the region.
A useful UserControl that will speed up your development time and give you a great looking GUI. Simply drop the control on your form and thats it, all done. At run time your form will be rendered with a stylish gradient background. Why should you bother with it when there are plenty of other gradient submissions out there? Because it will reduce your development time and keep your project organised and simple. It is easily transfered between projects. It doesnt repaint your whole form on each WM_PAINT message so generates no lag when other windows move in front of your app. It is clean, fast, and easy to understand. It produces little to no resize lag and can easily be added to any project. Some submissions are fun, some are educational, this one is FUNCTIONAL. 99% of projects could benifit from this sumbission.
A button that you would use to minimise your app to the system tray. I liked a submission made earlier by AB Software (code id = 58679) but didnt like the need for external controls and bas files. This submission does the same job but everything is contained within one usercontrol making it easy to just drop into any project. It has its limitations and there is scope for further development. If I do anything further on it I will post updates. Feedback appreciated. Acknowledgements made within the code where appropriate.
A datepicker. See screenshot. Supports themes, different date formats, hand cursor, short day names, non month days and first day of week assignment. The main advantage of this code is that it is a single usercontrol, not an OCX. Update: Changed the test to see if themes were enabled for 2000 users.
The screenshot should give you a good idea of what this control does. It slows down your code. It's like a DoEvents you can manage. Great for background tasks. I had an app that needed to do database maintenance to a very large number of records. Firing the maintence sub caused the cpu to run at 100% for several minutes during which time the user could not do anything as their system all but locked up. Hence this handbrake. Using it you can run your process in the background without causing the user any inconvenience. If you set CPULimit to 0 it will introduce a one second wait into each itteration of your loop. This will create a burst effect where your routine does a process, then waits for 1 second, then does another burst etc. Alternativly you can set CPULimit to the maximum level at which your app can process to. So you could create a situation such as... do the work, but dont exceed 10% of the cpu useage. If the user is doing something then the control will just hold your app suspended until CPU useage falls, or if the user isnt using the CPU then your app can grab it and process in the background. It is important to structure your loop properly. See sample for how to use.
A button that changes its display based upon the theme capabilities of the computer it is run on. See screenshot to see what I mean. If themes are detected buttons can: Include Icons. Be shown in Toolbar or Button style. Offset the Caption and Picture so they can be drawn exactly where you want. Draws icon disabled when button is disabled. If no themes are detected you get a normal graphical button. The button: Changes display with theme change. Contains No Timer. Is in a single usercontrol. You would use this button to provide backward comptability in your display whilst presenting modern buttons with icon support. Suggestions, Votes and Feedback appreciated. Update: Fixed bug on midi forms and added a deleteobject for the region.
A useful UserControl that will speed up your development time and give you a great looking GUI. Simply drop the control on your form and thats it, all done. At run time your form will be rendered with a stylish gradient background. Why should you bother with it when there are plenty of other gradient submissions out there? Because it will reduce your development time and keep your project organised and simple. It is easily transfered between projects. It doesnt repaint your whole form on each WM_PAINT message so generates no lag when other windows move in front of your app. It is clean, fast, and easy to understand. It produces little to no resize lag and can easily be added to any project. Some submissions are fun, some are educational, this one is FUNCTIONAL. 99% of projects could benifit from this sumbission.
A button that you would use to minimise your app to the system tray. I liked a submission made earlier by AB Software (code id = 58679) but didnt like the need for external controls and bas files. This submission does the same job but everything is contained within one usercontrol making it easy to just drop into any project. It has its limitations and there is scope for further development. If I do anything further on it I will post updates. Feedback appreciated. Acknowledgements made within the code where appropriate.
A datepicker. See screenshot. Supports themes, different date formats, hand cursor, short day names, non month days and first day of week assignment. The main advantage of this code is that it is a single usercontrol, not an OCX. Update: Changed the test to see if themes were enabled for 2000 users.
The screenshot should give you a good idea of what this control does. It slows down your code. It's like a DoEvents you can manage. Great for background tasks. I had an app that needed to do database maintenance to a very large number of records. Firing the maintence sub caused the cpu to run at 100% for several minutes during which time the user could not do anything as their system all but locked up. Hence this handbrake. Using it you can run your process in the background without causing the user any inconvenience. If you set CPULimit to 0 it will introduce a one second wait into each itteration of your loop. This will create a burst effect where your routine does a process, then waits for 1 second, then does another burst etc. Alternativly you can set CPULimit to the maximum level at which your app can process to. So you could create a situation such as... do the work, but dont exceed 10% of the cpu useage. If the user is doing something then the control will just hold your app suspended until CPU useage falls, or if the user isnt using the CPU then your app can grab it and process in the background. It is important to structure your loop properly. See sample for how to use.
A button that changes its display based upon the theme capabilities of the computer it is run on. See screenshot to see what I mean. If themes are detected buttons can: Include Icons. Be shown in Toolbar or Button style. Offset the Caption and Picture so they can be drawn exactly where you want. Draws icon disabled when button is disabled. If no themes are detected you get a normal graphical button. The button: Changes display with theme change. Contains No Timer. Is in a single usercontrol. You would use this button to provide backward comptability in your display whilst presenting modern buttons with icon support. Suggestions, Votes and Feedback appreciated. Update: Fixed bug on midi forms and added a deleteobject for the region.
A useful UserControl that will speed up your development time and give you a great looking GUI. Simply drop the control on your form and thats it, all done. At run time your form will be rendered with a stylish gradient background. Why should you bother with it when there are plenty of other gradient submissions out there? Because it will reduce your development time and keep your project organised and simple. It is easily transfered between projects. It doesnt repaint your whole form on each WM_PAINT message so generates no lag when other windows move in front of your app. It is clean, fast, and easy to understand. It produces little to no resize lag and can easily be added to any project. Some submissions are fun, some are educational, this one is FUNCTIONAL. 99% of projects could benifit from this sumbission.