forums.silverfrost.com

DanRRight · Posted: Wed Nov 02, 2022 6:24 am Post subject:

Thanks Mecej4, this solution with as usually perfect guiding description finally works and resolves the major problems of initial start of new thing. You saved me from days of clueless attempts.

Thanks Paul for new video. Clearwin finally has signs of perfection i always wanted to see from the beginning. Visual Clearwin was good idea at that time but it did not get enough traction i think. Please keep broadening its usage. Today with most Fortran compilers, tomorrow hopefully also with other OS

By the way i read in the documentation (possibly i did not update it for a long time) that %cw usage with gFortran/Intel changed vs FTN95 but still i see the attempt to open the %cw text window and write something into it. Unfortunately text window did not work when i ran this code clearly made for other compilers i do not know where from it got into my computer: error messages - missing %cw related and Info related functions. Is this my gFortran installation bug/feature (Equations dot com 13beta) ?

PaulLaidler · Posted: Wed Nov 02, 2022 11:09 am Post subject:

%cw is not supported for third party compilers.

The documentation refers to an alternative that uses a call to cw_write$. This is incorrect.

For third party compilers %cw can be replaced by %re. Then you do an internal write (to a character variable str) and call EditWriteLn$(hwnd, str) where hwnd is obtained from %lc.

DanRRight · Posted: Thu Nov 03, 2022 3:49 am Post subject:

To avoid confusion, i will post the error i got after downloading today Demo file (with newer clrwin.f95 and other library files)

PaulLaidler · Posted: Thu Nov 03, 2022 8:22 am Post subject:

There are some OpenGL demo programs in the FTN95 samples which by default are located in C:\Users\UserName\OneDrive\Documents\FTN95 Examples\OpenGL.

There is also some code in ftn95.chm at FTN95>ClearWin+>OpenGL>The conversion of a Red Book example.

DanRRight · Posted: Fri Nov 04, 2022 5:32 am Post subject:

Was the reason to remove %cw because of conflict of FTN95 with gFortran, iFort and basically all other compilers respect to where goes the default console print* - is it channel 0, or 1, or 2 or 6 etc?

Before %cw in FTN95 was using channel 0 for Print*. Now channel 2.

The %cw has a lot of flexibility and usability. You also can use any other channels, for example 155 or 43124 and you will just write there like this:

i=winio@('%100.25cw[hscroll,vscroll]&',155) - creates this window for all other such prints like this:

write(155,*) ...

Good about %cw is that 1) it has virtually unlimited buffer 2) you can change font, 3) font size, make it bolt, italic etc, 4) change window backgrounds and 5) i think you can even change color of output fonts. I do not even mention you can highlight and Ctrl+C and Ctrl+V the text from it and save if you need which workaround %re also can do. Typically, if you simulation works, it prints a lot of stuff as intermediate warnings and info etc and all that if goes into %cw instead of Command Prompt is not lost in %cw. Essentially the %cw is the same as Command Prompt window, but you can open 10 different %cw windows and write specific outputs you need there with no limit and all will be saved, while Command Prompt has small buffer you now can not find where to change in Windows Registry, and even if you increase it it is still very limited and often useless

Now i speculate (i need still to succeed to migrate and run my code with other fortrans which may take unknown time as i used tens of thousand lines of Clearwin text everywhere in the codes ) with this workaround %re instead of %cw we are getting a small buffer and additionally essentially losing the ability simply to Print* or write(155,*) Fortran standard way and return back to ancient ages with its black Command Prompt window for all your Print* outputs...Hope i am wrong.

PaulLaidler · Posted: Fri Nov 04, 2022 8:01 am Post subject:

%cw is still supported for FTN95. I accesses the FTN95 I/O library so it can't be used with third party compilers. For example, when you issue WRITE for gFortran you are accessing the gFortran I/O library which is not connected to %cw.

I think that you should be able to write large amounts of data using %re, at least for 64 bit applications. If you encounter problems then let me know and I will check this out.

As I recall, %cw also has a limit which is configurable.

PaulLaidler · Posted: Sun Nov 06, 2022 9:23 am Post subject:

Third party support for %cw has been restored (in the next release of the DLLs) in the sense that %cw will be available via cw_write$ rather than WRITE.

DanRRight · Posted: Wed Nov 09, 2022 5:31 am Post subject: Re:

DanRRight · Posted: Mon Nov 14, 2022 1:36 pm Post subject:

OK, how to compile Clearwin in batch and IDE Plato is clear. Now how to compile in BAT and Plato this simplest OpenGL demo with gFortran? It fails. With native FTN95 the compilation

> FTN95 ooo.f90 /64 /link

works fine both with /64 or without, and no matter with $ or @ without any changes

DanRRight · Posted: Tue Nov 15, 2022 12:01 pm Post subject:

And on a side note, since with FTN95 all works with @ and $ may be it's good idea to get rid of @ for the Clearwin codes to be universally compatible with all other external software and become future proof. The @ bugged me from the day one like some foreign for Fortran symbol, the sign of incompatibility

simon · Joined: 05 Jul 2006 Posts: 270

How do we include cw_write@ (and presumably we need to use cw_write$)? Is it in clrwin$?

On a slightly separate issue, I have not been able to get %bm to work with other compilers. Is there anything I should be doing differently?

PaulLaidler · Posted: Fri Dec 09, 2022 8:33 am Post subject:

Simon

Yes. Use clrwin$ and the form

call cw_write$(10,'Hello there!')

where 10 is the Fortran unit number used with %cw.

So normally you will do a internal WRITE to a CHARACTER variable followed by a call to cw_write$.

But note that %cw was disabled by mistake (for third party compilers) in a recent version of the library. So you may need use a different version of the DLLs.

Please provide a sample for %bm and say which compiler you used.

simon · Joined: 05 Jul 2006 Posts: 270

Hi Paul,

I understand that %cw will soon be restored - if so, then I will wait for the new release.

My bitmap example is not working with NAGWare. Here is a simple example, which works as expected using FTN95:

simon · Joined: 05 Jul 2006 Posts: 270

The curly-brackets solution you mentioned here:
http://forums.silverfrost.com/viewtopic.php?t=4715
solves this bitmap problem. Evidently something is not working with the resource script file, but that is no longer an issue I need to resolve for now.

PaulLaidler · Posted: Wed Dec 14, 2022 8:24 am Post subject:

Simon

I have not tried using ClearWin+ with NAGWare so I don't know which resource compiler they use. It might be the same one as for GFortran which works OK for me. As I recall, you need to use the resource compiler to create a .res file from the .rc script and then link the .res file with the other object code using the native linker.