Search:

Don't be an ass.

I said windows programs are not supposed to have spaces in their names... because of the way they're interpreted...

It's about how the command interpreter parses the filename...

You have to get this stuff right or it simply ignores the entire manifest....



Make these changes and recompile the resources...

And FWIW.... windows programs cannot have spaces in their...

Correct again... Yes, it's in a critical section, so the PB code waits in the event of a collision.

If you're still not getting the visual style... it's almost certain to be a problem with the manifest...

If you open your EXE in a hex editor can you see the manifest in the resources at the end...

Check out Pelles C ... it's C99, up to date, and comes with a wonderful IDE and full documentation of the entire library (including hundreds of extension calls), does Console and GUI mode... Best...

What resource editor are you using?

It's an external file that is included...



1 MANIFEST "Manifest.xml"


... like that.

You need to change the x86 to amd64 in two places... but yes that's essentially correct.




It goes in your .rc file. Then when you compiler the project it's placed in the resources area of...

Um, no...

Calculate the postion of the progress bar in the WM_TIMER handler according to the state of your task.

For example, loading a file, line by line... In the WM_TIMER do a calculation...

In your last code sample... Lines 21 to 25 should be above line 17... there's no point intializing comctrls AFTER the dialog returns.

To do this on a timer so that the progress bar travels on it's...

Then you would put the messages in the "click" handler for your button.

Although, it's far more common to do that with a timer, so that it appears to be updating on it's own.

Yes, good suggestion... although I generally keep an array of HWNDs at the page-global scope so I have them handy...



// after includes and defines

HWND Handles[10];


Makes life a...

Or as a third option, since CreateWindow returns a window handle...


hwndpb = CreateWindowEx(0, PROGRESS_CLASS, NULL,
WS_CHILD | WS_VISIBLE | PBS_SMOOTH ,
...

Ok, now you're creating a progress bar in WM_INITDIALOG, which is ok, but you're not saving the handle returned by create window so you can send messages to it. Sending messages to the dialog itself...

All the stuff to intialize common controls should be moved to your windmain function.

As it is now you are reintializing them every time a message is passed to your dialog proc.

Usually...