🚀 go-pugleaf

Jos� wrote:

> Today another problem arose unexpectedly. It was a familiar one. My
> program compiled and linked without problem but it crashed at the very
> outset. I already knew the solution to this problem: Start a new
> project, copy *.H, &.CPP and *.DFM, and the problem is solved.

Which .cpp file is that ? The one that contains calls to SelectDirectory() ?

I assume that you have more units in the project so this solutions
looks terrible.

Did it crash as soon as you tried to run it ? Inside/oudside the IDE ?

It might help if you told which version of buider you use.

> But this time this procedure resulted in another nasty problem:
> 
> [Linker Error] Unresolved external '__fastcall
> Filectrl::SelectDirectory(const System::AnsiString, const
> System::WideString, System::AnsiString&)' 

Throw away the .tds file and all .o files and do a rebuild.

Hans.

"Jos�" <jose@127.0.0.1> wrote in message
news:6jgu42lmnd7anrv89k6h8uevgnru3qshm2@4ax.com...

> But this time this procedure resulted in another nasty problem:

By default, the VCL's FileCtrl unit is not linked into an application,
because that particular unit is in the wrong VCL library file to begin with.
That is a long-standing problem on Borland's part.  In order to force that
unit to be linked into the application correctly, you have two choices:

1) drop a Win3.1 component onto a form, save the project, and then remove
the component.  The appropriate package references will remain in the
project.

2) edit the project BPR file directly to include the vclx package into the
projet manually.  The actual name of the package file depends on your
version of BCB:

    BCB 1 = ?
    BCB 3 = vclx35.bp*
    BCB 4 = vclx40.bp*
    BCB 5 = vclx50.bp*
    BCB 6 = vclx.bp*
    BDS 2006 = ? (I'll have to look that one up later)

The alternative is to not use SelectDirectory() at all.  Use the Win32 API
SHBrowseForFolder() function directly instead.  But then you have to deal
with other compiler errors if you are using BCB 5 or higher.  To fix those,
you have to add NO_WIN32_LEAN_AND_MEAN to the Conditionals list in the
Project Options dialog.


Gambit

On Wed, 26 Apr 2006 14:57:09 +0200, Hans Galema <notused@notused.nl>
wrote in borland.public.cppbuilder.nativeapi:

>> Today another problem arose unexpectedly. It was a familiar one. My
>> program compiled and linked without problem but it crashed at the very
>> outset. I already knew the solution to this problem: Start a new
>> project, copy *.H, &.CPP and *.DFM, and the problem is solved.
>
>Which .cpp file is that ? The one that contains calls to SelectDirectory() ?

The very one

>I assume that you have more units in the project so this solutions
>looks terrible.

There is only one unit

>Did it crash as soon as you tried to run it ? Inside/oudside the IDE ?

Immediately when the program starts, before any window is displayed. I
cannot single step into the error.

>It might help if you told which version of buider you use.

4.0

>> But this time this procedure resulted in another nasty problem:
>> 
>> [Linker Error] Unresolved external '__fastcall
>> Filectrl::SelectDirectory(const System::AnsiString, const
>> System::WideString, System::AnsiString&)' 
>
>Throw away the .tds file and all .o files and do a rebuild.

Well, I restored a back-up of the crashing program 
-- 
Jos�

On Wed, 26 Apr 2006 11:05:40 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote in borland.public.cppbuilder.nativeapi:

>
>"Jos�" <jose@127.0.0.1> wrote in message
>news:6jgu42lmnd7anrv89k6h8uevgnru3qshm2@4ax.com...
>
>> But this time this procedure resulted in another nasty problem:
>
>In order to force that
>unit to be linked into the application correctly, you have two choices:
>
>1) drop a Win3.1 component onto a form, 
>
>2) edit the project BPR file directly t

I did neither before the problem arose, and without trouble. Your
solution may be fine, but the first time I used SelectDirectory() I
had no problem at all.

>The alternative is to not use SelectDirectory() at all.  Use the Win32 API
>SHBrowseForFolder() function directly instead.  

We discussed this before. I had lots of trouble using
SHBrowseForFolder(), while SelectDirectory() was quick and easy.
-- 
Jos�

"Jos�" <jose@127.0.0.1> wrote in message
news:gar052pvee5ubqnv989tid8vcprkrku2tv@4ax.com...

> I did neither before the problem arose, and without trouble. Your
> solution may be fine, but the first time I used SelectDirectory() I
> had no problem at all.

For that to happen, you had to have done something in the project beforehand
that already caused the necessary changes to the project, and you just
didn't notice it until now.

> We discussed this before. I had lots of trouble using SHBrowseForFolder()

Such as?  It is a very easy function to use.


Gambit

Remy Lebeau (TeamB) wrote:

> For that to happen, you had to have done something in the project beforehand
> that already caused the necessary changes to the project, and you just
> didn't notice it until now.

Not needed. When I start a new application with bcb5 then

#include <FileCtrl.hpp>

is all that has to be done.

Hans.

On Thu, 27 Apr 2006 00:52:38 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote in borland.public.cppbuilder.nativeapi:

