請問一下各位先進,要如何把icon包在dll和exe檔中呢?可否寫一範例?謝謝

引言: 請問一下各位先進,要如何把icon包在dll和exe檔中呢?可否寫一範例?謝謝

可不可以詳述您的需求呢

引言: 請問一下各位先進,要如何把icon包在dll和exe檔中呢?可否寫一範例?謝謝

JS 你好:
據小弟我所知，應該至少有三種方法吧
(1)使用 TImageList，把你要用到的 Icon 放在裡面
(2)在你的 BCB 開發環境下按 Tools/Image Editor 然後載入 Project 的 res
   檔案，把你要用到的 Icon 加入
(3)利用 VC   或其他的 RC 編輯工具，把你要用到的所有 Icon 放到一個 RC
   檔案裡面，然你的 Project 再 add 這個 RC 檔案即可

-- Enjoy Researching & Developing --

我是想知道如何將許多的icon包在dll或exe file中,就如同windows系統本身或一些應用程式對小圖示的處理方式一般並在註冊檔中的Subkey->DefaultIcon 指定字串如下: Default REG_SZ C:\PROGRA~1\ACDSEE32\ACDSEE32.EXE,4

JS您好:

方法一.
     可用TimageList元件將Icons加入到ImageList中,C   Builder中很多元件
都有支援ImangeList,這個方法在Dll或EXE中皆適用    方法二.
      可使用Resource File將所需的Icon/Image/Wave/EXE....等等檔案加進Resource檔案然後含括在DLL或,中其作法參考如下:

Using Borland’s C Builder to create

Resource DLLs by Jean-Pierre Martel, editor of the dBulletin 資料來源:http://www.dbase.com/Knowledgebase/dbulletin/bu15cb.htm -------------------------------------------------------------------------------- Introduction In a previous article, we saw how to use Borland's Resource Workshop to store images (icons and BMPs, exclusively) in a DLL. Unfortunately, as soon as the number of resources stored in a DLL created by Resource Workshop gets around 30, dBASE chokes on some of them. The images can be seen and selected when one tries to datalink a control to a resource. However, as soon as the OK button is pushed, an error message appears saying that the resource can't be found. In our 13th issue, Dan Howard wrote an article on how to use Borland's free C Compiler to create a resource DLL. Of course, what's possible with the compiler is also possible with the full application. In the present article, we will use version 4.0 of Borland's C Builder. The complete version of that application was given for free with the May 2000 issue of the PC Plus (anUK magazine). For those who missed the occasion, I wouldn't be suprised if Borland would repeat the experience in the future. To create a resource DLL, there is only one prerequisite: we need a .RC resource file. A .RC file is just a special ASCII file in which the names of the images to be included in the DLL are listed. Since the main module of that compiler is a DOS executable, the short name of the images must be used in that .RC file. To create a resource DLL, load C Builder. Select the menu item File|New… then, in the New Items dialog box, select the Console Wizard icon (not the DLL icon) and click the OK button. In the Console Application Wizard dialog box, select the DLL radiobutton and click the Finish pushbutton. C Builder will open a new floating Windows called “ProjectX” (“X” being the number of the Project). Select the menu item Project|Add to Project…. At the bottom of the Add to project dialog box, there is a combobox: select the item Resource files (*.rc) in order to display the .RC files. Go to the appropriate folder and select your .RC file. The line USERC("PathName\ResourceFileName.rc"); will be added to the C code. Click the Open pushbutton. Select the menu item Project|Build Project: a new DLL that bears the same name as your Project will be created. That DLL will be located in \Projects sub-folder (one of the C Builder sub-folders). Conclusion dBASE is completly unable to create DLLs. C Builder fill that gap and completes very well dBASE. Contrary to Borland's Resource Workshop, C Builder can store a large number of images in a resource DLL and is not limited to .ICO and .BMP files. -------------------------------------------------------------------------------- HAVE A NICE DAY FOR YOU 發表人 - axsoft 於 2003/06/13 09:25:36

axsoft 桑你好！ 看到你圖文並茂解說，覺得你很用心。 小弟公司最近需要撰寫產品說明書， 所以想要請教你，在你的圖片中的數字， 紅色圈圈中間有數字的這種表示方法很棒， 不知道是用哪一種應用軟體做出來的呢？ 小弟想要提昇台灣軟體產品說明書的品質！ 讓國際了解我們台灣也是很棒的！

How to hide BMPs and icons in a DLL using Borland's

Resource Workshop

