Printable View
So, this is basically useluss all the same for non XP users, only XP users wanting to make there VB projects with an XP look. And the only way to make VB apps have an XP look on an OS other than XP is third party control whatever?
That sucks, no manefestation on Win98 Se:mad:
Me upgraded to XP now, so its cool :cool:
Ok a couple of things i want to point out. I have been researching this for a little while
1) Like someone mentioned before, for radio buttons and command buttons inside a frame, you must place the frame inside a picture box. Otherwise you'll get surround black areas around the radio buttons and command buttons. So the heirarchy of the objects would look something like this:
- PictureBox
- Frame
- CmdButton
- RadioButton
- Etc
2) There are two ways of using xp styles: 1) using a separate manifest file with the compiled vb executable OR 2) Avoid using a separate manifest file altogether and compile a .res file WITH the vb exectauble (which is MUCH cleaner IMO). You will need the following files:
This is an alternate way of doing what des1411 explained in his first post, as some people do not want to be downloading extra programs and screwing around inside an executable file.
BEOFRE YOU START: Replace anywhere it says 'abcApp' with the name of your vb app's executable file.
manifest file (abcApp.exe.manifest):
NOTE: for some reason the filesize of the manifest file must be a multiple of 4 bytes. So if your manifest file is 457 bytes (this is JUST an example), then add a few spaces to the end of the file to make it 460 bytes.A .rc file (abcApp.rc) :Code:<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity
version="1.0.0.0"
processorArchitecture="X86"
name="CompanyName.ProductName.YourAppName"
type="win32" />
<description>Your application description here</description>
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="X86"
publicKeyToken="6595b64144ccf1df"
language="*" />
</dependentAssembly>
</dependency>
</assembly>
and a batch file (MAKERES.BAT) :Code:#define CREATEPROCESS_MANIFEST_RESOURCE_ID 1
#define RT_MANIFEST 24
#define CONTROL_PANEL_RESOURCE_ID 123
CREATEPROCESS_MANIFEST_RESOURCE_ID RT_MANIFEST "abcApp.exe.manifest"
NOTE: make sure rc.exe is located at "C:\Program Files\Microsoft Visual Studio\VB98\Wizards\"Put all 3 of these files into a separate folder and run the batch file (MAKERES.BAT). This should create a file named abcApp.resCode:"C:\Program Files\Microsoft Visual Studio\VB98\Wizards\RC.EXE" /r /fo abcApp.res abcApp.rc
Copy the .res file to the folder where your vb project sources files are located and add the .res file to your project. To do this, right click in the Project Explorer and go to Add > Add File, then select the .res file.
You must still add the InitCommonControls code to your project as explained by des1411, but the difference is you won't have to continuously edit your executable everytime you compile it and you still wont have a messy manifest file hanging around.
(check out: http://www.vbaccelerator.com/home/vb...VB/article.asp for more information about this)
Just a side note: This is not very effective if you are working with large applications as it becomes tedious (and messy) to always embed your radio buttons and command buttons that are in frames, into a picture box. This also gives room for more errors, so I would avoid it for large projects. It's much more efficient for small programs that have one or two or three forms.
Hope this helps everyone!
Works good,but the optionbuttuns (only in frames) becomes black :(
(atachment)
Fixed!
That issue is explained in point 1 of the previous post, and so is the solution to it (put the option buttons on a picturebox, and put that on the frame)
Ok thanks:wave:Quote:
Originally Posted by si_the_geek