view release on metacpan or  search on metacpan

lib/App/SeismicUnixGui/doc/FAQ_SeismicUnixGui  view on Meta::CPAN

    	$flow_widgets	->clear($_flow_listbox_color_w );
    	
    	2. Blank out the names of the flow name		
   		_set_flow_name_color_w($flow_color);
   		$flow_name_color_w    					-> configure(-text => $var->{_clear_text});
   		$color_flow->{_flowNsuperflow_name_w}	-> configure(-text => $var->{_clear_text});
   		
    	3. clear all the versions from the changed list
   		_clear_stack_versions();
   		
   		4. clear the parameter values and labels belonging to the gui  				
   		$param_widgets		->gui_full_clear();
   		
   		5. clear all stored parameters in the param_flow
   		$param_flow_color_i     ->clear();
   		
   	Q. Which settings are made when the user navigates
   		between superflows and user-built flows work while opening flows?
   		What history of recent activity influences settings?
   		
   		Here are some situations PRIOR to:
   		
   1: Opening and Reading a user-built flow (Flow button)
   		which invokes:
   		
   		L_SU,
   			FileDialog_button
   		     			
   	Prior History  for  CASE 1, in prep for CASE 4
		  1. Open a pre-built superflow
		
	Prior History for CASE 2, in prep for CASE 4
		  1. Select a single sunix program
				 			 	       
	Prior History for CASES 3A-3D	
		Normally for user-built flows already in use:
		in grey (case A), 
		pink(case B) 
		green(case C) or 
		blue(case D)
		
		INCLUDING:
		 	Prior History for CASE: 
   		  1. Open pre-existing user-built perl flow  
   		  2. Open a pre-built superflow
   		  This case is rejected under Prior History  for  CASE 1, in prep for CASE 4
		
		BUT,
 		 can = 'neutral', when   sunix_select is selected
 		 and flow listbox is not a color
 		 ,because, when
 		 sunix_select is selected from a cold start
 	 	 the add2flow_button has not yet been activated
 	 	 
 	 	 can = 'neutral' also, when superflow Data is chosen
 	 	 
 		 can = nothing if chosen before a colored flow exists
 		 when coming from a user-built flow (JML is this possible?)
 		 							   			
 		CASE 3A											   								   							  	
 			if ( $L_SU->{_is_flow_listbox_grey_w} &&  $color eq 'grey' ) { # for added certainty

 		 CASE 3B	
 			} elsif ($L_SU -> {_is_flow_listbox_pink_w} &&   $color eq 'pink') { # more certainty
 			
 		 CASE 3C 		
  				$L_SU -> {_is_flow_listbox_blue_w}  && $color eq 'green') {
  		 CASE 3D		
		      $L_SU -> {_is_flow_listbox_blue_w}  && $color eq 'blue') {
	CASE 4
		When Opening Data for a superflow			

	Prior History for CASE 5
		 1. open pre-existing user-built perl flow

 #########################################################################  	
Q . How to build a new superflow/Tool/pre-built superflows/big_stream from scratch?
   	
   	e.g., interactive picking: iPick.pl
   	
   	NEEDS:
   		iPick (user-invoked from command line)
   		
   		iPick.pl (gui engine)
   		
   		iPick.pm (main module)
   		
   		iPick.config (a local file with work parameter values)
   		
   		iPick_spec.pm (behavioral definitions for iPick)
   		
   		iPick_config.pm (module that links local parameters to the progam flow)
   		
   		iShowNselect.pm (review picks)
   		
   		iSelect_xt.pm ( used for picking the x,t coordinates)
   			writes picks to e.g., .itemp_picks_sp1
   			
   		iPicks2par.pm ( reformatting data)
  
     	iPicks2sort.pm ( reformatting data)
     		
   		iSavePicks.pm ( save work)
   		
------ change the message type and message instructions
   		within SuMessages: e.g. ~ L 360-460 as follows:
   		
=head2 CASE:

  Interactive general x-t picking 

=cut 

   if($SuMessages->{_type} eq 'iPick') { 
=head2 CASE:

  Interactive general x-t picking 

=cut 

   if($SuMessages->{_type} eq 'iPick') { 

       if($SuMessages->{_instructions} eq 'first_pick') {