| Re: Project sav file in 7.0 [message #60575] |
Tue, 03 June 2008 04:07  |
helaha
Messages: 26
Registered: March 2004
|
Junior Member |
|
|
On 2 Jun., 22:28, Robert Moss <robert.m...@gmail.com> wrote:
> On Jun 2, 9:28 am, hel...@gmx.net wrote:
>
>> It hasn’t been possible for me to create a sav file from a project
>> with several routines since version 7.0. I read the tech tips
>> carefully and tried it accordingly, but without success. The problem
>> is always that there aren’t all routines resolved. The file gets
>> bigger if the command ITResolve is included and then the itools work,
>> that’s OK. I tried to store all the routines into one single folder,
>> but without success. Sometimes, but not always small red crosses
>> appear in the project window on some routines? Even more, the sav file
>> doesn’t have always the same size. Is there an issue with lower case
>> letters and capitalized letters? I had no problems before version 7.0.
>> Does anybody have a clue?
>
>> Thanks for any hint,
>> Helmut Ahammer
>
> There are two confirmed bugs with in IDL 7.0.1 that as far as I know
> have not been mentioned here in the newsgroup. I know they are bugs
> because I was working with ITTVIS on Friday to try and identify them
> and possibly resolve them.
>
> Bug 1: Checking the box to "build your project in another IDL session"
> can cause only SOME of your files to be compiled. I have not narrowed
> this down to the exact circumstances where this happens, but it
> definately DOES happen. In my case it is easily solved by NOT electing
> to compile in a separate project. I suspect this may be the problem
> you are seeing. You can try using the .RESET_SESSION option instead,
> or perhaps better yet just start a clean session of IDL if you want to
> build a clean sav file.
>
> Bug 2: When you import a project from an existing directory in the
> file system, and you select the check box that says to update your IDL
> path when opening and closing the project, the directory that was
> imported is added to your !PATH, but it is NOT removed automatically
> as it should be. I suspect this may be one of the causes for much
> complaining I have seen on this group.
>
> Allow me to clarify: I imported a directory into my project, which
> means I am using an existing directory to hold my project files. I did
> NOT copy the files into my workspace. There is a directory created in
> my workspace which holds a couple of things (like the sav file I
> create when I build it, and a .profile), but the source code remains
> in the filesystem at its original locations. I personally like this
> option for reasons I will not bore you with. I selected the "update
> my !path..." bit so that the workbench would automatically see when
> things in my source code tree changed. It dutifully adds two things to
> my !PATH: the directory it created in my workspace, and the directory
> which I imported (out in the file system). When I close the project,
> it removes the directory in the workspace (as it should), but it does
> NOT remove the directory from out in the file system. This is a bug,
> and it seems to me could cause much hair pulling and gnashing of
> teeth.
>
> ITTVIS is aware of both of these problems and is working to address
> them.
>
> Robert Moss, Ph.D.
> EOIR Technologies Inc.
Thank you very much for your suggestions. I changed all my filenames
to lower case and I deleted all additional !Path entries. Now !Path
contains the standard IDL paths and additionally only the path
pointing to the project directory. Nevertheless it doesn’t work. But I
think it’s still a “path” problem because I realized following
behaviour. If I run the project and start a specific routine (which
wasn’t included in the sav file at first), it appears that this
specific routine is correctly included, when the sav file is created
afterwards.
Many thanks so far,
Helmut Ahammer
|
|
|
|
| Re: Project sav file in 7.0 [message #60583 is a reply to message #60575] |
Mon, 02 June 2008 13:28  |
Robert Moss, PhD
Messages: 29
Registered: November 2006
|
Junior Member |
|
|
On Jun 2, 9:28 am, hel...@gmx.net wrote:
> It hasn’t been possible for me to create a sav file from a project
> with several routines since version 7.0. I read the tech tips
> carefully and tried it accordingly, but without success. The problem
> is always that there aren’t all routines resolved. The file gets
> bigger if the command ITResolve is included and then the itools work,
> that’s OK. I tried to store all the routines into one single folder,
> but without success. Sometimes, but not always small red crosses
> appear in the project window on some routines? Even more, the sav file
> doesn’t have always the same size. Is there an issue with lower case
> letters and capitalized letters? I had no problems before version 7.0.
> Does anybody have a clue?
>
> Thanks for any hint,
> Helmut Ahammer
There are two confirmed bugs with in IDL 7.0.1 that as far as I know
have not been mentioned here in the newsgroup. I know they are bugs
because I was working with ITTVIS on Friday to try and identify them
and possibly resolve them.
Bug 1: Checking the box to "build your project in another IDL session"
can cause only SOME of your files to be compiled. I have not narrowed
this down to the exact circumstances where this happens, but it
definately DOES happen. In my case it is easily solved by NOT electing
to compile in a separate project. I suspect this may be the problem
you are seeing. You can try using the .RESET_SESSION option instead,
or perhaps better yet just start a clean session of IDL if you want to
build a clean sav file.
Bug 2: When you import a project from an existing directory in the
file system, and you select the check box that says to update your IDL
path when opening and closing the project, the directory that was
imported is added to your !PATH, but it is NOT removed automatically
as it should be. I suspect this may be one of the causes for much
complaining I have seen on this group.
Allow me to clarify: I imported a directory into my project, which
means I am using an existing directory to hold my project files. I did
NOT copy the files into my workspace. There is a directory created in
my workspace which holds a couple of things (like the sav file I
create when I build it, and a .profile), but the source code remains
in the filesystem at its original locations. I personally like this
option for reasons I will not bore you with. I selected the "update
my !path..." bit so that the workbench would automatically see when
things in my source code tree changed. It dutifully adds two things to
my !PATH: the directory it created in my workspace, and the directory
which I imported (out in the file system). When I close the project,
it removes the directory in the workspace (as it should), but it does
NOT remove the directory from out in the file system. This is a bug,
and it seems to me could cause much hair pulling and gnashing of
teeth.
ITTVIS is aware of both of these problems and is working to address
them.
Robert Moss, Ph.D.
EOIR Technologies Inc.
|
|
|
|
| Re: Project sav file in 7.0 [message #60589 is a reply to message #60583] |
Mon, 02 June 2008 07:34 |
Vince Hradil
Messages: 574
Registered: December 1999
|
Senior Member |
|
|
On Jun 2, 8:28 am, hel...@gmx.net wrote:
> It hasn’t been possible for me to create a sav file from a project
> with several routines since version 7.0. I read the tech tips
> carefully and tried it accordingly, but without success. The problem
> is always that there aren’t all routines resolved. The file gets
> bigger if the command ITResolve is included and then the itools work,
> that’s OK. I tried to store all the routines into one single folder,
> but without success. Sometimes, but not always small red crosses
> appear in the project window on some routines? Even more, the sav file
> doesn’t have always the same size. Is there an issue with lower case
> letters and capitalized letters? I had no problems before version 7.0.
> Does anybody have a clue?
>
> Thanks for any hint,
> Helmut Ahammer
There has always been an issue with file name cases...
I'd also look at your path to make sure it's being handled the same as
before. That's the major change, that I've found regarding resolving
file names.
|
|
|
|
|
|
| Re: Project sav file in 7.0 [message #61760 is a reply to message #60575] |
Tue, 29 July 2008 00:41 |
helaha
Messages: 26
Registered: March 2004
|
Junior Member |
|
|
Finally, I was able to solve the problems and want to post the
solution here. First, file name cases were not the problem
(WindowsXP). Second, the !path issue (bug), as mentioned by Robert
Moss, has been eliminated for the current IDL version 7.0.3. With this
version there appeared some (red marked) compilation errors in my
routines, which I had to eliminate. But there were still a few errors,
which were only shown, when I disabled the ITRESOLVE command.
Disabling the ITRESOLVE command led to a very detailed compilation
result, showing an extended list of routines and subroutines. But if
there was an error, the compilation stopped and only the routines
compiled so far were saved. Such an error appeared in the list without
a red marking just before the first “SAVE” line (and this could be in
the middle of a very long list). There is still an issue concerning
the resolving of all iTools routines. The only way to include both the
iTool routines and my own routines was following: Building the project
at first with the ITRESOLVE command enabled and then afterwards
building the project with the ITRESOLVE command disabled.
So the project building under IDL7 is far more accurate compared to
prior versions (e.g. 6.4). IDL7 stops compiling whenever a compilation
error appears whereas prior versions continued compiling.
Almost always some of my routines are under development and aren’t
really free of errors. As an example there was a wrong single “I” in a
command line. Therefore there appeared the error that the function or
routine “I” cannot be found. Now I can say that finding a single “I”
in several hundred routines and over 70.000 command lines is really a
challenge. The advantage is now, that my code is really error free.
Helmut Ahammer
MUG
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
