Translating CFV source to SF

Klaus,

The indentifiers generated by initwindow are not Fortran units at all.  They are simply integers used internally in the AppGraphics library for managing windows.  They are actually (but not guaranteed to be) sequential as you create windows.  You shouldn't think of them as Fortran IO units at all.  In fact, no Fortran IO calls will work with them.

That's good news that your coordinate translation routines are working well!

Hello Jeff,
I have created an odd conflict between two routines using a mouse click
There function is :
a)  move a figure given in meters by mouse a certain distance
b) zoom in the figure using ordinates in meters. This routine uses  a mouse click for both opposite corners

I can repeat both functions from the menu without crash, but if I use first one and than the other a crash follows. The message is that the program is not longer working.
A debugger error says twice SEGV Segmentation fault.
The crash occurs  inside or while starting the handle subroutine.
What happens? Could you give me a hint how to solve this problem
regards, Klaus

Here the two routines :

Routine moves world window:
SUBROUTINE PICK_MOVE_Window(x_left, y_up, x_rght, y_bot)
USE AppGraphics
integer Oldx,Oldy,MouseXpos, MouseYpos,dx, dy
DOUBLE PRECISION x_left, y_up, x_rght, y_bot, dwx, dwy, xw,yw
dwx=abs(x_left - x_rght) ; dwy= abs(y_up - y_bot)       ! window size in world window
xw = (x_left + x_rght)/2. ;  yw = (y_up + y_bot)/2.       ! current centre of world window
CALL OUTTEXTxy(10,10, 'move center by left mousebutton') !instruction text
Call DRAW_CROSS(xw, yw, dble(5.))
dx= getmaxx() ; dy=getmaxy() 
CALL MOVETO((dx/2),(dy/2))
oldx= getx()   ; oldy=gety()
!    __________________________________________________________________
Call registermousehandler(MOUSE_LB_UP, handle_click_pos)
Call loop
move_x = oldx-MouseXpos ; move_y = oldy-MouseYpos   
!New world window:
    xw = dble(move_x)/dble(dx)*dwx  ;    yw = dble(move_y)/dble(dy)*dwy
    x_left = x_left + xw ; y_up  = y_up  - yw ! new upper left corner
    X_rght = x_rght + xw ; y_bot = y_bot - yw ! new lower right corner
return
contains

subroutine handle_click_pos(x, y)
    integer::x, y
    logical Clicked
Clicked = ismouseclick (MOUSE_LB_UP)
If(clicked)then
    MouseXpos = x
    MouseYpos = y
    Clicked =.false.
end if   
Call clearmouseclick(MOUSE_LB_UP)
    call stopidle   
end subroutine handle_click_pos
END SUBROUTINE PICK_MOVE_Window

….....is in conflict with next routine used twice to zoom in a figure......
SUBROUTINE MOVE_CROSS (x_cross, y_cross, finish)
USE AppGraphics
Use W_ords_to_pixels
    Logical finish
    DOUBLE PRECISION   x_cross, y_cross
   finish=.false.
!    __________________________________________________________________
    Call registermousehandler (MOUSE_LB_DOWN, handle_click)
!    Call registermousehandler (MOUSE_RB_DOWN, handle_click)
Call loop
contains

subroutine handle_click(x, y)
    integer::x, y   
    logical Clicked
   Clicked = ismouseclick (MOUSE_LB_DOWN)
   If(clicked)then
      CAll getmouseclick (MOUSE_LB_DOWN, x, y)
      call line (x-20,y,x+20,y)
      Call line (x,y-20,x,y+20)
      x_cross = dble(real(x -x_offset))/scale_x ;  y_cross  = ywtot- dble(real(y+y_offset))/scale_y! Else
  end if   
call clearmouseclick(MOUSE_LB_DOWN)
Call stopidle ( )
end subroutine handle_click
End SUBROUTINE MOVE_CROSS

hello Jeff,
The getmouseclick is removed but the crash is still the same following on pressing the left mouse button. I tested it with the debugger as well as a temporary print just after the register command and as first statement in the handle subroutines.
The debugger stops with "SEGV Segmentation fault" and i cannot find a guilty statement where it crashes after registermousehandler. The print on the console gives response after registermousehandler and not at the first line of the handle routine.

