PBWin IDE and PBForms "feature"

[Bob Clarke]

Just to get this off my chest.
Using PBWin 9.01 and PBForms 1.51.
1)
Doing modular programming with several *.bas files.
IDE 'set primary source file' gets wiped out every time
I use the PBForm editor.
Very frustrating!
2)
From Help 'Converting a .RC to a .RES'
Once configured, the IDE can automatically compile a .RC into a .RES file, and then produce a .PBR file from the .RES file.
This is achieved in one simple step:
simply load the .RC file into the IDE and select Compile.

oh no it won't

[Michael Mattias]

Once configured, the IDE can automatically compile a .RC into a .RES file, and then produce a .PBR file from the .RES file.
This is achieved in one simple step:
simply load the .RC file into the IDE and select Compile.

oh no it won't

Oh yes it will.... ONCE CONFIGURED.

The user interface when either step f(RC=>RES, RES=>PBR) fails is crummy, but once it is set up it works just fine.

[Rodney Hicks]

Is your primary source file a .pbp file?
The project file was not around when PBForms 1.51 was created, and thus files of that type may not be supported.

[Cliff Nichols]

Personally I use 1 *.bas
and many *.inc files

That way you are never left wondering if the *.bas was meant to be run? or a part of a bigger program?

[Bob Clarke]

Michael,
Then configuring it correctly eludes me.
Take /samples/sdk/skeleton.rc
and place it in an empty directory.
Open in IDE and press compile.
Bang its a microsoft report.

Rodney, nope see above.

Cliff,
I acually make my code so compartmentized that each .bas modul
can be compiled and run alone.
#IF %ALONE
FUNCTION PBMAIN() AS LONG
#ELSE
FUNCTION EDITCSVMAIN() AS LONG
#ENDIF
This really isolates problems.
I'm prone to make mistakes and have to debug.

[Kev Peel]

The RC file is basically a list of resources to include in a compiled resource (RES, PBR). You have to copy the other files referenced in the RC file as well or it won't compile. For the skeleton sample, you also need toolbar.bmp and skeleton.ico

[Michael Mattias]

Good example of crummy user interface when either step fails.

Why PBRES fires off when RC.EXE fails eludes me. Probably has something to do with the fact that RC.EXE is a 16-bit application and the 32-bit IDE can't detect the return code.

You might have an easier time of it compiling your resources OUTSIDE the IDE.

I think I have a batch file I used to use, let me look...nah, I can't find it.


Anyway it would be something like
FROM COMMAND PROMPT,

C:\MyFolder> start cores.cmd  basefilename

The command file:

REM  file cores.cmd 
[path]RC.EXE   %1%
IF NOT ERRORLEVEL 1  DO [path]PBRES.EXE %1%

That's close, anyway. Play with it.

MCM

[Bob Clarke]

Ok thanks

Now I know what I didn't know.
Would have prefered an error message from the compiler.
" can't compile this you dummy, missing included file xxx.yyy"