🚀 go-pugleaf

Currently, I have BC++ 5.02, which I think was the last BC++
before "Builder" right?

I'm running into problems using it without the latest import
libraries and #include files, especially for things like
comctl32.dll, which seems to gain new features every month.

I got a copy of the latest commctrl.h file from someone with
VC++, but it's a completely different file from the one supplied
by Borland. It has lots of MS-specific stuff in it and none of the
BC++ specific stuff.  I cut/pasted in a few of the LVS_EX_
#defines, but there's lots of other stuff I'm afraid to touch.

When I use LVS_EX_CHECKBOXES in my .rc file, the RC
can't find that value, even though it's in the commctrl.h file now.
I figured the PCH or other files contained the old commctrl.h files,
so I exited, purged all of the weird BC++ files from the project
directory and did a complete rebuild. Same error. I ended up
adding this in my .rc:
    #ifndef LVS_EX_CHECKBOXES
        #include "commctrl.h"
    #endif
something I've never had to do, because Borland's RC never
required any #include of standard files. Anyway, that compiles
ok.  But when I run the application, there is no image state
list on the side of the listview control.  But I do have version
5.x of comctl32.dll on my system.  I think the style isn't being
recognized because I'm using InitCommonControls() instead
of InitCommonControlsEx()

But I don't have InitCommonControlsEx() in my commctrl.h. I
can paste it in from the VC++ file, but  I will still need to use
IMPLIB to get a new import library. But now I'm getting confused
because I don't really know what I need to do to get this
to work.

So what's the prognosis for BC++ 5.02?  All I want is a good
Win32 API C++ development system - I don't want Delphi,
Builder, OWL or VCL or any of that stuff. Just the straight Win32
API. I've been led to believe that Builder isn't a complete a
development system as BC++ 5.02, so I've stayed with BC++
5.02

I really don't want to move to VC++, because I really do like
BC++  (I've been a loyal fan since TC 1.0). But unless there's
some way to keep updating my #include files to keep pace
with all of this new stuff, I may have to go to the Dark Side and
switch to VC++. Say it ain't so.

Thanks for any tips/help/suggestions/commiseration.

--
John A. Grant  * I speak only for myself *  (remove 'z' to reply)
Radiation Geophysics, Geological Survey of Canada, Ottawa
If you followup, please do NOT e-mail me a copy: I will read it here