by Jean-Pierre Martel, editor of the dBASE Developers Bulletin 資料來源:http://www.dbase.com/Knowledgebase/dbulletin/bu09rw.htm -------------------------------------------------------------------------------- Introduction When the dBASE Scan Center was released (with our seventh issue), most of its pushbuttons needed custom-made BMPs since these buttons performed actions rarely done by standard dBASE applications. Thus the original version of the Scan Center came with about 30 BMPs. When I started making a shareware version out of it, I wanted to hide all these images inside a DLL. The only tool available to dBASE developers is Borland's Resource Workshop (RW). This 16-bit application can't create DLLs, but it is useful to create or add resources in an existing 16 bit or 32 bit DLL (note: VdB 5.x uses 16-bit DLLs while VdB 7.x uses 32-bit DLLs). If you don't have RW, you can buy the 4.5 version (the same version as the one included with the VdB 5.5 compiler) for 70 US$ from Borland or get it for free from the CD-ROM provided by some computer magazines. It was given with the May 2000 issue of the UK magazine 'PC Plus'. An alternative solution is Resource Builder by SiComponents which is more stable (Dan Howard, personal communication). In a previous issue of the magazine, Robert Bravery explained how to use RW to add string resources to a DLL; here we will see how to add images. Contrary to Resource Builder, BMPs and ICOs are the only images that RW can store in a DLL. Since I wanted as few as possible images left in the Scan Center directory, I applied different solutions to different image types. Thanks to a suggestion by Romain Strieff, one of the GIFs had its suffix renamed to '.sca'. Strangely, form.background = "filename cpyright.sca" will be executed without any problem. How dBASE can know that it is a GIF is a mystery to me. But it works, so who cares? The other GIFs were buried in the binary fields of a table (dScan.dbf). An icon and about thirty BMPs were the only images left to hide in the DLL. A minefield The RW should work fine if you follow strictly the thin path that I will suggest to you. There may be other ways to make a 32-bit DLL out of BMPs, but I couldn't find another. Each time I tried shortcuts, my well-know patience was severely challenged… Among its bugs, RW has a tendency to make a copy of each BMP (under a .~BM suffix) and screw the original. So:

  for i = 1 to 1000000 
    my_advice = "Never use RW on the only existing copies of your BMPs" 
  next 
  replicate("Never",10) 

