Re: Manifest Requires Win2K Compatibility?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ya. Who knew there was actually as use for it. <eg>


"Rick Raisley" <heavymetal-A-T-bellsouth-D-O-Tnet> wrote in message
news:OuTYe344IHA.408@xxxxxxxxxxxxxxxxxxxxxxx
| So, Form_Initialize runs before Form_Load? Okay, thanks. ;-)
|
| --
| Regards,
|
| Rick Raisley
| heavymetal-A-T-bellsouth-D-O-T-net
|
| "Kevin Provance" <casey@xxxxxxxxxxx> wrote in message
| news:eRUACkt4IHA.4272@xxxxxxxxxxxxxxxxxxxxxxx
| >I don't know if this will be worth anything, but when using any kind of
| > InitCommonControl API via the form and not sub Main, the initialization
| > *must* be done in Form_Initialize. Why? Because the controls have
| > already
| > initialized by the time Form_Load executes which makes the
| > InitCommonControls useless.
| >
| > So, if your startup object is a form, do your CC initializing in
| > Form_Initialize. If using Sub Main, do initializing before loading *any*
| > forms.
| >
| > - Kev
| >
| > "Rick Raisley" <heavymetal-A-T-bellsouth-D-O-Tnet> wrote in message
| > news:eyYr8Wo4IHA.3796@xxxxxxxxxxxxxxxxxxxxxxx
| > | "Nando" <nospam@xxxxxxx> wrote in message
| > | news:jJidk.108615$102.93335@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
| > | >I was running into the same inconsistencies in the past, and after a
| > lot
| > of
| > | >trial and error I found that making the project and EXE name only
| > | >8-character long solved the problem.
| > |
| > | I was certain that couldn't be it, but changed the EXE name to 8
| > characters
| > | and it worked!
| > |
| > | Then I remembered I hadn't changed the Manifest file's name to match.
| > lol!
| > | No, that didn't work.
| > |
| > | > Also that in combination with the following code in a module:
| > | >
| > | > Private Declare Sub InitCommonControls Lib "Comctl32.dll" ()
| > | >
| > | > Public Sub Main()
| > | >
| > | > InitCommonControls
| > | >
| > | > Dim f As New Form1
| > | > f.Show
| > | >
| > | > End Sub
| > | >
| > | > Note that 'Sub Main' should be set as the 'Startup Object' under
| > Project
| > | > Properties -> General tab.
| > | >
| > |
| > | Actually, this stupid error on my part appeared to fix the problem. I
| > knew
| > I
| > | had to change the startup object, but got involved in other changes,
and
| > | forgot to do it. Fact is, I probably made it worse, as I took the
| > | InitCommonControls out of my Form_Load, put it in Sub Main, then
forgot
| > to
| > | change the startup object. ;-)
| > |
| > | > That's my two cents, hope it works for you.
| > | >
| > |
| > | Yes, it seems to so far. So basically everyone's advice was correct; I
| > just
| > | hadn't completely followed it up. I still think it's weird that when
set
| > to
| > | Windows2000 compatibility mode, it worked anyhow, but Bob may be right
| > about
| > | different OS's may have different DLL loading orders. I also think the
| > Win2K
| > | thing confused me enough that I wasn't being as careful as I should
have
| > | when setting up the DLL. That and the fact that most of my programs
work
| > | fine with only the Manifest, but not with the Init call.
| > |
| > | A final question: Setting up the InitCommonControls doesn't have any
| > effect
| > | on older Win95/98/Me/2K systems, does it? That is, I don't need to
| > determine
| > | the OS version before calling it, do I?
| > |
| > | Thanks again for everyone's help.
| > |
| > | --
| > | Regards,
| > |
| > | Rick Raisley
| > | heavymetal-A-T-bellsouth-D-O-T-net
| > |
| > |
| >
| >
|
|


.

Relevant Pages