| Linked resources and path management [message #57345] |
Thu, 06 December 2007 16:09  |
b_gom
Messages: 105
Registered: April 2003
|
Senior Member |
|
|
I've been trying to find a way to include parts of my large collection
of IDL libraries as projects in the new Workbench, since including the
full path bogs down my file server as a consequence of the new
'Analyzing Code' feature. Including each useful folder in my source
tree as an individual project is not feasible.
The 'linked resource' feature looked promising, since I could define a
small number of projects, each with a subset of my source tree, and
open them when required. The problem, though, is that the path for
each 'linked resource' is added to !PATH when the project is opened,
but they are never removed when the project is closed.
Is this a feature or a bug? Is this usage of 'linked resources' kosher?
|
|
|
|
| Re: Linked resources and path management [message #57417 is a reply to message #57345] |
Fri, 07 December 2007 12:51  |
Doug Edmundson
Messages: 58
Registered: November 2005
|
Member |
|
|
b_gom@hotmail.com wrote:
> Hi Doug,
>
> On Dec 7, 9:07 am, Doug Edmundson <do...@ittvis.com> wrote:
>
>> If you have a project's "Update IDL Path Preference" property turned on
>> and you close it, then the IDL Workbench will try and remove it from the
>> path. If it doesn't, then it could be a bug or the associated directory
>> was already on the path (was manually added). The workbench will only
>> remove one instance of a directory, not all occurrences.
>
> It looks like a bug to me. I start with a new workspace, add a single
> new project to it with the 'Update IDL Path' option enabled, then add
> a network folder as a linked resource. When the project is opened, the
> network folder is added to the path. When I close the project, the
> folder is not removed from the path, and the 'analyzing code' process
> continues. Even if I manually remove the folder from the path, IDL
> continues to analyze code over the network. (Hitting the cancel button
> in the 'Analyzing Code' window also has no effect.)
Brad,
This sounds similar to two known bugs with linked folders. Eclipse is
supposed to send a notification when projects, folders or files are
removed. Closing a project is a type of removal. For some reason,
Eclipse doesn't handle linked folders too well and doesn't deliver the
"close" notification for them.
Though we hope Eclipse will fix this in their next release, we may have
to go in and modify their code to fix this.
Sorry this makes your options more limited. I'll add comments
describing your situation to one of the CRs.
Doug
|
|
|
|
| Re: Linked resources and path management [message #57422 is a reply to message #57345] |
Fri, 07 December 2007 11:02 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Dec 7, 12:38 pm, b_...@hotmail.com wrote:
> Hi Doug,
>
> On Dec 7, 9:07 am, Doug Edmundson <do...@ittvis.com> wrote:
>
>> If you have a project's "Update IDL Path Preference" property turned on
>> and you close it, then the IDL Workbench will try and remove it from the
>> path. If it doesn't, then it could be a bug or the associated directory
>> was already on the path (was manually added). The workbench will only
>> remove one instance of a directory, not all occurrences.
>
> It looks like a bug to me. I start with a new workspace, add a single
> new project to it with the 'Update IDL Path' option enabled, then add
> a network folder as a linked resource. When the project is opened, the
> network folder is added to the path. When I close the project, the
> folder is not removed from the path, and the 'analyzing code' process
> continues. Even if I manually remove the folder from the path, IDL
> continues to analyze code over the network. (Hitting the cancel button
> in the 'Analyzing Code' window also has no effect.)
I've noticed that I cannot cancel the Analyzing code..., too. It's
like that process has a mind of its own.
|
|
|
|
| Re: Linked resources and path management [message #57423 is a reply to message #57345] |
Fri, 07 December 2007 10:38 |
b_gom
Messages: 105
Registered: April 2003
|
Senior Member |
|
|
Hi Doug,
On Dec 7, 9:07 am, Doug Edmundson <do...@ittvis.com> wrote:
> If you have a project's "Update IDL Path Preference" property turned on
> and you close it, then the IDL Workbench will try and remove it from the
> path. If it doesn't, then it could be a bug or the associated directory
> was already on the path (was manually added). The workbench will only
> remove one instance of a directory, not all occurrences.
It looks like a bug to me. I start with a new workspace, add a single
new project to it with the 'Update IDL Path' option enabled, then add
a network folder as a linked resource. When the project is opened, the
network folder is added to the path. When I close the project, the
folder is not removed from the path, and the 'analyzing code' process
continues. Even if I manually remove the folder from the path, IDL
continues to analyze code over the network. (Hitting the cancel button
in the 'Analyzing Code' window also has no effect.)
|
|
|
|
| Re: Linked resources and path management [message #57431 is a reply to message #57345] |
Fri, 07 December 2007 08:07 |
Doug Edmundson
Messages: 58
Registered: November 2005
|
Member |
|
|
b_gom@hotmail.com wrote:
> I've been trying to find a way to include parts of my large collection
> of IDL libraries as projects in the new Workbench, since including the
> full path bogs down my file server as a consequence of the new
> 'Analyzing Code' feature. Including each useful folder in my source
> tree as an individual project is not feasible.
>
> The 'linked resource' feature looked promising, since I could define a
> small number of projects, each with a subset of my source tree, and
> open them when required. The problem, though, is that the path for
> each 'linked resource' is added to !PATH when the project is opened,
> but they are never removed when the project is closed.
>
> Is this a feature or a bug? Is this usage of 'linked resources' kosher?
Hi Brad,
If you have a project's "Update IDL Path Preference" property turned on
and you close it, then the IDL Workbench will try and remove it from the
path. If it doesn't, then it could be a bug or the associated directory
was already on the path (was manually added). The workbench will only
remove one instance of a directory, not all occurrences.
From what I understand of your situation, the "linked resources"
approach seems the perfect way to go. Just to reiterate for the general
audience, if you have the IDL Workbench manage each project, then
closing currently unused projects will indeed help with the network
traffic situation (and reduce "analyzing code" if that's the main
concern). So in your case, the key to lowering network traffic is
indeed to limit the number of unneeded PRO files on the path. Pointing
to them with a project is fine, just close them when they're not needed.
Cheers,
Doug
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
