.RC dialogs and images limit!?

[JC]

Julio,

>In the second, the size of the executable will grow a lot.

Why is this a problem? The other way (using a DLL) the total size is probably similar (DLL + EXE). If you make any changes to the DLL you will still have to distribute the same size ZIP or install.

Regards,
James

James,

Yes, you are right! But my concern is the time to load a big executable in memory into machines with low memory.
I don't know... Still looking for a better solution... or choice!
Thanks james!

[JC]

Julio,

Personally I prefer to work with RC files, as they are ascii files that can be edited with a source code editor (to search, do replacements, copy and paste, etc.)

Antonio,

Many people say me the same solution. And splitting the .rc into several files apparently is the great choice!
My afraid is the size of executable when is load into memory... the time!

Thanks very much Antonio!

[Otto]

Harvey,

I am really curious about the answer you will get.
Regards,
Otto

[James Bott]

Julio,

The DLL also gets loaded into memory so there is still no size difference. When the RAM is not large enough, portions of the contents of the RAM are spooled out to disk and this will happen regardless of whether you are using a DLL and an EXE or just an EXE.

You really should recommend a certain size RAM as the minimum requirement for your application. Then if you have users without that minimum that are complaining about speed, you can refer to your requirements.

Regards,
James

[Antonio Linares]

Júlio,

Windows does not load the entire EXE in memory at once. It loads different blocks, as they are needed.

Also memory management is optimized with cache use, memory pagination to disk as James has explained, etc.