Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

XPManifest

0 views
Skip to first unread message

AdamMaynard24

unread,
Jul 17, 2006, 10:33:49 PM7/17/06
to
What exactly does XPManifest do? There's no help on it, and it doesn't
seem to have any interesting properties or change the look of my
application. (under windows 2000 anyway). Perhaps it only functions
under XP?

Adam.

Nicholas Sherlock

unread,
Jul 17, 2006, 11:15:38 PM7/17/06
to
AdamMaynard24 wrote:
> What exactly does XPManifest do? [...] Perhaps it only functions
> under XP?

Bingo. As I understand it, the manifest tells Windows XP that the
program can be shown with the Windows XP skin.

Cheers,
Nicholas Sherlock

--
http://www.sherlocksoftware.org

Rob Kennedy

unread,
Jul 18, 2006, 3:29:34 AM7/18/06
to
AdamMaynard24 wrote:
> What exactly does XPManifest do? There's no help on it, and it doesn't
> seem to have any interesting properties or change the look of my
> application.

The component itself doesn't do anything at all. Take a look at the
source code. The unit is nearly empty. What you'll see in that unit,
though, is something you won't see in most other units. It has a $R
directive to include a resource file. That resource file contains a
manifest, so when your program uses that unit, the manifest resource is
linked to your program.

When Windows XP loads your program, it detects that resource and changes
its behavior accordingly. The manifest tells the OS which version of the
Common Controls library to use. By default, the OS will use version 5,
which does not do any theming. The manifest requests version 6, which is
where all the themed drawing takes place.

When you place a component on a form, the IDE automatically adds that
component's unit to the form unit's "uses" clause. The TXPManifest
component simply takes advantage of that behavior. Add that component to
a form, and the necessary unit gets used. The unit drags in the resource.

Note that removing the component does _not_ remove the resource. That's
because the IDE does not automatically remove units the same way it adds
them. If you added a TXPManifest component and later deleted it, you'll
need to remove mention of the XPManifest unit yourself.

> (under windows 2000 anyway). Perhaps it only functions
> under XP?

Well, duh.

--
Rob

AdamMaynard24

unread,
Jul 18, 2006, 6:34:01 AM7/18/06
to
Well, knowing what the component actually does, obviously it would be a
silly question to ask this. Not knowing what the component does, it
isn't such a silly question - you can get all sorts of components that
make Windows 2000 applications look like XP, XP buttons style etc..
perhaps this could have been on of them.

Thanks anyway though :)

Adam.

Jamie

unread,
Jul 18, 2006, 11:19:19 PM7/18/06
to
AdamMaynard24 wrote:

it works under XP. and it only places a
script in the Resource file which signals
XP about how to draw the window controls.


--
Real Programmers Do things like this.
http://webpages.charter.net/jamie_5

0 new messages