View previous topic :: View next topic |
Author |
Message |
DanRRight
Joined: 10 Mar 2008 Posts: 2893 Location: South Pole, Antarctica
|
Posted: Thu Dec 12, 2024 5:54 pm Post subject: |
|
|
Code: | module MOD1
real*8 :: var1=0
Contains
integer function fun3 ()
call window_update@(var1)
fun3 = 2
end function fun3
end module MOD1
!.....................
Program CONFL2
use mod1
i=winio@('%ww%ca[Not Working]&')
i=winio@("%co[check_on_focus_loss]&")
i=winio@('%^30sl[horizontal] %df%^11rf[fmt=0.3e]%ff&',var1, 0d0,1d0, fun3, 0.1d0, var1,fun3 )
i=winio@('%nl%cn%bt[OK]%es')
END |
The whole purpose of this code is to set using slider some preliminary (low resolution) value of some variable var1 and then use %dd or %rf to set it precisely as needed. And during the process when you move slider you see the value of variable and vice versa if you change the value of var1 in the %dd or %rf the slider also reacts on that.
This link of these controls is broken if %co[on_focus_loss] is present in the code.
Or even worse, the %co somehow conflicts with the %cw (or its components which allow to highlight and save parts of the text inside %cw window) and the whole GUI crashes
Last edited by DanRRight on Fri Dec 13, 2024 2:17 pm; edited 1 time in total |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8090 Location: Salford, UK
|
Posted: Fri Dec 13, 2024 9:26 am Post subject: |
|
|
Dan
What you experience and describe is not a bug but is what you get with %co[check_on_focus_loss]. In effect it is a limitation on the use of [fmt=0.3e].
I will see if I can come up with a work-around or an enhancement to ClearWin+.
You do not provide any information about the %cw failure so I am not able to comment on that. |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8090 Location: Salford, UK
|
Posted: Fri Dec 13, 2024 2:08 pm Post subject: |
|
|
The next release of the DLLs for the ClearWin+ library will include an enhancement so that the following program will respond as requested.
The slider will immediately respond to changes made via the spin control.
Code: | winapp
program main
real*8 :: var1=0
i=winio@('%ww%ca[Working]&')
i=winio@('%30sl[horizontal]&',var1,0d0,1d0)
i=winio@('%fl&',0d0,1d0)
i=winio@("%co[check_on_focus_loss]&")
i=winio@(' %df%11rf[fmt=0.3e]&',0.1d0,var1)
i=winio@('%ff%nl%cn%tt[OK]')
end |
|
|
Back to top |
|
|
DanRRight
Joined: 10 Mar 2008 Posts: 2893 Location: South Pole, Antarctica
|
Posted: Mon Dec 23, 2024 5:42 am Post subject: |
|
|
That is great. All workarounds for Clearwin are welcome. Clearwin is not yet a Standard Fortran anyway. But it is very powerful and incredibly useful tool. People who use this compiler for years but do not use Clearwin are just a effing m$%^s.
If Silverfrost similarly lead the entire Fortran development (for which it had all the chances starting from 1990th) then any workarounds, any sneeze developers made or what their left leg would just decided anywhere in Fortran also become a standard. Given the perturbations with Intel and its Fortran and some others stopped their development may this is not yet too late. For that standard parallelization is needed to add and may be also to jump into AI |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 8090 Location: Salford, UK
|
Posted: Mon Dec 23, 2024 10:05 am Post subject: |
|
|
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. |
|
Back to top |
|
|
DanRRight
Joined: 10 Mar 2008 Posts: 2893 Location: South Pole, Antarctica
|
Posted: Wed Dec 25, 2024 12:52 pm Post subject: |
|
|
I mean to participate in all AI developments involving Fortran. There are several very active ones. For example this one called Modern Neural Fortran.
https://github.com/modern-fortran/neural-fortran
and some others
That will involve modern programmers into this compiler. Currently FTN95 gathers probably all living descendants of infamous Luddites in the world who do work on a single core and do not care. Sects of orthodox Fortran4 and Fortran77 most probably also are hidden here. |
|
Back to top |
|
|
|