Klaus,

Let me try to replicate your issue.  I'll have to write a small example program that effectively does the same thing as your code.  Clearly my examining your code snippets haven't led to a solution.  I'm sure it is an internal AppGraphics problem, though.

Jeff,
Thanks for your effort looking to my problem.
The function of parameter finish was to stop the procedure after a right button mouse click. I did remove it while testing. Parameter “finish” has now no function, it is not in use changed elsewhere in the program. I'll remover it completely.
The parameters x_left, y_up, x_rght, y_bot are global variables in the calling procedure and defined in a module but this module is not used in this mouse routines. Module  W_ords_to_pixels is used in MOVE_CROSS (see below). The scale variables are used in “handle_click” but not changed.
The scale parameters are defined in function setwindow which is also contained in W_ords_to_pixels  but will never be changed elsewhere.
Should it help to use different names internal the mouse handler for the scale as well as for the corner points in m?
Thanks so far.
Regards, Klaus

Module W_ords_to_pixels
Use AppGraphics
Real*8 xw,xwtot, scale_x
Real*8 yw,ywtot, scale_y
Integer dx,dy, x_offset, y_offset
TYPE wxycoord
      Real*8 x
      Real*8 y
end type wxycoord
TYPE (wxycoord)wxy
contains

!!!!! ===================== warning ==============================!!!!! a
! The pixel window to show graphics has to be opened prior to apply this function !!!!!

Function setwindow (origin , x_left, y_up, x_rght, y_bot)    ! same as CVF but little changed functionallity!!
! i2   = setwindow (.TRUE.   , x_left, y_up, x_rght, y_bot)  ! make this work in module
        ! make returnvalue =1 if OK, otherwise 0
! In this this function a world coordinate system y from top down is not defined and has to return zero (diff from CVF)
integer setwindow
logical origin     ! to be true for lower left corner and y up warts
Real*8 x_left, y_up, x_rght, y_bot !virtual world corners of the viewport
                    ! If negative lower left corner there is an offset to the origin xw,yw = 0.,0.
Real*8 dxw, dyw    ! absolute "world"dimensions in xy direction
integer dx, dy
setwindow = 0

! the window size in world ordinates is defined by the arguments of this routine!!!!!!!!!!!!!!!!!!
dxw = x_rght - x_left
dyw = y_up - y_bot
If(dxw == 0.)setwindow = -1
If(dyw == 0.)setwindow = -2
If(.not. origin)setwindow = -3
If(setwindow <0) return

! get the pre-defiened window size of the CURRENT window in pixels x,y may be the max screen or lower defined
dx = getmaxx()
dy = getmaxy()

! ****************************************
! WARNING: the scale of the screen between real world orinates and screen resolution has to be the same for x and y
! because the appgraphics functions only knows one scale for instance circles and elipses.
! It is NOT possible to stretch a figure more in one direction unless unrealible figures will be shown!!!
!  If scale_x is not scale_y, scale_x should be recalculated with or without warnimg dlg
!   *************************************

IF(dx > 0 .and. dy > 0 )then
    ! only works in a predefined actual window!
     xwtot = dxw           !  May ..tot should be replaced by  ..w !!!
     scale_x = dble(dx)/dxw
     x_offset= -int(x_left*scale_x)
     
     ywtot = dyw
     scale_y = dble(dy)/dyw
     y_offset= -int(y_bot*scale_y)       ! test pos or neg
!  End subroutine init_world_window
setwindow =1 ! does not work with origin in top left

End if
If(scale_x/scale_y < dble(0.95) .or. scale_x/scale_y>dble(1.05))then
print*,'scale x and y',scale_x,scale_y
dxw=dble(dx)/scale_y; scale_x=scale_y
x_left =dxw - x_rght
call dlgmessage(dialog_warn,'scale in x and y direction whers not the same. Scale x is corrected')
end if
End function setwindow
…..
….