![]() ![]()
If you have any more ideas I would greatly appreciate them. ![]() I have also included what I think is the relevant part of my new vfproj file for you to see. ![]() I have also attached a screen capture of that program called "Capture Old Code.jpg". #Simply fortran write to console codeAnyway, I'm sure I can track that down.Ī very old version of the code (one for which I have no source code or project files) only generated a single small console window which was moveable and sizeable and received all diagnostic messages. When I looked at the code I found a command ( EXECUTE_COMMAND_LINE) to make a directory and there was no check on the pre-existence of the folder. I suspect the code is issuing some kind of DOS command that may be causing the other window to appear because at one point it was reporting a folder already existed. I have attached a screen capture here called "Capture New Code.jpg". Additionally, a movable black console window appears. It was replaced by an immovable smaller gray window with a smaller black console inside of it that is currently receiving diagnostic statements being sent by the code. #Simply fortran write to console fullI was actually in the middle of rebuilding as a regular QuickWin project to see what would happen when I received your response.Īs of today, the full screen black console window is gone. #Simply fortran write to console 64 BitI have my project set up for both 64 bit and 32-bit in both DEBUG and RELEASE mode. vfproj file but the system rejected the attachment so I am simply copying it here. Life sometimes gets in the way of having one. ![]() I have been all over the Google world and have not found a solution to my problem. I know there is something simple I am missing. Stepping through the next write statement still opens the full screen window as before, albeit behind the small console window, and the words MyApp appear there. When I step through the status line a small console window opens as I thought it would. I added the following lines with the idea of opening a small console window which I thought would capture all the output instead. Displayed in that window are the words In MyApp. No sizing options, no taskbar is visible, etc. The problem is, upon hitting the RUN button a full screen console window opens behind the GUI that occupies the ENTIRE screen. The first statement to the console is a simple statement like write(*,*) 'In MyApp' When the user hits the RUN button in the GUI there are several diagnostic and informative outputs going to the console. CheckMate is a graphical debugger, the Debug mode is a simple console. I inherited this rather old application which uses dflogm to present a simple GUI for the user. needed to write a program tremendously and therefore FORTRAN, the first release of. The optimist believes we live in the best of all possible worlds - the pessimist fears this might be true.Fortran Compiler Intel Parallel Professional. In the days of old I was one of those that occasionally created a lot of nearly empty printout. The 'use dfwin' - statement is present only for the sleep function to work, you would not need both in real life.īut I am quite happy that this carriage control does not work any more unless you express your wish to do so explicitly. That is what apparently happens in the open-statement. Write(6,'(a1, a10, i3)')'+','values are ', i ! write to consoleĬall sleep (100) ! wait some time to see the outputĪs far as I understand it, you have to specify that the console handles the first character of an output record as in the days of old, taking it for a carriage control character. Open (unit = 6, file = 'CON', carriagecontrol = 'fortran') Use dfwin ! win 32 API routine definitions ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |