Results for "Author: mick doherty"

This turned out to be more difficult to work out than the drawing of a button on the titlebar. Of course once I'd got it it was simple. Once again this code uses subclassing so always use the forms close button or the menus exit to stop the project, or you will crash.

I have been working on menus since my last submission and here is the result.

I keep seeing messages posted about the lack of support for Visual Styles in TabPages. Well, I thought, that can't be too difficult to overcome, and I was right it wasn't. OK so I already knew how to use the API's from VB6 and it was simply a case of getting those to work in DotNet(not quite as simple as I'd like). One problem though, I am using VS2003 Beta so this project will not load in VS2002. However, the TabPageXP.vb file is just plain text so you can add that to a VB2002 project, and really thats all you want. Full instructions for usage supplied in the TabPageXP Class file.

Even though you didn't seem interested in my TabPageXP submission, I have Updated it to a full Control. It has inherited the TabPage reordering bug (SelectedIndex) and has introduced a new one (well only one that I have found), adding Tabpages through the Collection Editor is fine, but if you add through the designers contextmenu you will get a standard TabPage. The TabPageXP Class has been updated to remove the flicker that no one complained about.(well at least on my P4 2Gig). Written in VB2003 Final Beta so the solution will not open in VS2002 (Sorry about that, but I don't have VS2002 installed since my Hard drive died).

Tired of those ugly black shadows you get from WindowsXP Alpha Icons? Sure DrawIcon solves the problem, but sometimes you just want to pass a bitmap, created from an Icon, to an Image property. This project shows you how.

This version demonstrates how to use the new style dialog (WinMe, Win200 only), and start at specific paths. I am sure there are better ways of doing things than the way I have done some of it, but I don't know that way. Very little comments, but I think its easy enough to follow.

This has kept me occupied for a couple weeks. Most of what is in here I learned to use while writing it. I think I have thought of everything, but maybe not. The button draws itself in the correct system colours, it sizes and positions itself according to system settings. I have noticed that the TrayMenu does not react properly in the development environment, it does behave itself once compiled though. Also, when compiled, the Tooltip does not work until after you have restored the App from the system tray, but it works ok in the development environment. I don't know why this is, maybe someone could explain it for me.

This turned out to be more difficult to work out than the drawing of a button on the titlebar. Of course once I'd got it it was simple. Once again this code uses subclassing so always use the forms close button or the menus exit to stop the project, or you will crash.

I have been working on menus since my last submission and here is the result.

I know there are a lot of ScreenSaver examples on PSC, but I have not seen a complete one. This example includes: Thumbnail Preview Password Protection Password Change Set Up The actual screensaver is nothing special, so please don't comment on the excellent graphics. I can only test on WIN ME so if this code does not work with other OS's, then this is the feedback that I want. I know of some probs with NT and believe I have handled those, but I can't test that. I am not looking for votes, just feedback.

Windows XP ships with Common Controls version 5 and version 6. By default all windows apps use version 5. In order to force your app to use version 6 your application must have a manifest. It must also correctly call InitCommonControls(). A manifest is a text file with an xml script similar to this: ------------------------------------------------------------------------------ Your App Description ------------------------------------------------------------------------------ If your application is called 'MyApp.exe' then in the same directory you must have a manifest file called 'MyApp.exe.manifest' otherwise WinXP will use common controls v5. Instead of having a seperate manifest file, this project inserts the manifest into the executable file, and therefore, safeguards the manifest file from deletion or corruption.

