Delphi 7 Project Manager - unsorted

[Richard Cox]

Is it planned behaviour that the Delphi 7 Project Manager does not sort the
individual file names in alphabetical order (as Delphi 6 did)?

Perhaps it is an option somewhere which I have missed.

Thanks,

Richard Cox.

[Mike Williams (TeamB)]

This is a well-known complaint about D7. Let your feelings be known here:

http://qc.borland.com/wc/wc.exe/details?ReportID=2559

--
-Mike

[Richard Cox]

Thanks, Mike. Sorry, I didn't know it was well-known. Is there a place I
should search before posting to avoid irritating everyone with stuff which
has already been covered?

Cheers,

Richard.

"Mike Williams (TeamB)" <mi...@remove.aps-soft.com> wrote in message
news:Xns940B5E7248...@207.105.83.66...

[Mike Williams (TeamB)]

On 05 Oct 2003, "Richard Cox" <rp...@traqs.com> wrote:

> Is there a place I should search before posting to avoid irritating
> everyone with stuff which has already been covered?

Two good places to search the newsgroups:

http://groups.google.com/advanced_group_search
http://www.fulltextsearch.com

--
-Mike

[Warren Postma]

I added a comment at the QC on issue 2559:

---

http://qc.borland.com/wc/wc.exe/details?reportid=2559

----
Comment Added:

Further to this issue, I think the underlying issue is more subtle
than some people in this forum appear to realize.

Sometimes, initialization order (form creation order in particular) is
very significant. Delphi 7 currently displays items in the order in
which they are created, in the project.

It would be nice, if without changing the order in the DPR file, as a
cosmetic nicety only, we could view all filenames in a project sorted by
their name. [ The workaround so far suggests reordering the dpr file,
which can creates huge problems, physical ordering of UNITS is
significant, and possibly INDEPENDANT of form creation order. ]

What I have been missing even MORE than this is the ability to not only
view the files in sorted order, but to group them into visual groups.
In the Microsoft Visual C++ 6.0 IDE (and probably in VC++.NET too) you
can create a project, and then create a Group (which looks just like a
subfolder icon, in the tree view), and then group your related files
together by this.

The reason this related to Report#2559 is that the original poster
relied on file naming conventions (Abc*.pas for all files related to
component Abc) to group his files together. Good idea, but wouldn't it
be nice if subcomponent of the system Abc could have a folder Abc
containing all the files. These folders need not be reflected as
anything more sophisticated than as comment/pragmas {##SUBFOLDER:XXX##}
in the DPR file.

Secondly, if sorting is put back into the D7 IDE, it would be nice if it
were optional, so you could select Sort by Initialization Order, Sort by
Filename, since there is value to the current D7 behaviour, where it
shows the project in the order in which the units are declared in the
uses clause, in the DPR file, and in an order which corresponds to their
initialization/finalization section execution order.

Warren Postma
Toronto Canada
wp at tekran dot com

[Chris Morgan]

> Sometimes, initialization order (form creation order in particular)
is
> very significant. Delphi 7 currently displays items in the order in
> which they are created, in the project.

As I understand it, initialisation order is not determined by the
order
in the project uses clause, but by the *dependencies* of the units
used,
and the order of units is only used to determine default scoping rules
to resolve variable/type name clashes.
The initialisation order is determined by the compiler, and has
nothing
to do with the physical order in which units are listed in the uses
clause.
This would make it very difficult for the project manager to display
units in initialisation order.

Cheers,

Chris

[Jeff Overcash (TeamB)]

Chris Morgan wrote:
>
> > Sometimes, initialization order (form creation order in particular)
> is
> > very significant. Delphi 7 currently displays items in the order in
> > which they are created, in the project.
>
> As I understand it, initialisation order is not determined by the
> order
> in the project uses clause, but by the *dependencies* of the units
> used,
> and the order of units is only used to determine default scoping rules
> to resolve variable/type name clashes.
> The initialisation order is determined by the compiler, and has
> nothing
> to do with the physical order in which units are listed in the uses
> clause.

You understand incorrectly. The order in the uses clause does affect
initialization order.

> This would make it very difficult for the project manager to display
> units in initialisation order.

Danny Thorpe has already stated this was an intentional change to deal with
exactly this type of problem.

>
> Cheers,
>
> Chris

--
Jeff Overcash (TeamB)
(Please do not email me directly unless asked. Thank You)
If there is somebody up there could they throw me down a line. Just a
little helping hand just a little understanding. Just some answers to the
questions that surround me now. If there's somebody up there could
they throw me down a line. (Fish)

[Chris Morgan]

> You understand incorrectly. The order in the uses clause does
affect
> initialization order.

Oh OK.

Thanks,

Chris