Menu
▾
▴
dev-cpp-users
|
From: Tim T. <ti...@tr...> - 2003-02-01 03:03:06
|
Thanks to Carlos (cgm1) for pointing out where to put default include directories. It works nice. Now, along with Ioannis' dev-cpp fix file I am moving right along. One issue came up that someone else might encounter - all of a sudden I started getting build errors complaining of an empty resource file. Apparently Dev-cpp just writes this file for some reason, most likely in response to something I did, but you can not compile until you simply delete this resource file again. Is that a bug or a feature? |
|
From: Ioannis V. <iv...@em...> - 2003-03-19 10:46:27
|
Hi guys & girls, I would be happy if someone answered to me regarding this: What exactly are resource files (binary or text) and what type of dialog boxes do they describe in Win32 API world? Regards, Ioannis Vranos * Programming pages: http://www.noicys.freeurl.com * Alternative URL: http://run.to/noicys |
|
From: Terry L F. <tf...@sm...> - 2003-03-19 11:02:12
|
Hello Ioannis, Wednesday, March 19, 2003 you wrote: IV> What exactly are resource files (binary or text) and what type of IV> dialog boxes do they describe in Win32 API world? A resource file contains a collection of icons, menus, dialog boxes, strings tables, and other stuff. For instance you might right click on an .exe file and be able to see the author, version, name, company, etc. This typically would be in a resource file. Likewise the icon associated with an .exe is there. The menus in an application or often defined in a resource file. Terry Fritts |
|
From: Louis G. <lg...@ya...> - 2003-03-19 13:35:47
|
On this same question, Are .res files optional or must they always be present in WIN32 API apps ? What is the advantage of having a menus etc. in the .res file and not in the .exe file? --- Terry L Fritts <tf...@sm...> wrote: > Hello Ioannis, > > Wednesday, March 19, 2003 you wrote: > IV> What exactly are resource files (binary or text) and what type of > IV> dialog boxes do they describe in Win32 API world? > > A resource file contains a collection of icons, menus, dialog boxes, > strings tables, and other stuff. > > For instance you might right click on an .exe file and be able to see > the author, version, name, company, etc. This typically would be in a > resource file. Likewise the icon associated with an .exe is there. > The menus in an application or often defined in a resource file. > > > Terry Fritts > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Does your code think in ink? > You could win a Tablet PC. Get a free Tablet PC hat just for playing. > What are you waiting for? > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com |
|
From: Zodiaq <zo...@ac...> - 2003-03-19 14:02:29
|
Hello Louis and all Dev-C++ users, Wednesday, March 19, 2003, 2:35:46 PM, Louis wrote as follows: LG> On this same question, LG> Are .res files optional or must they always be present in LG> WIN32 API apps ? Resource files are optional... LG> What is the advantage of having LG> a menus etc. in the .res file and not in the .exe file? The resource files I know ( .rc ) are compiled and linked into executable final file ( .exe)... The external "resource files" should be rather named as extra configuration files, not resource files... What are advantages of using .rc files for apps?? Here are few: -there are some editors to help you easly build them, and later maintain - make changes, add new ones... hmmm... for now only realy good one is the one that comes with Visual C++... after making some changes to .rc it adds few M$ related lines to code which you can later delete using text editor... for building new resources I prefer wedit (new version is integrated into lcc32 ide) but I had some difficulties to get it work with existing .rc... -you can EASLY make your app localized - very good example is eMule - her (http://www.emule-project.net/?s=downloads) you can find its FULL source, look at emule.rc :-) -when using resource files you can make fast changes to any messages that are passed to user - for example if I want to changes text passed through MessageBox I don't have to look thoughout my whole code, I need to find it my .rc -.rc files are (AFAIK) only places where app version, compilation date, company name etc. can be stored... you can later view it using "details" (right-click on file) under any Windows... DISadvantages: -dialog resources when using text editor are (very) hard to edit - you have to know EXACTLY where to place them on the screen (pixels) and what special properties they have... this is much harder then comparing WYSIWYG HTML editor to TEXT HTML Editors... -- regards, Zodiaq |
|
From: Per W. <pw...@ia...> - 2003-03-19 14:32:35
|
The xx.res file is just a middle step during the build of the application, just like the xx.o or xx.obj is an itermediate file for the source code. The last step in the linking will place the xx.res data into the xx.exe or xx.obj file. /Per W On Wed, 19 Mar 2003, Zodiaq wrote: > Hello Louis and all Dev-C++ users, > > Wednesday, March 19, 2003, 2:35:46 PM, Louis wrote as follows: > > LG> On this same question, > > LG> Are .res files optional or must they always be present in > LG> WIN32 API apps ? > > Resource files are optional... > > LG> What is the advantage of having > LG> a menus etc. in the .res file and not in the .exe file? > > The resource files I know ( .rc ) are compiled and linked into > executable final file ( .exe)... The external "resource files" should > be rather named as extra configuration files, not resource files... > > What are advantages of using .rc files for apps?? Here are few: > -there are some editors to help you easly build them, and later > maintain - make changes, add new ones... hmmm... for now only realy > good one is the one that comes with Visual C++... after making some > changes to .rc it adds few M$ related lines to code which you can > later delete using text editor... for building new resources I prefer > wedit (new version is integrated into lcc32 ide) but I had some > difficulties to get it work with existing .rc... > -you can EASLY make your app localized - very good example is eMule - > her (http://www.emule-project.net/?s=downloads) you can find its FULL > source, look at emule.rc :-) > -when using resource files you can make fast changes to any messages > that are passed to user - for example if I want to changes text passed > through MessageBox I don't have to look thoughout my whole code, I > need to find it my .rc > -.rc files are (AFAIK) only places where app version, compilation > date, company name etc. can be stored... you can later view it using > "details" (right-click on file) under any Windows... > > DISadvantages: > -dialog resources when using text editor are (very) hard to edit - you > have to know EXACTLY where to place them on the screen (pixels) and > what special properties they have... this is much harder then > comparing WYSIWYG HTML editor to TEXT HTML Editors... > > -- > regards, Zodiaq > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Does your code think in ink? > You could win a Tablet PC. Get a free Tablet PC hat just for playing. > What are you waiting for? > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > |
|
From: Terry L F. <tf...@sm...> - 2003-03-19 14:19:48
|
Hello Louis,
Wednesday, March 19, 2003 you wrote:
LG> Are .res files optional or must they always be present in WIN32
LG> API apps ?
Resource files are not necessary.
LG> What is the advantage of having a menus etc. in the .res file and
LG> not in the .exe file?
Resource files are embedded directly into an executable or dll and
then at runtime the program uses the resource data. So if data in
the resource file changes the program still has to be recompiled
to create the executable.
Typically you begin with a .rc file (Resource Compiler file) which
can be edited. The .rc file is then compiled into a .res file.
Some programming languages even have converters for .res files so
that you might use it in different application languages.
Microsoft has a dialog editor (DLGEDIT.EXE) that produces a .dlg
file which can be edited with any text editor and saved as a .rc
file. DLGEDIT.exe produces 16 bit binary .res files so normally
not usable in 32 bit applications. You can make a few changes to
the .dlg file, save it as .rc and then use dev-c++ to edit it.
You mainly just change the block in the .dlg:
DLGINCLUDE RCDATA FIXED IMPURE
BEGIN
"FILE.H\0"
END
to
#include "FILE.H"
But now if you want to change the ICON or menu strings, other
strings, or even other user-defined items you can do it in the .rc
file - recompile it to a .res file - and then recompile your
application. But you haven't had to touch your code.
Terry Fritts
|
|
From: Per W. <pw...@ia...> - 2003-03-19 14:34:05
|
Some resource editors allows you to edit the resources in situ. You just open an existing exe file - make my anoone - and translates... the resources and then saves them back to the exe file. /Per W On Wed, 19 Mar 2003, Terry L Fritts wrote: > Hello Louis, > > Wednesday, March 19, 2003 you wrote: > LG> Are .res files optional or must they always be present in WIN32 > LG> API apps ? > > Resource files are not necessary. > > LG> What is the advantage of having a menus etc. in the .res file and > LG> not in the .exe file? > > Resource files are embedded directly into an executable or dll and > then at runtime the program uses the resource data. So if data in > the resource file changes the program still has to be recompiled > to create the executable. > > Typically you begin with a .rc file (Resource Compiler file) which > can be edited. The .rc file is then compiled into a .res file. > Some programming languages even have converters for .res files so > that you might use it in different application languages. > > Microsoft has a dialog editor (DLGEDIT.EXE) that produces a .dlg > file which can be edited with any text editor and saved as a .rc > file. DLGEDIT.exe produces 16 bit binary .res files so normally > not usable in 32 bit applications. You can make a few changes to > the .dlg file, save it as .rc and then use dev-c++ to edit it. > You mainly just change the block in the .dlg: > DLGINCLUDE RCDATA FIXED IMPURE > BEGIN > "FILE.H\0" > END > to > #include "FILE.H" > > But now if you want to change the ICON or menu strings, other > strings, or even other user-defined items you can do it in the .rc > file - recompile it to a .res file - and then recompile your > application. But you haven't had to touch your code. > > > Terry Fritts > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Does your code think in ink? > You could win a Tablet PC. Get a free Tablet PC hat just for playing. > What are you waiting for? > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en > _______________________________________________ > Dev-cpp-users mailing list > Dev...@li... > TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users > |
|
From: Per W. <pw...@ia...> - 2003-03-19 19:00:36
|
Sorry, I should try to proof-read before sending :-)
/PWM
On Wed, 19 Mar 2003, Per Westermark wrote:
> Some resource editors allows you to edit the resources in situ. You just
> open an existing exe file - make my anoone - and translates... the
------------------------->made by anyone
> resources and then saves them back to the exe file.
>
> /Per W
>
> On Wed, 19 Mar 2003, Terry L Fritts wrote:
>
> > Hello Louis,
> >
> > Wednesday, March 19, 2003 you wrote:
> > LG> Are .res files optional or must they always be present in WIN32
> > LG> API apps ?
> >
> > Resource files are not necessary.
> >
> > LG> What is the advantage of having a menus etc. in the .res file and
> > LG> not in the .exe file?
> >
> > Resource files are embedded directly into an executable or dll and
> > then at runtime the program uses the resource data. So if data in
> > the resource file changes the program still has to be recompiled
> > to create the executable.
> >
> > Typically you begin with a .rc file (Resource Compiler file) which
> > can be edited. The .rc file is then compiled into a .res file.
> > Some programming languages even have converters for .res files so
> > that you might use it in different application languages.
> >
> > Microsoft has a dialog editor (DLGEDIT.EXE) that produces a .dlg
> > file which can be edited with any text editor and saved as a .rc
> > file. DLGEDIT.exe produces 16 bit binary .res files so normally
> > not usable in 32 bit applications. You can make a few changes to
> > the .dlg file, save it as .rc and then use dev-c++ to edit it.
> > You mainly just change the block in the .dlg:
> > DLGINCLUDE RCDATA FIXED IMPURE
> > BEGIN
> > "FILE.H\0"
> > END
> > to
> > #include "FILE.H"
> >
> > But now if you want to change the ICON or menu strings, other
> > strings, or even other user-defined items you can do it in the .rc
> > file - recompile it to a .res file - and then recompile your
> > application. But you haven't had to touch your code.
> >
> >
> > Terry Fritts
> >
> >
> >
> > -------------------------------------------------------
> > This SF.net email is sponsored by: Does your code think in ink?
> > You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> > What are you waiting for?
> > http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> > _______________________________________________
> > Dev-cpp-users mailing list
> > Dev...@li...
> > TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> > https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
> >
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Does your code think in ink?
> You could win a Tablet PC. Get a free Tablet PC hat just for playing.
> What are you waiting for?
> http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
> _______________________________________________
> Dev-cpp-users mailing list
> Dev...@li...
> TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm
> https://lists.sourceforge.net/lists/listinfo/dev-cpp-users
>
|
|
From: <qa...@ho...> - 2003-02-01 08:12:32
|
Hi. I think I know why the empty resource file is created and I concider it a= bug. In 'Project'->'Project Options'->'Version Info' you have checked AND= unchecked the 'include version...' This makes the compiler complaint: [Resource Error] no resources /J=F6rgen *********** REPLY SEPARATOR *********** On 2003-01-31 at 22:03 Tim Trischuk wrote: >Thanks to Carlos (cgm1) for pointing out where to put default include >directories. It works nice. Now, along with Ioannis' dev-cpp fix file I >am >moving right along. > >One issue came up that someone else might encounter - all of a sudden I >started getting build errors complaining of an empty resource file. >Apparently Dev-cpp just writes this file for some reason, most likely in >response to something I did, but you can not compile until you simply >delete >this resource file again. Is that a bug or a feature? > > > >------------------------------------------------------- >This SF.NET email is sponsored by: >SourceForge Enterprise Edition + IBM + LinuxWorld =3D Something 2 See! >http://www.vasoftware.com >_______________________________________________ >Dev-cpp-users mailing list >Dev...@li... >TO UNSUBSCRIBE: http://www.noicys.cjb.net/devcpp/ub.htm >https://lists.sourceforge.net/lists/listinfo/dev-cpp-users @ |
