Screen issues when I get back from call to ghost screen

[Karen Barrett]

Hiya John,

I don't think you want to know this mode, based on strange display issue.  I hauled it out because the other ghost screens were being called that way.

 
Working fine now with basic call/passing. 
 

 run screen multichip_nl_f &
              passing is_mc_flag &


Called screen very minimal too - 

screen multichip_nl_f & 
 nomode & 
 receiving is_mc_flag      blah blah blah.

 

Happy New Year!


Karen

 


Subject: RE: Screen issues when I get back from call to ghost screen
Date: Fri, 7 Jan 2011 11:55:06 -0500
From: PICKERIJ at norbord.com
To: kbarrett00 at hotmail.com
CC: powerh-l at lists.sowder.com








Interesting! I’ve never heard of “MODE GHOST” before! I didn’t think there was much about Powerhouse left for me to learn!
 
My ghost screens are all called without MODE and are defined as SCREEN XX MENU.
 




From: powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com [mailto:powerh-l-bounces+john.pickering=norbord.com at lists.sowder.com] On Behalf Of Karen Barrett
Sent: Thursday, January 06, 2011 6:51 PM
To: PowerhouseList Post
Subject: Screen issues when I get back from call to ghost screen
 
Hi All,
 
<snip>
 The passed items are declared as temps in both calling and called screens.       
        let return_status_text_c132 = " "
        let t_pass_lot_id = lot_id of lot_step_summ
        run screen multichip_f mode ghost &
             passing is_mc_flag    &
            , t_pass_lot_id   &
<snip> 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20110107/000848e5/attachment.htm