FiveTech Support Forums

FiveWin / Harbour / xBase community
Board index FiveWin for Harbour/xHarbour Pelles C resource editor
Posts: 2706
Joined: Fri Oct 07, 2005 01:50 PM
Pelles C resource editor
Posted: Wed Nov 22, 2006 01:31 AM

To All

Just received my RTM Vista Business version and quickly found that Borland's Resource Editor will NOT run...

I have downloaded SI Componants resource editor .. and Pelles C IDE. I am not too thrilled with either ..

One of the most anoying problems with Pelles C IDE is when you create a form (.rc ) the editor places header include files in the .rc

// RESOURCE SCRIPT generated by "Pelles C for Windows, version 4.50".

include <windows.h>

include <commctrl.h>

include <richedit.h>

LANGUAGE LANG_ENGLISH,SUBLANG_ENGLISH_US

COMPANY DIALOG DISCARDABLE 34, 26, 329, 305
STYLE WS_POPUP|DS_SYSMODAL|DS_3DLOOK|WS_CAPTION
FONT 8, "Arial"

My question .. is there a way to configure the Pelles C IDE to 'turn off' the insertion of the #include lines ??

Rick Lipkin
SC Dept of Health, USA

Posts: 2706
Joined: Fri Oct 07, 2005 01:50 PM
Pelles C resource editor
Posted: Wed Nov 22, 2006 02:10 AM

To All

Found out a way to run Borland Workshop in Vista RTM .. you can NOT open Workshop with File and drill to your form .. Workshop will 'barf' .. but you can click on the .rc file and tell it to open with Resource workshop and it let Workshop open and Edit your resource file ..

Still not a good solution .. you can not create a new form .. have to right click and 'open with' Workshop to use this 'hack' ..

Still, I would like to find a better solution !

Rick Lipkin
SC Dept of Health, USA

Posts: 44158
Joined: Thu Oct 06, 2005 05:47 PM
Pelles C resource editor
Posted: Wed Nov 22, 2006 07:57 AM

Rick,

You may use PellesC with your RES file, not with your RC file.

regards, saludos

Antonio Linares
www.fivetechsoft.com
Posts: 824
Joined: Thu Oct 13, 2005 07:39 AM
Pelles C resource editor
Posted: Wed Nov 22, 2006 09:25 AM

Rick,

I use PellesC without problems, also with rc-files. You have just to add an includepath in the brc-command:

%C_BIN_INSTALL%\Brc32.Exe -r -iD:\PellesC\include;D:\PellesC\include\win -fo%RES% %RC%

The includes are needed to resolve the #defines PellesC uses.

Finally there are two issues to solve, PellesC uses DIALOGEX instead of DIALOG and MANIFEST instead of 24. You can solve this by using another includefile (<name_of_the_resourcefile>.h) in your projectdir with this content:

// INCLUDE FILE generated by "Pelles C für Windows, Version 4.00".

define MANIFEST 24

define DIALOGEX DIALOG

Stefan

kind regards

Stefan

Continue the discussion