Note: If you don't have XP then this is of no use. A simple replacement frame control. Since the release of Windows XP, VB developers have been plagued with those trusted old standard controls misbehaving themselves. One of the most common problems being with the Frame control. When you place certain controls in a frame control, such as buttons and option boxes, they are drawn with incorrect masking when Visual styles are in use. If you place a frame control inside a frame control then the label of the frame control becomes transparent (you can see the etched edge behind the caption) and is incorrectly sized resulting in an incomplete caption. In addition to these problems, the frame control will flicker during redraw events. You can fix the frames incorrect masking by adding a picturebox to the frame control and using this as the cointainer, but because there is an extra window, it will result in making the flicker worse. There is a fix to cure the flicker through API, using SetWindowLong with the WS_EX_COMPOSITED style, but I found that caused problems with scrollbars. After a lot of messing about I decided to write my own Frame Control. It has been based on the standard frame control and there are a few minor bugs, but all in all I think it does a better job in XP than the standard control. The code is fairly simple and the Test project contains a Manifest Resource which will compile into the exe. I have not seen a Manifest in any example code and have not seen any explanation on how to create one, so perhaps this example should have been dedicated to that. I spent a few days messing around with Manifest Files until I found the solution to successfully creating Manifest Res files, but I am keeping that secret for now :( (hint: Padding) thats as much as i'm saying. I am sure that some of you will borrow the Manifest resource for your own apps (I'll be watching). You may notice the redundant ImageList control. This is an essential part of the control even though it appears to do nothing. If you don't believe me, compile the control with it and make an executable with the control. Run the compiled exe and close. Next build the same control without the Imagelist and re run your compiled exe. What's that? Runs fine you say. Well what happens when you close it? If all was well then you were probably not running XP or if you were then you have found some fix that I know nothing about.------------------------------------------- Bug Fix 21 January 2003:------------------------- Accelerator Key support added.

I am a fair VB6 programmer. I have taken a trial version of VS.NET. I decided to play with the new Owner Draw Menus. After around five total rewrites I am happy with these results. Simply follow the instructions in the Class #Region "Usage Notes" and you will instantly have XPStyle Menus without coding. Don't ask me how to get the real colors though as I gave up there(So many settings affect each one).

I keep seeing messages posted about the lack of support for Visual Styles in TabPages. Well, I thought, that can't be too difficult to overcome, and I was right it wasn't. OK so I already knew how to use the API's from VB6 and it was simply a case of getting those to work in DotNet(not quite as simple as I'd like). One problem though, I am using VS2003 Beta so this project will not load in VS2002. However, the TabPageXP.vb file is just plain text so you can add that to a VB2002 project, and really thats all you want. Full instructions for usage supplied in the TabPageXP Class file.

Even though you didn't seem interested in my TabPageXP submission, I have Updated it to a full Control. It has inherited the TabPage reordering bug (SelectedIndex) and has introduced a new one (well only one that I have found), adding Tabpages through the Collection Editor is fine, but if you add through the designers contextmenu you will get a standard TabPage. The TabPageXP Class has been updated to remove the flicker that no one complained about.(well at least on my P4 2Gig). Written in VB2003 Final Beta so the solution will not open in VS2002 (Sorry about that, but I don't have VS2002 installed since my Hard drive died).

Tired of those ugly black shadows you get from WindowsXP Alpha Icons? Sure DrawIcon solves the problem, but sometimes you just want to pass a bitmap, created from an Icon, to an Image property. This project shows you how.

This version demonstrates how to use the new style dialog (WinMe, Win200 only), and start at specific paths. I am sure there are better ways of doing things than the way I have done some of it, but I don't know that way. Very little comments, but I think its easy enough to follow.

This has kept me occupied for a couple weeks. Most of what is in here I learned to use while writing it. I think I have thought of everything, but maybe not. The button draws itself in the correct system colours, it sizes and positions itself according to system settings. I have noticed that the TrayMenu does not react properly in the development environment, it does behave itself once compiled though. Also, when compiled, the Tooltip does not work until after you have restored the App from the system tray, but it works ok in the development environment. I don't know why this is, maybe someone could explain it for me.

This turned out to be more difficult to work out than the drawing of a button on the titlebar. Of course once I'd got it it was simple. Once again this code uses subclassing so always use the forms close button or the menus exit to stop the project, or you will crash.

I have been working on menus since my last submission and here is the result.