| T O P I C R E V I E W |
| Mike Buess |
Posted - 12/20/2001 : 4:37:28 PM
An ealier discussion (tool is open) raised a question about Dialog Builder methods. I have created nine DB dialogs for an application I'm working on and I wonder now if it's better to put them all in a single DLL or to build a separate DLL for each. (I've already done the latter, so I hope that's the answer.  ) Aside from saving a few kB, are there any advantages to combining DB dialogs?
Mike Buess
Origin WebRing Member |
| 2 L A T E S T R E P L I E S (Newest First) |
| Mike Buess |
Posted - 12/21/2001 : 6:02:13 PM
Hi Laurie,
Thanks for the comments and advise. I tried to combine three of my dialogs and soon found that the String table can indeed be a bear. I started with an empty project, copied the simplest dialog (IDD_) and its string table, then copied the other two dialogs with the intention of adding them to that string table. I soon ran into duplicate ID's and values and, while I'm sure that could eventually be sorted out, I'm not so sure that it's worth the effort. Since you say there's only a slight benefit in performance I'll probably stick with what I've got.
Thanks again and Merry Christmas!
Mike Buess
Origin WebRing Member |
| Laurie |
Posted - 12/21/2001 : 4:47:49 PM
Hi Mike,
Here's the pros and cons of each method.
One DLL Advantage:
1) Smaller size
2) If all the dialogs are almost always used -- fewer number of dll's loaded
Disadvantage:
Maintenance difficulty -- too many entries in the String table easy to make mistake when changing
Multiple dll: Just the opposite.
There can be a slight benefit in performance if all your dialogs for one application are in one DLL. However, searching entries from a big list in the string table from the resource editor might not be much fun and could lead to errors (as well as the wizard to create dialogs can't be used when adding a new dialog), under such circumstances a multiple DLL approach might be beneficial.
OriginLab Technical Support |
|
|
