The MASM Forum Archive 2004 to 2012

Project Support Forums => MASM32 => Topic started by: hutch-- on March 20, 2011, 01:32:04 AM

Title: Later memory dialog update.
Post by: hutch-- on March 20, 2011, 01:32:04 AM
With special thanks to Erol, Ramon Sala and JJ for testing prototypes on non-US English versions that I don't have access to, I have attached a zip file that contains a later version of the DIALOGS.INC file that contains 2 new macros for respectively ICONS and BITMAPS where the 4 XY parameters are used and the centered flag is set. I have also added a toolbar macro that should have been there before.

The CHM help file has been updated to reflect changes with a section on MANIFEST files, changes to the technique to initialise the common control library and the addition of the extra controls.

The ZIP file also has a small template generator that creates the source file, RC file and manifest file so that starting a simple memory dialog in source code is fast and easy to get going.
Title: Re: Later memory dialog update.
Post by: dedndave on March 20, 2011, 02:58:25 AM
looks great Hutch
i like the CHM file - even if it is 28131 bytes   :lol

couple questions...
how do you make the CHM files
how would i bring up a CHM file from a menu item
can the CHM be included as a resource of some sort ?
is there a way, other than via a resource file, to load a manifest in the PE - or is that the nature of the beast
Title: Re: Later memory dialog update.
Post by: hutch-- on March 20, 2011, 03:42:24 AM
Dave,

You dwnload the Microsoft CHM help compiler, (a geniune pig to use) and use a HTML editor to make the pages. I use the freeware Komposer. CHM is a file format that the Windows html help engine runs so you could add it as a binary resource but you would have to write it to disk first.

Interestingly enough you can do it the other way around, embed your EXE in the CHM file and when the user wants your binary they just "download" it from the CHM file.

ShellExecute() will call a CHM file so you just have to provide the correct path.

You can do a manifest file as a separate text file named in this manner.


yourapp.exe
yourapp.exe.manifest


I prefer to embed it in the resource section

http://msdn.microsoft.com/en-us/library/ms669985(v=VS.85).aspx
Title: Re: Later memory dialog update.
Post by: Vortex on March 20, 2011, 10:03:06 AM
Hi Hutch,

Thanks for the update. It works fine but there is a minor issue. The target folder name is not displayed correctly if it's too long. Could you check the attached file?
Title: Re: Later memory dialog update.
Post by: hutch-- on March 20, 2011, 10:09:14 AM
Thanks Erol, I will make it longer.

See if this handles a long enough path. It is limited to 256 characters but I don't know if thats the problem.
Title: Re: Later memory dialog update.
Post by: dedndave on March 20, 2011, 10:39:59 AM
thanks Hutch   :U
Title: Re: Later memory dialog update.
Post by: Ramon Sala on March 20, 2011, 11:50:09 AM
OK, it works fine now!

Thanks Hutch!
Title: Re: Later memory dialog update.
Post by: Vortex on March 20, 2011, 06:31:17 PM
Hi Hutch,

Thanks, it works fine.