>> We discussed this before. I had lots of trouble using SHBrowseForFolder()
>
>Such as?  It is a very easy function to use.

Sorry, my memory failed me a bit. Hans advised to use that function. I
could not find it in help files, and Regis advised me to look in 
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/shell/reference/functions/shbrowseforfolder.asp

This turned out to be pretty complicated, and in the meantime my
attention was drawn to the much easier function SelectDirectory, and I
could not be bothered about SHBrowseForFolder any more.

It could be that SHBrowseForFolder is easy to use, but its
documentation requires same patient reading.
-- 
Jos�

Jos� <jose@127.0.0.1> wrote:
>
> [...] advised me to look in [...] This turned out to be
> pretty complicated,

You seem to be ignoring the archives. When I said that there
was at least one sample that was a component I wasn't kidding.

   http://tinyurl.com/mocny

If you click File | New | Unit and save the new unit and then
paste the sample, all you'd have to do is remove the component
specific stuff:

static inline void ValidCtrCheck(TBrowseForFolder *) 
{
    ...
}

and

namespace Browseforfolder 
{
    ...
}

Then to use it, include it's header and dynamically allocate it
just like another other component. Set it's Prompt, Caption,
InitialFolder and RetainSelection properties and use it's
Execute method just like any other dialog.

Note that since it's assigned an Owner, you don't need to
delete it. You can allocate it in the form's constructor
and forget about it until you need to use it.

It should take you 10 minutes tops. Just don't forget to add
NO_WIN32_LEAN_AND_MEAN as noted by Gambit.

~ JD

"Hans Galema" <notused@notused.nl> wrote in message
news:44507adf$1@newsgroups.borland.com...

> Not needed. When I start a new application with bcb5 then
>
> #include <FileCtrl.hpp>
>
> is all that has to be done.

That is not the end-all solution.  Yes, the function is *declared* in that
file, so the compiler is happy.  But the function *code* is in the wrong
binary lib file which does not always get included into a project, so the
linker usually complains.  Hense my earlier suggestions for forcing the
required library to be included into the project.


Gambit

On Thu, 27 Apr 2006 10:11:22 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote in borland.public.cppbuilder.nativeapi:

>Yes, the function is *declared* in that
>file, so the compiler is happy.  But the function *code* is in the wrong
>binary lib file 

I think there is an upgrade suggestion here. A header should not only
contain a function declaration, but also the name of the library file,
so that the library is automatically included.

This is rather similar to including the entire function definition in
the header.
-- 
Jos�

Remy Lebeau (TeamB) wrote:

> ...   But the function *code* is in the wrong
> binary lib file which does not always get included into a project, so the
> linker usually complains. 

Then the question is: 'when does it and when does it not ?'.

Hans.

Jos� wrote:

> ... A header should not only
> contain a function declaration, but also the name of the library file,
> so that the library is automatically included.

No that is no good. And what syntax would you use?

The o. file or library, which contains the body for a function,
should only be added when the function is actually called.

> This is rather similar to including the entire function definition in
> the header.

Which is never done. Or do you refer to memberfunctions which
are completely in a class definition ?

Hans.

No, it should not.  A header file is a compile time item.  It is not a link 
item.

C and C++ are professional development languages. The variety of uses for a 
professional language includes that where a user supplies a library of his 
choice. .

.  Ed

> Jos� wrote in message
>news:2f4252tilb6shc7alh7vec24s67pevef5l@4ax.com...
>
> I think there is an upgrade suggestion here. A header should
> not only contain a function declaration, but also the name of
> the library file, so that the library is automatically included.
>
> This is rather similar to including the entire function definition
> in the header.

On Wed, 26 Apr 2006 11:05:40 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote in borland.public.cppbuilder.nativeapi:

>2) edit the project BPR file directly to include the vclx package into the
>projet manually.  The actual name of the package file depends on your
>version of BCB:
>
>    BCB 1 = ?
>    BCB 3 = vclx35.bp*
>    BCB 4 = vclx40.bp*
>    BCB 5 = vclx50.bp*
>    BCB 6 = vclx.bp*
>    BDS 2006 = ? (I'll have to look that one up later)

I am no sure how this is done. I tried:

Project | Options | tab Packages | Add | browse to
Borland\Cbuilder4\Lib\Release\Vclx40.Bpi. 

It says: Package can't be installed because another packae with the
same name is already loaded: C:\Windosw\system32\vclx40.bpl

-- 
Jos�

On Wed, 26 Apr 2006 11:05:40 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote in borland.public.cppbuilder.nativeapi:

>2) edit the project BPR file directly to include the vclx package into the
>projet manually.  The actual name of the package file depends on your
>version of BCB:

Hm, BPR happens to be an ASCII file. Of course that's what you meant.
It contains: 

PACKAGES = qrpt40.bpi vcldb40.bpi nmfast40.bpi ibsmp40.bpi
vcldbx40.bpi teeui40.bpi  vclsmp40.bpi teedb40.bpi tee40.bpi dss40.bpi
inetdb40.bpi inet40.bpi  vclmid40.bpi VCL40.bpi VCLX40.bpi 