1 — The first step is to create a new folder. 2 — The second step is to copy all the BMPs that have to be included in the DLL in this new folder. Since RW can't create a new 32-bit DLL, you will need an empty one. You may ask: “Where in the World can you find an empty DLL?” The answer: where else than in Ken Mayer's dUFLP (under EmptyRes.zip). Actually, we will use two empty DLLs (Empty.dll and Empty32.dll), both made by Bowen Moursund. To make things easier, they can be downloaded from a link at the end of this article. 3 — Copy Empty.dll and Empty32.dll to the folder you have just created. 4 — From the Explorer, right-click on each of them and select “Properties” to take off of their read-only property. If you don't, RW will refuse to add new images to them. 5 — Optional: Rename Empty.dll to MyApp.dll, and Empty32.dll to MyApp32.dll (the name of your application). 6 — Run Resource Workshop. 7 — Follow these instructions to open MyApp.dll — the 16-bit one — even if your goal is to create a 32-bit DLL: From the File menu, select 'Open project…'. The first time you are using RW, the combobox displays 'RC resource script' as the file type by default. Use the combobox to select 'DLL, VBX, CPL library' as illustrated in the image below. In the lower right rectangle, double-click on the appropriate drive and folder until you get to the folder where you stored the DLL created in the first step. Select 'MyApp.dll' in the lower left rectangle and click the OK button. 8 - Load M$ Explorer. Select all the BMPs (and only the BMPs) you would like to add to your DLL. Drag'n drop them in the left pane of RW. Note: I was not very lucky while I tried to add both BMPs and ICOs at the same time in a 32-bit DLL. I could add them in the 16-bit DLL, but when I tried to transfer them to the 32 bit DLL, it was impossible to save the latter without crashing. My suggestion would thus be to add only BMPs for now. 9 — For each of these image files, you will have to confirm that you want to add it to the 'project' (i.e.— to the DLL). By default, RW will numbered each resource consecutively (bitmap_1, bitmap_2, etc.). 10 — Optional: At this point, you might want to rename the resources (from the Resource menu: Rename…), but if you have a lot of them have to be renamed, it is easier to edit the resource script file that we will create next. If your goal was to make a 16-bit DLL, that's it for now. Save and jump to the section called “Adding icons to the DLL”. 11 — Once your images have been added to MyApp.dll, create a Resource script file: a) From the File menu: Save file as… b) In the combobox, select the item: RC resource script. c) In the 'New file name' entryfield at the top of the dialog box, give it a name (here, 'myapp.rc'). d) Click the OK button. With Explorer, if you give a look at the folder where your BMPs are stored, RW has just screwed up all your images. Since you knew it in advance, you couldn't care less. 12 — Optional: The resource file you have just created is a simple ASCII file. If you want to rename your resources, load 'myapp.rc' in an editor (for example, Notepad) and do it. Personally, I like to give to each resource the name of its corresponding BMP. So I just copy and paste the name of the image (without its suffix!). Don't reorder since your resources will always be displayed in alphabetic order whatever you do. Save the resource file. 13 — Load MyApp32.dll in RW. It contains only an icon called 'Do_not_delete'; don't touch it since it seems to be necessary to permit the RW to produce a DLL compatible with VdB7. 14 — From the File menu, choose 'Add to project…' and select the resource script 'myapp.rc' in the lower left rectangle. Click the OK button. In a flash, all your images will be added to the 32-bit DLL. Save the DLL. Adding icons to the DLL 15— Load the 32-bit DLL again (or the 16-bit one if you are a VdB 5.x user). From the Explorer, drag'n drop each icon in the left pane of RW. Rename the new icon resources, if you want (from the Resource menu: Rename…), and save the DLL. Using bitmaps from a DLL 16 — Set the bitmap properties of the controls to be linked to your 32-bit DLL: a) From the Property Inspector, click the wrench at the right of the property to be changed (step #1, below). b) The Bitmap Property Builder dialog box will offer a filename to choose by default in VdB 7.x. (In VdB 5.x, this dialog box will offer a resource by default.) Open the 'Location' combobox to select a resource (step #2), and click the wrench tool at the right of the 'Bitmap' entryfield (step #3). c) In the 'Choose Resource Image' dialog box, click the wrench at right to select another DLL (step #4). d) Change to the drive where your DLL is located (step #5), select it (step #6), and click the 'Open' pushbutton (step #7). e) You will be back to the 'Choose Resource Image' dialog box (seen in c). Select the resource you want (step #8), and click the OK pushbutton (step #9). f) You will be back to the Bitmap Property Builder dialog box (seen in b). Click the OK pushbutton. Unfortunately, for each bitmap property you will have to go through all these steps since dBASE will always offer to link your bitmap property to a filename, then Resource.dll as the default DLL. In my case, this process was easier because all the bitmap properties were already linked to a filename that carried the same name as the resource bitmap. So I just had to use the Code editor to change: upBitmap = "filename b_garbag.bmp" to upBitmap = "RESOURCE b_garbag dScan32.dll" If you have a lot of changes to make, you can “seek and replace” to edit your code. If you must add a few new resources, the Code editor can be used to edit the Resource script. One good point about editing the Resource script (and renaming your resources) is that you don't run the risk that your bitmaps will carry different resource numbers and will be displayed at the wrong place in your application if you have to make your DLL anew. Finally, when you use numbers to name your resources, in your code the sign “#” must precede that number, for example: upBitmap = "RESOURCE #12 dScan32.dll". Pitfalls Among the BMPs stored in the DLL that I made for dBASE Scan Center, there was an image resource that I was unable to use. In RW the bitmap resource could be seen. In dBASE it was even displayed in the "Choose Resource Image' dialog box (step #4). So the image was not corrupted (it could be seen in Photoshop and in QuickView). In the Form designer, I could select it without receiving any warning whatsoever. Yet, when I ran the form, I got an error message: “Resource not found: b_garb_d”. I tried every solution possible, but my efforts were in vain. If ever something similar also happens to you, stay calm. Don't argue with dBASE (you will loose). Just copy the image file under a different name, add this name to your Resource script, and, from the latter, import your BMPs into a new empty 32-bit DLL. Whatever the version you are using, the Form designer will not allow you to select an icon resource when there is only one in the DLL; in the previous image, the “step #9” OK button is then disabled. But if the DLL contains at least two icon resources, the OK button is enabled. Under VdB 5.x, the Form designer can thus be used to link an icon property to an icon resource from any 16-bit DLL which contains at least two icons. Under VdB 7.x, you can use the Form designer to link an icon property to a filename or to an icon resource from Resource.dll. If you try to link that property to an icon resource from another DLL, you will get an error message similar to this one: Actually, you can link that property to an icon resource, but not with the Property inspector. Thanks to Jørgen Feder, I learned that you can do it with the Code editor. In the form constructor code, add icon="RESOURCE Resource_name dll_name.dll", and this line will work fine when your form is run. Conclusion The Resource Workshop is one of the rare tools available to hide bitmaps inside a DLL. This rather buggy 16-bit software was not updated by Borland in recent years; the version still distributed today is the same one included years ago with the VdB 5.5 compiler. It can be very handy if you have the patience to tolerate its crashes and adhere strictly to a safe methodology. To download Bowen Moursund's DLLs, click here (they are inside a 62Kb zipped executable file) To download the new VdB7 version of the Scan Center, click here (it is inside a 154Kb zipped executable file) -------------------------------------------------------------------------------- This article was based on the instructions Bowen Moursund wrote for the users of his empty DLLs. I would like to thank him for allowing me to make these DLLs available here. Also I would like to thank Flip Young, my proof-reader, and also Rainald Taesler, Dan Howard and Jørgen Feder for their help in preparing this article. HAVE A NICE DAY FOR YOU 發表人 - axsoft 於 2003/06/13 12:06:41

