"Dialogs" in AppGraphics (Page 2 of 3)

Jeff,
In a application using the full screen window is opened a child window, for instance a dialog window. A mouse click per accident not  in the window but outside causes that the main window is on the foreground and the child window below it. Is it possible to avoid that the child goes to the background an how can I manage it?
Klaus

Jeff,
For all my applications, the intention is that users only should interact with the current child window but not with other windows (except to have to look only in window below)
So I prefer the first option.
Klaus

Jeff,
I have implemented enablewindow and it works pretty well!
Thanks, Klaus

Jeff,

I've implemented Enablewindow throughout my application and thus far it works seamlessly.

Thank you for taking the time to develop Enablewindow for AppGraphics and following up on member suggestions.

Much appreciated,

Frank

Klaus,

It sounds like a bug.  The two dialogs are very different things behind the scenes.  I'll see if I can recreate it and fix the problem.

Jeff,

To manage the layout of multiple line dialogs, I started to add a CR character at the end of my text line to avoid a random new line like my example:

Subroutine about
use appgraphics
Character*1 cr
cr=char(13)
call dlgmessage(DIALOG_INFO,'_______  HeatCat _______'//cr//&
   '      Copyright by ASC '//cr//&
   ' Computer aided structual design procedure'//cr// &
   ' For vessels with independent cargo tanks '//cr//&
   ' To generated vessels basic data use CASTOR'//cr//&
   ' generating a principal structure model   '//cr//&
   '____________________________________________'//cr//&
   ' This is a test and demo for a standard vessel '//cr//&
   '             beta version 8/1/2018')
end Subroutine about

Is this the best way to do or is there a more straight forward way?

regards Klaus

Jeff,
A nasty problem I got:
From the main window a second window is opened
In this second window  a dialog is opened.
After closing the dialog different returns are found
Using the program from simply fortran for testing control returns with the second window on top.
But if the program runs directly under windows, without using SF, the main window appears on the foreground and that is not the intention.

How can I try to tackle the problem?

The dialog in the second window (initW) starts as follows:

initW = getcurrentwindow()  ! keep the previous window in memory for later return
Call enablewindow(initW,.false.)
! ______________________ open dlg-window__________________________________
dlg_screen = initwindow(250, 360, title = "Secundary Stiffening", closeflag = .false.)
CAll setdialoghotkeys(.TRUE.)
…..........
….........
And it ends with:
call loop()
   Call enablewindow(initW,.true.)
   Call closewindow(CURRENT_WINDOW)
   Call setcurrentwindow (initW)
!____________________________________________________________________________
Contains
.....
May be this info is too short to give a hint and I have to make a tiny testprogram first?

Regards, Klaus

Klaus,

The problem is related to setcurrentwindow.   When you're calling that subroutine, the description (and subroutine name, quite frankly) sound as if it should also bring that window to the foreground.  In reality, all the call does is set the internal indicator within the library to point at that window for any subsequent graphics calls.  The library should also raise the indicated window to the top when setcurrentwindow is called.

I'll make the change and release a new build with the fix within the week.

Jeff, I wrote a window with a scroll bar to list a lot of rows and saved it by calling enablewindow(initW,.false.) to avoid that the window moves to the background by hitting the mouse outside the scroll window as follows:
.....
initW = getcurrentwindow()  ! keep the main window in memory for return to it
Call enablewindow(initW,.false.)
dlg_screen  = initwindow(660, 900, title = "Structural parts defined on cross sections", closeflag=.false.)
.....
Unfortunately it does not work like in all my other dialogs: The window moves to the background but  requires action in it. Other windows are not accepting input.
The only difference with other dialogs is a menu I did add to the scoll window to make it possible to leave the scoll window.

Whats wrong with it?
Klaus

Ok Jeff,
That was the problem. Its not correct to disable the current window
thanks
Klaus

The subroutine test is actually run twice when scrolling.  The problem is that AppGraphics was triggering calling the scroll subroutine whenever a WM_HSCROLL or WM_VSCROLL message was sent by Windows.  While this might seem to make sense, Windows will send these messages with the "scroll request" for SB_SCROLLEND to indicate that scrolling has ended.  Scrolling ending isn't a particularly good reason in AppGraphics to trigger a scrollbar callback.

So calling the subroutine test twice is a bug.  We've fixed it, and it should be included in Simply Fortran 3.15, which we're finishing up now.