Adding vclx40.bpl makes no difference.
-- 
Jos�

On Thu, 27 Apr 2006 21:16:36 +0200, Hans Galema <notused@notused.nl>
wrote in borland.public.cppbuilder.nativeapi:

>> ... A header should not only
>> contain a function declaration, but also the name of the library file,
>> so that the library is automatically included.
>
>No that is no good. And what syntax would you use?

This hardly matters. A possible syntax would be:

Function name(parameters)[library name];
-- 
Jos�

On Thu, 27 Apr 2006 16:55:48 -0400, "Ed Mulroy"
<dont_email_me@bitbuc.ket> wrote in
borland.public.cppbuilder.nativeapi:

>C and C++ are professional development languages. 

Which makes programming so hard, I think. I long for the time when I
programmed in Assembly, but this apears to be suitable for DOS
programs only.
-- 
Jos�

"Jos�" <jose@127.0.0.1> wrote in message
news:jkc2521s7b6ffp5an43a10hnps2a0ddpuu@4ax.com...

> I am no sure how this is done.

As I said before, you have to edit the BPR file directly.  The IDE can't
help you on this issue.


Gambit

"Jos�" <jose@127.0.0.1> wrote in message
news:t1d252h9ib68j7p2bgal2i004lsp0mdj1s@4ax.com...

> Hm, BPR happens to be an ASCII file.

Yes.  Which only makes it easier to edit by hand.

> Adding vclx40.bpl makes no difference.

You need to add vclx40.bpi, not vclx40.bpl.  You also should add vclx40.lib
to the LIBRARIES and SPARELIBS sections.


Gambit

On Thu, 27 Apr 2006 14:38:15 -0700, "Remy Lebeau \(TeamB\)"
<no.spam@no.spam.com> wrote in borland.public.cppbuilder.nativeapi:

>> Hm, BPR happens to be an ASCII file.
>
>Yes.  Which only makes it easier to edit by hand.

Definitely. I never looked inside the file before.

>> Adding vclx40.bpl makes no difference.
>
>You need to add vclx40.bpi, not vclx40.bpl.  You also should add vclx40.lib
>to the LIBRARIES and SPARELIBS sections.

That's it. Thanks, Remy.
-- 
Jos�

The same thing applies to programs written partially or entirely in 
assembly, including those for DOS.  If he wishes, the programmer should be 
able to supply his own libraries implemetation.  In the DOS days this was 
even more of a need as machines were not as standardized and it was common 
to supply custom versions of runtime library functions or of the runtime 
library itself to handle differences in customers' machines.

For 32 bit Windows very few programs are entirely written in assembly.  More 
often portions are written in assembly and most of it is written in a higher 
level language such as C or C++.

.  Ed

> Jos� wrote in message
> news:7ad2525vkqstuvar2jl7h5uj1atrgnnf2o@4ax.com...
>
> Which makes programming so hard, I think. I long for the time when I
> programmed in Assembly, but this apears to be suitable for DOS
> programs only.

Jos� wrote:
> On Thu, 27 Apr 2006 16:55:48 -0400, "Ed Mulroy"
> <dont_email_me@bitbuc.ket> wrote in
> borland.public.cppbuilder.nativeapi:
> 
>> C and C++ are professional development languages. 
> 
> Which makes programming so hard, I think. I long for the time when I
> programmed in Assembly, but this apears to be suitable for DOS
> programs only.

You may want to look at the Gibson Research Corporation "Small is
Beautiful" page:

http://www.grc.com/smgassembly.htm

There is also a list of other assembly language resources.

Regards,
Jim Dodd
Onset Computer Corp.

On Fri, 28 Apr 2006 11:42:26 -0400, Jim Dodd <bcbuilderboy@yahoo.com>
wrote in borland.public.cppbuilder.nativeapi:

>You may want to look at the Gibson Research Corporation "Small is
>Beautiful" page:
>
>http://www.grc.com/smgassembly.htm
>
>There is also a list of other assembly language resources.

In the times of DOS I wrote a program in assembly. It was a 50 kB .COM
file. Rewritten with C++B it is 825 kB.
-- 
Jos�

On 27 Apr 2006 05:55:45 -0700, "JD" <nospam@nospam.com> wrote in
borland.public.cppbuilder.nativeapi:

>Just don't forget to add
>NO_WIN32_LEAN_AND_MEAN as noted by Gambit.

Call me a dunce. How is this done?
-- 
Jos�

On 27 Apr 2006 05:55:45 -0700, "JD" <nospam@nospam.com> wrote in
borland.public.cppbuilder.nativeapi:

>You seem to be ignoring the archives. When I said that there
>was at least one sample that was a component I wasn't kidding.
>
>   http://tinyurl.com/mocny

I tried that one. I don't see much difference with SelectDirectory().
They display the same window. I guess one function uses the other one.

>Just don't forget to add
>NO_WIN32_LEAN_AND_MEAN as noted by Gambit.

I did forget it, since I didn't know how to do it, and I had no
errors.
-- 
Jos