Creating Resource DLLsh2 for dB2K

by Dan Howard 資料來源:http://www.dbase.com/Knowledgebase/dbulletin/bu13dll.htm -------------------------------------------------------------------------------- Introduction dB2K is a rich and powerful software but one utility it sadly lacks is a resource builder. Back in the days of 16 bit dBASE we had Borland’s Resource Workshop. This was a good product and worked well for 16 bit development but it has some shortcomings in the 32 bit world. Unfortunately this product has problems when you try to save your work in a 32 bit format. Either the dll simply won’t work at all or worse - it will make your application become unstable. The good news is that there is an excellent shareware 32 bit resource builder out there called Resource Builder. It can be downloaded from the following URL: http://www.sicomponents.com/. The author, Igor Siticov is very helpful with question about the product. Resource builder also supports JPEG files which is very useful. The only downside to Resource Builder is that it works with RC (resource script) files. These are simple ASCII files which describe the resources in text format. Although Resource Builder allows you to compile your resource files in to RES files, it does not go that extra step and make the DLL for you. Fortunately there is a solution to this. To make the DLL we’ll need the help of Borland’s free C++ compiler. Borland recently released it core C++ compiler to the public for free. This is a bare bones software. No GUI, no drag & drop, only a DOS command line interface but it’s fully functional and can be used to write any C or C++ program you want. It can be downloaded from this URL: http://www.borland.com/bcppbuilder/freecompiler/. Once you’ve download this fairly hefty file (8 meg!) install it on your computer. I normally install it to c:\borland\bcc55 but you can specify other locations if you want but be careful not to use paths with spaces. In the install folder is a readme.txt file. This contains some configuration instructions which I’ll review for you. Configuring Borland C++ Borland’s compiler requires only a few settings to get it to work. First you’ll need to set the path to the compiler itself. This will be in the BIN folder where you installed it. If you’re using Windows 9x you have to set this in your autoexec.bat file and then reboot. The entry might look like this: PATH=C:\WINDOWS;C:\WINDOWS\COMMAND;C:\Borland\BCC55\BIN For Windows NT or 2000 you can set the path by modifying the system environment variables. Right click on “My Computer” Choose “Properties” Choose the “Advanced” Tab Click “Environment Variables” You should see something like: Look under the System Variables for a entry called Path and click edit. At the end of the path string enter: ;c:\borland\bcc55\bin // Notice the semi-colon. That's important. Once this is done you’ll be able to run the compiler from any directory on your computer. The next thing we have to do is create 2 configuration files. One for the compiler and one for the linker. In Borland’s readme file is a sample of these files. These can be created using any text editor like notepad or the dBASE program editor. First we’ll create a file for the compiler. This file needs 2 entries. Open up a new file and enter this: -I"c:\Borland\Bcc55\include" -L"c:\Borland\Bcc55\lib" Make sure that the paths are the same as where you installed the compiler. These 2 lines will tell the compiler where to find it’s include and library files. Save this file as bcc32.cfg in the BIN folder. Next we’ll create a file for the linker. This needs only a single entry: -L"c:\Borland\Bcc55\lib" Again make sure that the paths are the same as your install. This tells the linker where to find any library files it will need. Save this file as ilink32.cfg in the BIN folder. Creating a DLL from an RC file Once Borland’s compiler is installed we’re ready to create our resource dlls. Included with this article is a batch file I wrote which will make building DLLs very easy. All you have to do is save this file into the BIN folder and run it whenever you need to. All you’ll need is an RC file created with either Resource Builder or Resource Workshop and then from the DOS prompt: MAKEDLL myresourcefile Notice that you don’t specify an extension. This will run the compiler and the linker and produce a DLL in the same folder as your RC file. How it works Creating a DLL is a 2 step process. First the compiler has to compile the RC file to convert into a binary (RES) format and then the linker has to link that binary file into the final DLL. To compile the RC file, use the command: brcc32 -FOmyresource.res myresource.rc The compiler takes 2 parameters, -FO tells the compiler what the output file name will be — in this case myresource.res. The second parameter is the input file that will be compiled. This would be your resource script file. Once this command runs you’ll have a compiled version of your resource file saved in the same folder as your script file. We’re half way there now. All we have to do is link this file to make the DLL. To link the RES file into a DLL, use this command (watch word wrap. this should all be one command): ilink32 -Tpd -aa -V4.0 -c -x c0d32.obj, myresource.dll , ,import32.lib cw32i.lib, ,myresource.res The linker is more complex and takes several parameters.

  Parameter          Meaning 
  -Tpd               This tells the linker the type of file you want
                     to create. You can use -Tpe to create an exe. 
  -aa                This tells the linker that this will be a 32 
                     bit Windows application. 
  -V4.0              This specifies the target Windows version that
                     this DLL will be used for. 
                     4.0 represents Windows 95 and later. 
  -c                 This tells the linker that you want case sensitive symbols.  
                     I'm not sure that this is critical but since C 
                     is case sensitive it's a good idea to include it. 
  -x                 This suppresses the creation of a MAP file. 
                     A MAP file is a text file which list all the 
                     memory locations of the symbols of a C program.
                     Since this is simply a resource file we're 
                     making, it's not that useful to have a MAP 
                     file. 
  c0d32.obj          This object file is required to link into the
                     dll. It allows the DLL to be loaded into memory 
                     only when needed. 
  myresource.dll     This is the output DLL file that will be 
                     created. 
  import32.lib and cw32i.lib  These libraries are needed for the DLL. They're used to access the Windows API. 
  myresource.res     This is your compiled RES file that will be linked. 
      

