Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Text editor doesn't recognize fixed-form source

Steven_L_Intel1
Employee
2,945 Views
Moved discussion from 11.1 announcement thread
0 Kudos
37 Replies
Steven_L_Intel1
Employee
1,093 Views
Ok- I didn't think it would but it was worth a shot. Let me see what the IDE developers suggest.
0 Kudos
Steven_L_Intel1
Employee
1,093 Views
The developers got back to me. They say that they know about this issue and that it is not new, though some change may have revealed it for you. The problem can occur when:

  • You try to open a file without a project open and you open the file from the Errors or Find Result pane.
  • The file does not belong to the current (active) project
I will ask that this be fixed in a future update.
0 Kudos
a_leonard
Novice
1,093 Views
The developers got back to me. They say that they know about this issue and that it is not new, though some change may have revealed it for you. The problem can occur when:

  • You try to open a file without a project open and you open the file from the Errors or Find Result pane.
  • The file does not belong to the current (active) project
I will ask that this be fixed in a future update.

What do you mean by "current (active) project"? Is the active project the one that contains the file currently "active" in the text editor. If so, that agrees with what I observe. It never happened to me before I installed 11.1, however.

I have a solution with 47 projects, so it's very likely that opening a file from the Find Results pane will not open a file in the active project.



0 Kudos
Steven_L_Intel1
Employee
1,093 Views
I'll admit that wording had me a bit confused -not sure what he meant by that. But it does sound as if this mostly explains what you are seeing. It will get fixed.
0 Kudos
a_leonard
Novice
1,093 Views
Ok, let's try this. For those of you using VS2005, save the attached file and double-click on it to edit the registry. If you are using a different VS version, do not use this file. (You can edit it and change the 8.0 to 9.0 or 7.1 for VS2008/VS2003 if you wish.) Restart Visual Studio and see if the problem persists. This is just a random idea of mine - I have a request in to the IDE developers for their thoughts.
Can I undo this? Visual SourceSafe doesn't seem to know to use VisualStudio to edit .F files anymore.
0 Kudos
Steven_L_Intel1
Employee
1,093 Views
Undo what - the registry file I sent? that just sets what should be set.

Go into the File Types list as I described earlier, select the F extension and click the Change button by Opens With. Select the desired Visual Studio.
0 Kudos
abhimodak
New Contributor I
1,093 Views
Steve

Reverting back to visual studio in tools--file options does not help. VSS does not recognize F extension. I must be doing something wrong here.

Is there any work around or we are forced to wait for a "patch"? May be it is worth making a point (I apologize for rude words here) that a text editor is quite essential component. Already the IVF text editor lacks many features and that has been blamed on microsoft making too many changes. While I think I understand that I would say that at least keeping the current simple editor intact should be made a part of testing.

Abhi
0 Kudos
Steven_L_Intel1
Employee
1,093 Views
Abhi,

The editor seems to work fine for most people, and we never had a complaint about this during our beta test that I am aware of. I don't know what causes it to fail for you. As for VSS, I don't know what it uses - it should simply be using the file association set in File Types. Can you double-click on a .F file and bring up Visual Studio?

If you want to try to "reset" everything, remove the Intel Visual Studio integration. Delete the registry entries for HKEY_CLASSES_ROOT.f and HKEY_CLASSES_ROOT.for, then reinstall the integration.
0 Kudos
abhimodak
New Contributor I
1,093 Views
Thanks Steve. ".F" does open in visual studio when I double click on it in the windows explorer.

I will do the registry thing you mentioned.

One dumb question: when installing the 11.1 it displays an info-box saying that with new (11.1) integration the old one with v10 will not be possible. However I can still build and run with 10.1.024 through Visual Studio. May be I did not understand it right or is there something here? Does it mean that I don't have 11.1 integration?

Since you say that this text editor problem is my local issue I thought of reporting this.

Abhi
0 Kudos
a_leonard
Novice
1,093 Views
Abhi,

The editor seems to work fine for most people, and we never had a complaint about this during our beta test that I am aware of. I don't know what causes it to fail for you. As for VSS, I don't know what it uses - it should simply be using the file association set in File Types. Can you double-click on a .F file and bring up Visual Studio?

If you want to try to "reset" everything, remove the Intel Visual Studio integration. Delete the registry entries for HKEY_CLASSES_ROOT.f and HKEY_CLASSES_ROOT.for, then reinstall the integration.

I changed the entry back to "VisualStudio.Fortran.8.0" and VSS opens the files correctly. I didn't have to do anything with the installation.
0 Kudos
Steven_L_Intel1
Employee
1,093 Views
If you see 11.1 or as a choice for compiler, you have 11.1. I think it is 10.0 you can't use with the new integration, but I'm not certain of that.
0 Kudos
Steven_L_Intel1
Employee
1,093 Views
I believe that this problem was fixed in update 2 (11.1.046). Please try that and let me know.
0 Kudos
abhimodak
New Contributor I
1,093 Views
I believe that this problem was fixed in update 2 (11.1.046). Please try that and let me know.
Hi Steve

As of today (:)) it is working for me...

Abhi
I may be wrong here but I think it started to work when I installed the previous (July upgrade) 11.1.038.
0 Kudos
Nick2
New Contributor I
1,093 Views
I believe that this problem was fixed in update 2 (11.1.046). Please try that and let me know.

Apparently not, since my issue with Premier (555791) is still open.

I've only tried it onVS2008 SP1 STD/Win2008x64.

If I have a few .FOR files open, I exit VS (the X in thetitle bar), openthe solutionagain - the files that were previously open come up with screwy colors.
0 Kudos
Steven_L_Intel1
Employee
1,093 Views

I can't reproduce that. I looked at your Premier issue and tried following the steps you indicated, but it all worked ok for me.
0 Kudos
Nick2
New Contributor I
1,093 Views

I can't reproduce that. I looked at your Premier issue and tried following the steps you indicated, but it all worked ok for me.

The sequence from that issue was with the old version of 11.1 compiler. The sequence I described above could be a brand new bug.
0 Kudos
Steven_L_Intel1
Employee
1,093 Views

I tried the above sequence too and did not see a problem.
0 Kudos
Reply