Subscribe for automatic updates: RSS icon RSS

Login icon Sign in for full access | Help icon Help
Advanced search

Pages: [1]
  Reply  |  Print  
Author Topic: When closing Menu launcher, should it's children programs stop as well  (Read 7553 times)
Candy M.
Posts: 139


« on: January 29, 2018, 04:10:59 pm »

For our application we have a main program that displays a menu and the user
can launch any of the programs.

Our question is, if the window for the main program is closed, should
the other programs that were launched stop as well?
I have included a sample.

menu_launcher.4gl is main program.

programa.4gl and programb.4gl are programs that can be launched.

We see mixed results and are trying to determine a pattern.

In some cases, the child programs stop as well, when the main program is closed.
In other cases, the child programs will remain running.

We are trying to determine what causes the child programs to continue running or
stop.

The child programs have a command "fglrun ......."

When I run this on 3.10.11 GDC and close the program, the child process stops  (Window is no longer seen).   I'm using VPN into our office.
When someone in our office runs it, closes the main program, the child process is still running (Window is still active).

We are using same shortcut in our GDCs.   I don't know if it something in OS or what.   Our GDC connections are SSH in testing.

I have also submitted case to USA support, just wondering if the community has insight on this.   I'm sure it is something simple.

Candy

mtdefault.4st:
Code
  1. <?xml version="1.0" encoding="ANSI_X3.4-1968"?>
  2. <StyleList>
  3.  <Style name="Window.mtmain_tree">
  4.     <StyleAttribute name="windowType" value="normal" />
  5.     <StyleAttribute name="ignoreMinimizeSetting" value="yes" />
  6.     <StyleAttribute name="startMenuPosition" value="tree" />
  7.     <StyleAttribute name="startMenuSize" value="large" />
  8.     <StyleAttribute name="actionPanelPosition" value="none" />
  9.     <StyleAttribute name="ringMenuPosition" value="none" />
  10.     <StyleAttribute name="toolBarPosition" value="none" />
  11.     <StyleAttribute name="errorMessagePosition" value="popup" />
  12.  </Style>
  13. </StyleList>
  14.  
mtstart.per:
Code
  1. DATABASE formonly
  2. LAYOUT
  3. GRID
  4. {
  5. [image1                                                                        ]
  6. }
  7. END
  8. ATTRIBUTES
  9. IMAGE image1:image1, IMAGE="mtstart", PIXELWIDTH=640, PIXELHEIGHT=480,
  10.         STRETCH=BOTH;
  11.  

* menu_launcher.4gl (2.75 KB - downloaded 1016 times.)
* programa.4gl (0.6 KB - downloaded 1030 times.)
* programb.4gl (0.56 KB - downloaded 1030 times.)
* programa.per (0.15 KB - downloaded 1003 times.)
Candy M.
Posts: 139


« Reply #1 on: February 05, 2018, 05:37:37 pm »

I wanted to followup with this post.   We did determine it was something in my ssh tunnel that was closing the child programs.

What we wanted, was to not allow the menu launcher program to be closed if any of the children programs were still running, so we could have an orderly exit of our application.

To accomplish this we used the base.Channel and ran a 'ps he --user user_name -o args'  command in linux.
Then we searched for the _FGL_PPID environment variable which appeared to be the linux process ID of the menu launcher.
Then we could inform the user which programs were still running and ask them to please exit those programs.   It appears to work and we got it working in
GDC over ssh, GDC over http and with the GBC.

Candy
Pages: [1]
  Reply  |  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines