forums.silverfrost.com

Ken

Sorry to take you on a wild goose chase. I think you are right. These alternatives don't work in this context.

Thank you for this helpful feedback.

Here are two possible alternative approaches that could be explored.

1) The subroutines FREEZE_WINDOW_CONTENTS@(hwnd) and UNFREEZE_WINDOW_CONTENTS@(hwnd) mig ...

Ken

Thank you for the valued feedback.
This false error report has now be fixed for the next release of FTN95.
In the mean time, a work-around is to use /ignore 967 when using /undef in this cont ...

Ken

Thank you for the feedback. This looks like a bug that needs fixing.

Dan

Thank you for this very useful sample program.

I will keep it (in a simplified form) for future reference.

Here is a copy...

winapp
use clrwin
real*8 FontSize
...

shiftl,shiftr and shifta have now been added for Win32 and x64.

These will be in the next release of FTN95 and the associated DLLs.

Ken

Thank you for the bug report which I have logged for investigation.

Lester

Is there a function like this in the Fortran Standard?
Our focus with respect to development has to be on conforming to the lastest standards.

Thanks Ken. I will add these to the task list.

Lester

Thank you for the feedback.

This is a known fault in the build for v9.05.

This is a false warning that has been removed for the next release of FTN95.

Steve

Please provide a short main program that illustrates the issue.

Lester

Which version of FTN95 are you using? You will probably need to use the DLLs for v9.05 from the download in this post...

http://forums.silverfrost.com/viewtopic.php?t=4245

AI will access and use online help files so any advance will depend on the quality of these files. In that sense there is no direct link between AI and a compiler such as FTN95.

FTN95 has now been fixed for the next release so that an argument that is out of bounds will give a meaningful runtime failure message (as already occurs for Win32).