Notice in the command line that there are items seperated by commas. One part of the command line has 2 commas with nothing in between. This part of the command line is for dependency files (.DEP) which we don’t need for a dll. Conclusion Well, I hope this helps you with building your own dlls. I think you’ll find that a C compiler can be very useful for you and fun to experiment with! To download the code of the MakeDLL batch file, click here (it's a 306 byte zipped file) -------------------------------------------------------------------------------- Note: The author would like to thank John Staub, his proof-reader, for the improvements he brought to this text. About the Author: Dan Howard is an independent software developer and a member of dBVIPS. You can usually find him lurking around the dBASE newsgroups. HAVE A NICE DAY FOR YOU 發表人 - axsoft 於 2003/06/13 10:20:01

引言: axsoft 桑你好！ 看到你圖文並茂解說，覺得你很用心。 小弟公司最近需要撰寫產品說明書， 所以想要請教你，在你的圖片中的數字， 紅色圈圈中間有數字的這種表示方法很棒， 不知道是用哪一種應用軟體做出來的呢？ 小弟想要提昇台灣軟體產品說明書的品質！ 讓國際了解我們台灣也是很棒的！

BGman您好: 您可以試試SnagIt v6.22可以達到您要的功能,但如果真的要像上頭這麼漂亮建議用Ulead PhotoImpact或Adobe PhotoShop來做 http://www.techsmith.com/products/snagit/default.asp HAVE A NICE DAY FOR YOU 發表人 - axsoft 於 2003/06/13 11:43:00

謝謝大家的熱情回應,不過可否問一個笨問題啊!如果我做好一個包含icon的dll或exe file,那我該如何使用其它的應用程式去取用它呢?

引言: 謝謝大家的熱情回應,不過可否問一個笨問題啊!如果我做好一個包含icon的dll或exe file,那我該如何使用其它的應用程式去取用它呢?

JS 你好: 你可以利用 Win32 API Resource Functions 達到目的 LoadLibrary, LoadLibraryEx, FindResource, FindResourceEx, LockResource, LoadResource, FreeLibrary,....... http://delphi.ktop.com.tw/topic.php?TOPIC_ID=22599 -- Enjoy Researching & Developing --

感謝 axsoft 桑的協助！ 上網看了一下介紹功能真的很不錯， 已經寫申購單去申請這個軟體了！ 小弟，感激不盡！